There is no honest single number for a CRM migration. Two projects with the same contact count can differ by an order of magnitude in effort, because the cost sits in history, relationships and the process work around the data. This guide breaks down the six drivers, then compares what you pay for with DIY, native tools, migration tools and services, citing the published prices of public options.
What drives the cost of a CRM migration?
| Driver | Why it matters | Cheaper when… | More expensive when… |
|---|---|---|---|
| Record volume | Load time, API limits, checking | Under the importer’s limits | Millions of records, tight API allowances |
| Number of objects | Each object is a mapping and a load step | Contacts, companies, deals only | Leads, cases, products, line items, quotes |
| Custom fields and objects | Schema to build and map | Few custom fields, no custom objects | Many custom objects, record types, sub-forms |
| History | Activities must attach to the right records with original dates | Only open records move | Years of emails, calls, meetings, notes, files |
| Integrations | Each one must be repointed and tested | Email and calendar only | ERP, billing, marketing automation, custom APIs |
| Process work | Pipelines, workflows, reports rebuilt | Same process, simple pipeline | Redesigned sales process, many automations |
Two smaller factors: data quality (duplicates and messy picklists add cleanup) and cutover tolerance (a zero-downtime switch needs delta runs).
What does each approach cost?
DIY with native importers
The tools are free: Salesforce’s Data Loader and Data Import Wizard, HubSpot’s import tool, Zoho’s Migration Wizard. You pay in staff time for:
- exporting from the source, which may not include everything (some exports leave out emails or call logs);
- building one file per object, in dependency order;
- matching new record IDs into child files at every step;
- setting up created dates and owners (for example enabling Create Audit Fields in Salesforce);
- checking the result by hand, with no rollback if a load goes wrong.
DIY is cheapest for a few objects, little history and an admin who has done it before.
Native migration tools
| Option | Published cost | What you get | Limits that add cost |
|---|---|---|---|
| HubSpot Smart Transfer | Free on all plans; custom field mappings need Data Hub | One-way, one-time transfer from 13 apps | No custom objects; Super Admin only |
| HubSpot CRM Data Migration (Bronze, Silver, Gold) | Not published in HubSpot’s catalog | HubSpot-run migration up to 350,000, 1 million or 5 million records | API sources only, no flat files; custom objects limited by tier; Salesforce workflows and reports out of scope |
| Zoho CRM Migration Wizard | Included with Zoho CRM | Files from any CRM, API from a few | No custom modules over API; three reruns on API migrations |
Self-serve migration tools
Published prices as of November 2026:
| Tool | Published pricing |
|---|---|
| dataloader.io (Salesforce loading) | Free (10,000 records a month), Professional $99, Enterprise $299 per user per month |
| Import2 | Free up to 500,000 records when the vendor approves or sponsors; full migration from $499; professional services from $5,000 |
| Help Desk Migration | Per record, one-time; example: $100 for 1,000 records and $514 for 10,000 on the Essential plan |
Tools price by records and apps, so the cost is predictable. What they usually leave to you is mapping decisions, process rebuild and the check that nothing went missing.
Done-for-you services
Services quote by scope. You pay more than a self-serve tool, and in return someone else owns the mapping, the runs, the validation and often the destination build. Partner and agency prices vary widely and are rarely published. When comparing quotes, ask each provider:
- Does the price include activity history (emails, calls, meetings, notes) and files?
- Are custom objects and record types in scope?
- How many sample or test runs are included?
- How are changes during cutover handled?
- What happens if a run fails: is there a rollback?
- Are pipelines, workflows and reports rebuilt, or only data moved?
How do I estimate my own migration’s cost?
- Count records per object, including activities by type. Activities can outnumber contacts many times over.
- List custom objects and fields with fill rates.
- List integrations that read or write the CRM.
- Decide what history moves. All of it, open records only, or a cut-off date.
- List the automations and reports that must exist on day one.
- Estimate internal hours for the DIY route: one load per object, plus ID matching, plus checking.
- Get two quotes with the same scope document, so you’re comparing like with like.
Where do hidden migration costs come from?
- Re-runs. A load that drops history or owners has to be deleted and run again.
- Overlapping licences. Every week of delay is a week paying for both CRMs.
- Lost history. Sales reps rebuilding context by hand, or a forecast with no past data.
- Broken automations. Workflows that fire on imported records and email customers.
- Rework after go-live. Fixing mapping errors once users have changed records is slower than fixing them before.
How can I reduce the cost of a CRM migration?
- Archive instead of migrating closed records nobody reports on; keep them in a searchable backup.
- Drop empty fields before mapping. Every field kept is a field mapped, checked and maintained.
- Agree the destination model first, so mapping isn’t redone after the sample run.
- Freeze schema changes in the old CRM during the project.
- Use a delta at cutover rather than a long freeze, which costs selling time.
Is it cheaper to DIY, use a tool or hire a service?
| If… | Usually cheapest overall |
|---|---|
| Under the importer’s limits, few objects, no history needed | DIY with native tools |
| Source is on HubSpot Smart Transfer’s list, no custom objects, moving to HubSpot | Smart Transfer, plus a check of what didn’t move |
| Standard objects, clear mapping, your team has time | Self-serve migration tool |
| Custom objects, years of history, integrations, process redesign or a hard deadline | A done-for-you service |
When to bring in FlitStack AI
FlitStack AI is a data-migration platform sold as software plus a done-for-you service. Its quote is based on the same drivers: records, objects, custom fields, history, integrations and process work. Every migration includes AI-proposed field mapping you review, a sample run, validation on every record, timestamp preservation, delta migration for cutover and one-click rollback. Pipelines, workflows and reports are set up through the implementation services.
See what’s included on the data migration service page, plan the work with the CRM migration checklist, and book a free scoping call for a quote.