CRM Data Migration Services: Move Your Customer History Without the Mess
Switching CRMs is the one chance to start clean, and the easiest moment to lose years of customer history. We plan and run the move so contacts stay linked to their companies and deals, duplicates are resolved once, and you can see, in counts and in real records, that everything arrived.
Our CRM data migration services move your contacts, companies, deals, activity history and files from spreadsheets or an old CRM into a new one, with duplicates resolved, fields and picklists mapped, relationships intact and record counts reconciled before you switch over. Edward Pinela, MBA plans and runs the migration himself.
A migration is not an export followed by an import. It is a set of decisions: what to bring and what to archive, how to recognize the same customer in two systems, and how old stages and statuses translate into the new ones. Get those right and the new CRM opens on day one with data your team trusts. Your first step is a free 30-minute strategy call; migrations are priced per project rather than from a price list, and you see a written quote before any data is exported.
What goes wrong in a CRM data migration?
Most failed migrations technically finished. The records arrived, but not in a usable state, and the team quietly went back to the old system or a spreadsheet. The common failures are predictable, which is why each one has a step in our method:
- Duplicates multiplied, because each source had its own copy of the same customer
- Contacts imported without their company, or deals with no contact attached
- Notes, calls and emails left behind, or attached to the wrong record
- Records owned by people who left years ago, so nobody is assigned to follow up
- Old deal stages and picklist values dropped into the new system untranslated
- Dates, phone numbers and currencies imported in the wrong format
- New leads still arriving in the old CRM after the final export
How does a CRM data migration work, step by step?
A CRM data migration runs in seven steps, the same whichever platforms are involved: inventory, source cleanup, a signed-off mapping, a test load, the full load in dependency order, reconciliation and cutover. You sign off at every step, so problems surface on a sample rather than across your whole database.
- 1. Inventory and scope: which objects exist, how many records each holds, how far back history goes, and what should be archived rather than migrated.
- 2. Cleanup at the source: deduplicate, standardize values such as states, industries and phone formats, and fill fields the new CRM will require.
- 3. Mapping document: every field, picklist value, owner and relationship mapped from old to new, written down and signed off by you.
- 4. Test load: a sample loaded into a sandbox or test environment. You check records you know well, not just a row count.
- 5. Full load in dependency order: users and owners, then companies, contacts, deals, activities and attachments, so every relationship has something to attach to.
- 6. Reconciliation: record counts compared object by object, spot checks on real accounts, and key report totals compared between old and new.
- 7. Cutover: a short freeze window, a final delta of records changed since the full load, and the old system set to read-only until you sign off.
What moves cleanly, and what needs a plan?
Not every kind of data travels equally well. Contacts and companies are rarely the hard part; activity history, attached files and anything custom usually are, because each destination stores them differently. The table is the short version of the conversation we have during inventory.
| Data | Usually | What to plan for |
|---|---|---|
| Contacts and companies | Straightforward once duplicates are resolved | A reliable unique key: email for people, domain or an ID for companies |
| Deals or opportunities | Moves well | Old stages mapped to new ones; closed deals kept if you report on win rates |
| Notes, calls, emails and meetings | Possible, depending on the destination's import options | Correct links to contacts and deals, with original dates and owners preserved |
| Attachments and files | Often the slowest part | Storage in the new system, or an archive with links from the records |
| Users and record owners | Simple mapping | What happens to records owned by people who have left |
| Custom fields and objects | Depends on the destination and plan | Whether the new CRM supports them on your subscription; HubSpot custom objects require Enterprise |
| Automation, templates and reports | Not migrated as data | Rebuilt in the new system, usually simpler than before |
How do HubSpot, Salesforce and other CRMs handle imports?
Each platform has its own import rules, and the plan has to respect them. HubSpot deduplicates contacts on email address and companies on domain name, and can match rows to existing records by Record ID or a unique-value property. It will not merge a contact with no email or recognize three spellings of one company, so cleanup comes first.
Salesforce offers two main tools: the browser-based Data Import Wizard, capped at 50,000 records per import and limited to common objects such as accounts, contacts, leads and custom objects, and Data Loader for bigger volumes or objects the wizard does not cover. Dynamics 365, Zoho and other CRMs have their own tools and limits, and some history can only be moved through the API. Whatever the tool, it is tested on your data before the full run.
If the destination is still being configured, the migration and the setup should be planned together. See our HubSpot implementation and Salesforce CRM setup pages.
How is your customer data handled during the move?
We work inside your systems, with accounts you create and can switch off. Before any export we agree where working files are stored, who can access them, and when working copies are deleted at the end. We migrate only the fields you need; sensitive fields you no longer use can be left behind rather than copied forward.
If your business has specific obligations, for example under California privacy law or an industry regulation, tell us on the first call. We will build the migration around your policies; we do not replace your own compliance review.
When you do not need a migration project
If you are moving a few thousand contacts from one clean spreadsheet with no deal or activity history, the new CRM's own import tool is probably enough. A short mapping review before you press import may be all the help you need, and we will tell you that on the call.
At the other end, if the old data is so unreliable that nobody would trust it after the move, the better answer can be a fresh start: migrate active customers and open deals, and keep the rest in a searchable archive.
Why work with Lightray on a CRM migration?
A migration succeeds when the new CRM is set up to receive the data and the reports built on it still add up. We handle all three parts, the destination setup, the move itself and the reporting afterward, so nothing falls between vendors and no one has to referee between a CRM installer and a data contractor.
- Senior-led: Edward Pinela, MBA writes the mapping, runs the loads and reconciles the results. No hand-off to junior staff.
- Both sides of the move: we configure the destination CRM as part of our CRM consulting services, so fields and stages are ready before the data arrives.
- History you can still report on: when years of closed deals matter for trend reporting, we can keep them analyzable in Power BI even if they stay out of the new CRM.
- Proof, not promises: a 4.9★ Google rating and 20+ years of experience across 200+ delivered projects, with a reply within 4 business hours when you reach out.
Further reading: HubSpot Knowledge Base: how HubSpot deduplicates records.
Planning a CRM switch? Get the migration plan first.
Book a free 30-minute call with Edward Pinela, MBA. You get an honest read on what to fix first — and if we are not the right fit, you will hear that on the call.
Frequently asked questions
How long does a CRM data migration take?
It depends on the number of objects, the volume of records and history, the condition of the source data, and how much the new CRM's structure differs from the old one. Cleanup and mapping usually take longer than the load itself. You receive a written plan with milestones after the inventory, and the cutover is scheduled around your sales calendar.
Can we keep using the old CRM while you migrate?
Yes. Your team keeps working in the old system through the test load and the full load. At cutover we take a final delta of records created or changed since the full load, then set the old system to read-only until you sign off on the new one.
Will we lose our activity history?
Not if it is in scope. Notes, calls, emails and meetings can usually be migrated and linked to the right records with their original dates, though what is possible depends on the destination's import options. Where history cannot move cleanly, we agree an archive you can still search.
Is the migration done remotely, and what do you need from us?
Yes. The whole migration runs remotely, with the mapping review and sign-off done together over video and screen share. We need admin access to the old and new systems (or exports from the old one), a list of users and who replaces anyone who has left, and one person who can sign off the mapping. We can move data from spreadsheets, Outlook or Google contacts, and most CRMs that export data or offer an API, including HubSpot, Salesforce, Dynamics 365, Zoho and Pipedrive.
What does a CRM data migration cost?
Cost follows the number of objects and records, the amount of cleanup, how much history and how many files are moving, and whether the destination CRM also needs configuring. You receive a written, itemized scope after the free strategy call, before any data is touched.
You Won’t Get Handed Off to Junior Staff.
At most consulting firms, the senior person who sold you shows up for the kickoff — then you get handed to a team of juniors learning on your dime. That’s not how we work.
When you hire Lightray Solutions, you work directly with Edward Pinela, MBA — a principal consultant with 20+ years of experience across Power BI, web development, SEO, and CRM systems. Edward architects every engagement personally, stays involved through delivery, and answers his own phone.
Read Edward’s Full Bio“Mid-market companies deserve senior-level expertise without paying enterprise-agency prices. That’s the gap Lightray fills.”
Simple. Transparent. Proven.
No black-box processes. No endless discovery phases. A straightforward three-step approach designed to deliver measurable results fast.
Discovery Call
Free 30-minute strategy session where we assess your data landscape, website, marketing — and where AI would genuinely pay off versus where it's hype.
Free · No ObligationCustom Roadmap
You receive a tailored plan with clear deliverables, realistic timelines, and expected ROI. You approve every detail before we start.
Fixed Scope · Clear PricingMeasurable Results
We execute, measure, and optimize. You get dashboards, regular check-ins, and full visibility — so you always know the impact.
Data-Driven · TransparentGet a clear plan in one free call.
Tell us what you are trying to fix. Your request goes to Edward Pinela, MBA — the principal consultant who would do the work — and you hear back within 4 business hours.
Prefer to call? +1 (714) 872-9606