Understanding CRM Data Migration Complexity: A Framework for Agencies
Paul Aqua · Founder, QuillSwitch
Every CRM migration starts with the same question: 'How long will this take?' Learn our 5-category complexity scorecard that gives defensible estimates backed by data.
Why 'How Long Will This Take?' Is the Hardest Question in RevOps
Every CRM migration engagement starts the same way: the client asks how long it will take, and the agency guesses. Sometimes the guess is right. More often, it's not — and the gap between estimate and reality is where agency margin goes to die. The challenge is that migration complexity is genuinely multidimensional. Record volume is the metric everyone reaches for first, but it's often the least predictive of actual effort. A migration involving 500,000 clean contact records can be faster than one involving 50,000 records with broken associations, legacy custom fields, and four years of inline attachments. Without a structured complexity framework, every estimate is a bet, and agencies absorb the downside when that bet is wrong.
The 5-Category Complexity Scorecard
QuillSwitch's complexity framework evaluates migrations across five dimensions, each scored 1–5 based on discovery inputs. Category 1: Data Volume and Variety — how many records, objects, and relationship types are involved. Category 2: Data Quality — percentage of records with missing required fields, duplicate rates, and inconsistent formatting. Category 3: Workflow and Automation Complexity — number of active workflows, sequences, assignment rules, and custom automation logic that must be preserved or reconstructed. Category 4: Attachment Density — whether files are attached to records and at what volume, since file migration has a materially different infrastructure cost than record migration. Category 5: Integration Dependencies — how many third-party tools are connected to the source CRM and must be reconnected or reconfigured post-migration. Each category score feeds into a composite complexity tier that maps to a time and cost estimate range.
Scoring Data Volume and Variety
Volume alone is a blunt instrument. The more useful input is the combination of record count, object diversity, and relationship density. A database of 100,000 contacts in a single object with no associations is straightforward. A database of 30,000 contacts linked to custom objects, with many-to-many deal associations and multi-touch attribution fields, is not. When scoring this category, agencies should inventory: total record count by object type, number of custom object types, number of association types (including many-to-many), and whether historical activity records (calls, emails, meetings) need to migrate or just live records. Activity migration is frequently underestimated — a five-year-old Salesforce instance can have more activity records than contact records by an order of magnitude, and each activity record carries its own association logic.
The Data Quality Multiplier
Poor data quality is the single most common source of migration underestimation. Agencies that skip a structured data quality assessment during discovery consistently blow their timelines. The key metrics to capture before scoping: duplicate contact rate (industry average is 20–30% in CRMs older than three years), percentage of records missing a required field in the target system, inconsistent picklist values (especially for deal stages, lead sources, and contact types that have accumulated organic variation), and encoding or character set issues that corrupt text fields during transfer. A data quality score of 3 or above on a 5-point scale typically adds 40–60% to base migration effort. QuillSwitch's pre-migration audit surfaces these issues automatically, giving agencies the data they need to scope accurately and protect their estimates contractually.
Scoping Workflows and Business Logic
Workflow complexity is the category most likely to be underestimated by agencies without a structured scoring approach. The reason: workflows are invisible until you go looking for them. A client may report 'a few automations' and have 47 active workflows, many of which they've forgotten about but which their team depends on daily. The discovery process must include a full workflow audit in the source system — not just a count of workflows, but an assessment of which ones touch what records, which trigger conditions are CRM-native vs. property-based, and which involve external actions (webhooks, integrations) that require independent reconfiguration. Agencies should treat each workflow as a discrete migration unit, not a background item. At QuillSwitch, workflows are migrated as first-class objects with documented pre- and post-migration validation, not reconstructed from scratch by hand.
Attachment Density: The Hidden Infrastructure Cost
File migration is categorically different from record migration and must be scoped separately. The infrastructure cost of migrating attachments depends on total file volume (GB), number of individual files, file type diversity (some CRMs store attachments as links, others as binary blobs), and the access control model of the source system. Agencies frequently exclude attachments from migration scope to reduce apparent cost, then face client escalations when the new CRM feels operationally empty. A better approach: score attachment density explicitly in discovery, quote it as a separate line item, and use it as an opportunity to demonstrate the depth of your migration capability. For clients in professional services, healthcare, or financial services, where documents are tied directly to deal outcomes, attachment migration is often the highest-value component of the entire engagement.
Turning Complexity Scores into Defensible Estimates
The output of a structured complexity scorecard is a composite tier (Low, Medium, High, Enterprise) that maps to a time range, a resource model, and a price band. Low-complexity migrations (composite score 1–2): typically completable in 72 hours with automated tooling, minimal manual intervention. Medium (3): 72–120 hours with structured data quality remediation and workflow validation. High (4): 1–2 weeks with dedicated migration engineering and custom field mapping. Enterprise (5): scoped individually with a full discovery engagement. Publishing this framework — even in simplified form — to clients and prospects does two things: it positions your agency as methodical and trustworthy, and it creates a paper trail that protects you contractually when scope changes. QuillSwitch's platform encodes this framework into its pre-migration audit, making defensible scoping a repeatable process rather than a judgment call.