Nothing broke — the environment simply reached volume during real-world usage. The workflows that looked perfect during implementation are now handling thousands of records, hundreds of documents, and daily user activity. Storage grows, templates multiply, approvals slow down, and support questions change.
The implementation was successful. The challenge is what happens when success scales.
The pattern partners see over and over
Across Dynamics 365 partners, the same story repeats itself in different customer environments. A project goes live on schedule. User acceptance testing passes. The customer signs off happy.
Then, somewhere between month four and month eight, small frustrations start to surface. Quotes take longer to put together. Storage warnings appear out of nowhere. Users start double-checking which version of a template is the current one.
A recent partner panel featuring Velosio, congruentX, and RSM compared notes across their customer bases and landed on the same conclusion: these issues rarely arrive all at once. They build quietly from ordinary habits — a tracked email here, a manual proposal there — until the environment behaves differently than it did on day one.
Why these problems are invisible at go-live
User acceptance testing with two hundred records cannot surface a problem that only exists at ten thousand records. That isn’t a testing failure. It’s a scope limitation nobody names out loud.
Storage was fine at go-live because there was almost nothing in the system yet. Templates were consistent because there were only four of them. Approvals were fast because nobody was queued behind anyone else. None of that was engineered — it was just true, temporarily, because the environment hadn’t reached production volume.
Example: An IT Manager signs off on a document approval workflow during testing. It runs cleanly against a dozen sample records. Eight months later, that same workflow is what sales reps complain about most — not because it changed, but because it now runs fifty times a day instead of twice.
The four things that change between month one and month six
Storage starts growing silently
A new Dynamics 365 environment barely registers on a capacity report. By month six, tracked emails, attachment-heavy notes, and untouched historical activity have quietly become the largest line item.
mscrm-addons.com’s own product data shows email attachments and notes can account for up to 70% of Dataverse storage in an environment that’s been live for a while — not because CRM record volume grew, but because nobody was managing what got attached to those records.
Example: An IT Manager gets a capacity warning, reviews record counts, and finds they’ve barely moved. The real growth turns out to be two years of tracked email attachments that nobody was actively governing.
Templates lose control
At go-live, there’s usually one quote template and one invoice template, built and approved during the project. Six months in, sales has a variant, service has another, and a regional office has quietly modified a third.
Example: A Solution Architect running a health check finds four versions of the same proposal template in active use across business units, no two of them identical, and no clear record of which one is actually correct.
Workarounds become processes
Early on, a manual workaround is a one-time exception for an edge case. By month six, it’s simply how a team gets its work done — invisible to reporting because it lives entirely outside Dynamics 365.
Performance expectations change
Early support tickets ask how to use a feature. Later support tickets complain that something that used to work fine no longer does.
That shift is a volume signal, not a training gap — and treating it as the latter wastes everyone’s time.
Why this lands on the partner, not the customer
A customer experiencing this shift doesn’t know whether it’s a platform limit, a configuration gap, or something their own team did wrong. What they do know is who implemented the system — so that’s who they call.
This is worth stating generously, not as a criticism: the partner didn’t miss anything at go-live. Storage, template governance, and workaround creep are volume problems, and volume can’t be tested for in a project that, by definition, hasn’t reached volume yet.
What a six-month health check should look at
A short, structured review can catch this shift before a customer escalates it. Worth checking on a recurring basis:
- Storage trend — Is file and database consumption growing faster than record count would explain?
- Template count per process — How many versions of the same quote, invoice, or contract template are currently in use?
- Manual workaround count — How many steps in the “official” process actually happen outside Dynamics 365?
- Ticket category mix — Has the ratio of “how do I” tickets to “why is this slow” tickets shifted in the last quarter?
- Approval and generation cycle time — Is the time to produce and approve a document trending up as volume increases?
What partners include up front to avoid the cleanup project
The partners who avoid a painful mid-contract cleanup project are the ones who scope document governance and storage strategy into the original implementation, rather than treating them as a phase-two conversation.
That doesn’t mean solving everything on day one. It means naming, in the statement of work, who owns templates and how storage will be monitored once the environment reaches real volume.
This is also why many partners introduce dedicated solutions for these areas early in the lifecycle. DocumentsCorePack helps maintain template governance, while solutions such as AttachmentExtractor help customers manage Dataverse storage growth.
Frequently asked questions
What problems usually appear in Dynamics 365 after go-live?
The most common are rising Dataverse storage costs, template sprawl across departments, manual workarounds that quietly become permanent, and support tickets that shift from training questions to performance complaints.
None of these typically show up during implementation, because none of them exist until the environment reaches real usage volume.
Why does Dataverse storage become an issue only after implementation?
A new environment has little data in it, so storage isn’t a visible constraint yet. Storage pressure builds from tracked emails, attachments, and notes accumulating over months of daily use — not from core CRM records, which stay comparatively lightweight even at scale.
Should storage and document tooling be scoped during implementation or after?
During implementation, ideally as a named line item in the statement of work.
Scoping it early doesn’t mean solving it immediately — it means the customer and partner agree upfront on who owns template governance and how storage will be monitored once usage grows.
What should a Dynamics 365 post-implementation review cover?
At minimum:
- Storage growth trend
- The number of active template versions per business process
- How many steps in daily workflows happen manually outside the CRM
- Whether support tickets are shifting from “how do I” questions toward performance complaints
See the full framework
The D365 Efficiency Partner Advisory Guide walks through this pattern in more depth, with a repeatable framework partners can use during onboarding, optimization reviews, and annual customer health checks.
Download the Partner Advisory Guide to start identifying these signals before your customers do.