Pressing Import is the easy part of switching CRMs. The real work is deciding what must survive, how records relate, and which parts of the old system need to be rebuilt. A contact CSV may contain names and email addresses but omit notes, files, deal relationships, consent history, or the automations that keep leads moving.
This guide explains how to switch CRMs without losing your data, from the first inventory through the final validation. If you are still choosing the destination, start with the CRM alternatives directory and compare the platforms that fit your shortlist. The migration plan should influence the buying decision before you sign.
First, define what “your data” includes
Before exporting anything, inventory every object, relationship, file, and process your team depends on.
| Area | Examples to inventory | Why it gets missed |
|---|---|---|
| Core records | Contacts, companies, leads, deals, opportunities | Often spread across separate modules |
| Relationships | Contact-to-company links, deal participants, parent accounts | A flat CSV can break these connections |
| History | Notes, emails, calls, meetings, tasks, SMS conversations | Frequently exported through separate tools |
| Files | Quotes, contracts, photos, attachments | May require a full backup or separate archive |
| Structure | Custom fields, pipelines, stages, tags, owners | Field names and data types differ by CRM |
| Permissions | Teams, roles, record visibility | Usually configured rather than imported |
| Operating logic | Workflows, forms, calendars, integrations, reports | These normally need to be rebuilt and tested |
| Compliance data | Consent, opt-outs, suppression lists, retention flags | Losing it can create legal and deliverability risk |
Do this with the people who use the system. Sales may care most about deal history, while service needs appointment notes and finance needs quote or invoice references.
What usually transfers, and what needs rebuilding
Most modern CRMs can import basic records from CSV or XLSX files. Many can also import deals, notes, activities, products, and relationships when the files include the right identifiers. The details vary by platform.
For example, HubSpot’s official record-export documentation says its standard export contains current property values and associations, while contact activities such as calls and notes use separate export methods. Pipedrive likewise exports activities, notes, and files separately, even when they are linked to deals or contacts. In Salesforce, the administrator must select options to include images, documents, attachments, Salesforce Files, and content versions in a backup export. Zoho distinguishes a module export from a complete backup, which is the option that includes attachments and configuration details.
Those examples make the practical rule clear: never assume that Export Contacts means Export Everything.
Basic records are the most portable. Relationships, history, files, custom objects, owners, and consent fields need closer inspection. Workflows, forms, reports, integrations, connected inboxes, phone settings, and permissions are configured systems. Plan to rebuild them unless your migration provider confirms a supported transfer.
How to switch CRMs in nine steps
1. Choose an owner and a cutover rule
Put one person in charge of the checklist, file versions, test results, and final go/no-go decision. Department leads can validate their data, but one owner should approve the cutover.
Decide early which CRM will be the source of truth during each phase. If both systems remain editable without a rule, the databases will drift and your final import will already be outdated.
2. Export a complete backup before cleaning anything
Use an administrator account with permission to see all records. This matters because export tools may respect the user’s record visibility. Pipedrive, for example, notes that a user can export only data visible to that user, even when export permission is enabled.
Request the fullest account backup available, including attachments and custom objects. Export important modules separately for practical working files. Save every original in a dated, access-controlled folder and do not edit it.
Open each archive immediately, spot-check it, and note which file holds each object. Export links can expire, so download everything promptly.
3. Create a working copy and clean that copy
Leave the raw export untouched. Clean duplicates, formatting, and obsolete records in a working copy so you can always return to the source.
Standardize phone numbers, state names, dates, currencies, country codes, and dropdown values. Decide how to handle missing emails, duplicate company names, and records owned by former employees. Keep source record IDs in their own columns so you can preserve relationships and trace imported records.
Do not delete opt-outs or suppression records because they look inactive. They are operational data, not clutter.
4. Build a field-mapping sheet
For every source column, document the destination object and field, data type, transformation rule, and whether it is required.
Pay special attention to:
- Custom dropdowns and multi-select fields
- Dates, time zones, and currency formats
- Contact owners and inactive users
- Deal pipelines and stage names
- Tags and lead-source values
- Contact-company and contact-deal relationships
- Consent, subscription, and do-not-contact fields
Create required custom fields before importing so useful information has a valid destination.
5. Configure the destination before loading records
Set up users, teams, permissions, pipelines, stages, custom fields, and basic account settings first. Record owners cannot map correctly if the users do not exist. Deals cannot land in the right stage if the pipeline has not been created.
Document terminology changes too, such as an “account” becoming a “company” or two old stages becoming one.
6. Run a representative pilot import
Do not test with ten perfect contacts. Include awkward records: duplicate emails, multiple companies, open and closed deals, custom fields, notes, attachments, international numbers, opt-outs, and former owners.
Modern importers provide useful controls when you take time to use them. HubSpot supports imports across multiple objects and activities with association mapping and deduplication keys in its multi-object import process. Pipedrive’s spreadsheet import workflow includes field mapping, a preview, duplicate handling, and a skip file for failed rows.
After the pilot, compare counts and inspect records inside the CRM. A successful upload message does not prove that owners, dates, links, and values landed correctly.
7. Import in dependency order
Load parent records before the records that depend on them. A common order is users and companies first, then contacts, deals, activities, notes, and files. Preserve the keys used to associate those objects.
Import one logical batch at a time and save every success and error report. Fix skipped rows before moving on. Smaller batches make bad mappings easier to isolate.
8. Rebuild and test the operating system around the data
Recreate forms, calendars, workflows, templates, integrations, webhooks, dashboards, and permissions. Use the new CRM’s native structure instead of cloning every old workaround.
Test with controlled records before enabling live messages. Submit key forms, book an appointment, create a deal, trigger follow-up, reply through the inbox, and confirm that opt-outs stop future messages.
9. Cut over, run a final delta import, and validate
Schedule the cutover for a quieter period. Pause edits in the old CRM, export records changed since the main migration, import that final delta, and switch forms, integrations, inboxes, and team activity to the new system.
Keep the old CRM read-only long enough to answer questions and verify history. After sign-off, retain the original exports according to your security and retention policy, then remove temporary files from personal devices and shared download folders.
When a parallel run is safer
A short parallel run is worth considering when the CRM controls booking, payments, dispatch, regulated records, complex automation, or several business units.
Parallel does not mean entering every update twice. Choose one system for new activity and keep the other read-only, or define a narrow group of records that moves first. Write the rule down. Two editable sources of truth create the duplicate and stale-record problems the migration is supposed to solve.
A direct cutover may suit a small team with clean data, a simple pipeline, few integrations, and a successful pilot. Let the test results decide.
The validation checklist before you cancel the old CRM
Compare totals by object, then sample different owners, pipelines, dates, and customer types.
- Contact, company, deal, activity, note, and file counts reconcile
- Contacts remain associated with the right companies and deals
- Open deal values, stages, owners, and expected close dates match
- Notes and activities retain usable timestamps and authors where supported
- Opt-outs, consent status, and suppression lists are preserved
- Custom fields contain the expected values and formats
- Forms, calendars, inboxes, phone numbers, and integrations point to the new CRM
- Automations trigger once, assign correctly, and stop when they should
- Reports use the right fields and date ranges
- Users can see what they need without seeing restricted records
Have each department sign off on its own workflow. The migration owner should not approve sales history on behalf of sales or appointment data on behalf of service.
If you are switching to SMBcrm
SMBcrm’s current migration offer covers contacts, pipelines, and notes at no charge on every plan. The team also helps rebuild automations and organize imported data. Onboarding and support include unlimited group training, an onboarding portal, and 24/7 chat, ticket, and Zoom support. Professional and Enterprise include four guided sessions; Startup customers can add them at signup.
Confirm the scope for your specific source system before cutover, especially for attachments, conversation history, custom objects, and third-party integrations. You can review the switching and alternatives pages or use head-to-head comparisons such as SMBcrm vs HubSpot, SMBcrm vs Salesforce, and SMBcrm vs Keap while you evaluate fit. For broader selection criteria, read how to choose a CRM and compare the full cost of a CRM, including migration and onboarding.
Make the move with a rollback plan
SMBcrm includes free migration help on every plan, guided onboarding, and a 60-day money-back guarantee so you can change systems with a documented path forward and a way back if the fit is wrong.
See plans & pricing or schedule a demo to review your migration scope with the team.
