Moving business software feels exactly like moving apartments. You open a drawer you haven't looked at in three years and wonder why you kept an expired warranty for a broken toaster. A CRM data migration forces you to confront years of digital hoarding, and it is rarely pretty. If you just dump everything from your old database into your new one, you will carry all that mess with you, and your new system will be just as cluttered as the old one. You need a strict process to move your information so that nothing gets lost and everything actually works on Monday morning.
What you need before you start
Do not start clicking export buttons yet. Set up a comfortable workspace and gather your tools before touching any live data.
You will need full admin access to both your old and new CRMs. You also need a dedicated afternoon where nobody expects you to answer Slack messages or put out fires. Close your tabs. Get a large monitor if you have one. You will spend a lot of time looking at a spreadsheet tool like Excel or Google Sheets, and toggling between small windows is exactly how mistakes happen.
Treat this like a surgical operation. You want total focus.
Step 1: figure out what to keep and what to ditch
Moving an empty shell of a lead from a 2018 trade show just clutters up your new system. That contact has not replied to an email in six years, and they probably do not work there anymore anyway. Business contact data decays at an average rate of 22.5% per year.
Here is the trick for figuring out what stays and what goes. Filter out anything you haven't interacted with in two years. You only plan to migrate active customers, open deals, and key contacts who are actually engaging with your sales team.
Archive the rest. Download the inactive records as a CSV file, name it "Legacy Archive," and put it in a secure cloud folder. You still own the history, but it will not ruin the search results when your reps look for active buyers.
Step 2: lock down a secure backup
Before you change a single cell, export your entire current database as a CSV file and save it somewhere safe.
This gives you a guaranteed reset button if things get messy. A failed migration without a backup is completely unrecoverable, meaning your sales team will wake up to an empty pipeline. Do not trust the cloud to just hold onto it for you. Download a hard copy of your contacts, companies, deals, and notes. Store it on a local drive and a secure company server.
Do this right now. Never start cleaning data in your live environment without this safety net securely in place.
Step 3: map your old fields to your new home
Every software platform names things slightly differently. What one system calls a "Stage," another calls a "Pipeline Status." What your old database labels "Account Name" might need to become "Company Name" when the basic mechanics of your database change.
You have to create a simple cheat sheet matching the exact fields in your old database to the ones in your new setup so nothing gets lost in translation.
Open a blank spreadsheet. In column A, list every field from your old CRM. In column B, list the exact matching field in your new CRM. When you find a field that does not have a native equivalent, mark it in red. This forces you to make a conscious decision about whether to create a custom field for it or drop it entirely.
Implementation partners cite data mapping and cleanup as the primary cause of 54% of timeline delays during migrations. Taking the time to build this map prevents your data from landing in the wrong columns.
Deal with the custom fields you actually use
If your team relies on a custom drop-down for "Industry," recreate it in the new CRM right now. Match the spelling perfectly.
Skip the fields no one has touched since you launched the company. If there is a checkbox for "Attended 2019 Webinar" that applies to exactly four people, let it die. Your goal is a lean workspace, not a historical museum of every idea your marketing team ever had. Create only the custom fields that directly drive your current reporting and daily sales activities.
Step 4: clean up duplicates and junk data
Post-migration cleanup is a nightmare, so fix the typos and merge the duplicate John Smiths while the data is still in a spreadsheet.
A typical B2B database contains 10-30% duplicate records that require fuzzy matching to find. If you import those duplicates into a new environment, they will trigger double automations. Your top client will get the same welcome email twice, and they will notice.
Use fuzzy matching tools or Excel formulas that catch similar spellings rather than exact matches. This spots the hidden duplicates you would otherwise miss. "Acme Corp" and "Acme Corporation" need to become one single row before they touch your new software.
Standardize your formatting while you are in the spreadsheet. Make sure all phone numbers use the same format. Ensure states are spelled out completely or all abbreviated to two letters. You want this data spotless.
Step 5: set up your new CRM skeleton first
You cannot assign a deal to a sales rep who does not exist in the new system yet.
Add your team members as users and configure their permissions before you import a single contact. This is the bedrock of getting your new system off the ground. Go into the settings panel and invite your sales reps, your managers, and your marketing team.
Set up the roles. Decide who can delete a contact and who can only view them. Build your sales pipelines and create your specific deal stages. When you eventually pull your data in, the information needs a structural home. If the rooms are not built, the furniture just piles up in the hallway.
Step 6: run a small pilot test
Pick 100 contacts and push them through the migration process to see what breaks.
It is much easier to fix a mismatched email column on a tiny batch than to untangle 10,000 broken records. Choose a diverse sample for this pilot. Include a few complex accounts with multiple contacts, some deals in different stages, and a handful of custom fields.
Run the import. Then, log into the new system and look at those 100 records. Did the notes attach to the right person? Did the phone numbers format correctly? Did the deal owners transfer over, or is everything assigned to you by default?
Industry data reports 98% success for phased approaches compared to big bang cuts. Find the errors now, fix your spreadsheet, and test again until that small batch imports perfectly.
Step 7: call a hard stop on the old system
Pick a specific Friday afternoon and tell your team to stop adding notes or updating deals in the legacy CRM.
This cut-off date prevents new information from slipping through the cracks while you move everything over. If a sales rep logs a crucial discovery call on Friday at 4 PM, but you exported the data at noon, that note is gone forever.
Send an email to the entire company clearly stating that the old database is frozen. They can look at it, but they cannot edit it. Any notes they take during the migration window need to go into a temporary Word document or notebook until the new system is live.
Step 8: load the data in the exact right order
CRM relationships are fragile, and loading data out of order is exactly how you end up with deals attached to nobody. Always follow the hierarchy.
If you load deals before contacts, the database does not know who the deal belongs to. It creates an orphaned record floating in the void. You have to build the containers, then put the people inside the containers, then attach the money to the people.
Here is the exact sequence you must follow.
Import companies first
Get the businesses into the system to start. This creates the foundational buckets that everything else will sit inside.
Take your clean spreadsheet of accounts and run the import. Check that the company names, websites, and billing addresses land in the correct fields. The system will assign a unique internal ID to each of these companies. You will use these company records to anchor everything else you import next.
Import contacts next
Now pull in the actual people, making sure to link them to the companies you just uploaded.
The new CRM usually relies on email domains to make these connections stick. If John works at Acme Corp, the system looks at his "@acmecorp.com" email address and automatically places him inside the Acme Corp bucket you created in the first step.
Make sure your spreadsheet has a dedicated column matching the contact to their employer. If someone uses a Gmail address, you will need to map them to their company manually using the unique company ID or an exact name match.
Import deals and opportunities
Move your active pipelines over, tying each deal back to the specific contact and company it belongs to.
This is where the money lives, so pay attention. Your deal spreadsheet must include columns that explicitly state which company and which contact the deal is for. It also needs to show the deal amount, the current pipeline stage, and the expected close date.
Verify that the pipeline stages in your spreadsheet exactly match the stages you built in Step 5. If your spreadsheet says "Contract Sent" but your new system says "Proposal Out," the import will reject the rows or create messy duplicate stages.
Import notes, activities, and attachments
Bring in the history, including the logged calls, meeting notes, and files.
This is the hardest part, but it is what keeps your sales team from flying blind on Monday morning. Notes are tricky because they need to map to a specific timestamp, a specific author, and a specific contact.
Format this file carefully. Every note needs a column for the date it was created, the body text of the note itself, and the email address of the contact it belongs to. If you skip this step, your sales reps will have no context for their follow-up calls, and they will hate the new software immediately.
Step 9: reconnect your daily integrations
Re-link your team's email inboxes, calendars, and accounting software to the new CRM.
Most cutovers break at least one integration, so send a test email to yourself to make sure it logs correctly. If your sales team expects their Gmail replies to automatically show up in the contact record, you have to establish that connection before they log in.
Go into the integration settings and authenticate your workspace. Book a fake meeting on your calendar and watch to see if it populates the database. This is a critical step in getting your team to log in and trust the new setup. If they have to manually log their emails on day one, you will lose their buy-in immediately.
Step 10: validate the relationships, not just the rows
Do not just check that you imported 5,000 contacts and 5,000 showed up.
Click into a random deal and verify that the associated contact, company, and past meeting notes are all exactly where they should be. Scroll down to the activity timeline. Does it show the email you sent them last month? Is the deal value correct? Is the right sales rep assigned as the owner?
Check ten random records across different territories and pipeline stages. Look at a brand new lead. Look at a closed-won customer. Look at a deal that has been stalled for three months. If the relationships are intact, the migration was successful. If the data is there but disconnected, you need to delete the batch and run the import again with corrected mapping.
How to fix common migration hiccups
Things rarely go perfectly on the first try, and that is completely fine. Do not delete your entire account in a panic. Here is how to handle the most frequent roadblocks without losing your mind.
What to do when deals lose their owners
If imported deals show up as "unassigned," check your user mapping.
The old CRM might have used a username like "jsmith" while the new one demands an exact email address like "john.smith@company.com" to assign ownership. If the system does not recognize the owner format in your spreadsheet, it defaults to leaving the deal blank or assigning it to the admin who ran the import.
To fix this, go back to your spreadsheet. Do a simple find-and-replace on the "Owner" column, swapping all the old usernames for the correct email addresses of your sales reps. Run an update import based on the record IDs to reassign the deals to the right people.
How to fix broken integration syncs
When calendar invites stop logging, disconnect the integration entirely and set it up fresh.
A clean reconnection solves the vast majority of API glitches. Software tokens expire, and sometimes a migration triggers a security protocol that pauses data syncing. Do not waste hours digging through developer documentation. Just revoke the access in your email provider, go back into the CRM, and click "Connect Calendar" again.
If your accounting software is duplicating invoices, turn off the two-way sync immediately. Proving the value of your software investment becomes impossible if your revenue numbers are artificially doubled. Set the integration to one-way sync from the accounting software to the CRM, rather than letting the CRM overwrite your financial ledger.
The morning after and your next steps
Keep your old CRM alive but in read-only mode for two weeks just in case someone needs to verify an old note.
Inevitably, a rep will swear a specific phone number was lost in the move. Having the old system accessible lets them check for themselves, and usually, they realize the number was never there to begin with.
Invite your team to log in, poke around, and try updating just one deal today to get the feel for their new workspace. Have them send one tracked email. Have them move one deal stage. Start small, let them build muscle memory, and close the legacy archive for good.