CRM migration lessons from Salesforce and HubSpot projects: make the first 30 days count
Across Salesforce and HubSpot migrations, the patterns repeat. The stacks change and the mistakes do not. Most of them trace back to decisions that belonged in the first 30 days and were made in the last 30 instead. Here is what to settle early.
Share article

A CRM migration goes well or badly in its first 30 days. The data load is rarely the hard part; the hard part is the decisions teams defer in the first month, about scope, history, process design, freezes, automation, access and backups, which come back in the final weeks when every change costs the most.
Across the Salesforce and HubSpot migrations we have run, the tech stacks change and the vendor names change. The mistakes do not. For a CEO or CFO the cost shows up as a go-live that slips by a quarter, a sales team working in two systems, and a forecast nobody trusts during the switch. For the RevOps lead running the project, here is what keeps going wrong and what works.
Most CRM migration problems are discovery problems
The decisions you defer in week one set the blast radius of everything that follows. If you are still mapping objects in month three, you started too late. Scope creep is rarely a planning failure. It is a symptom of incomplete discovery.
Get a full data and report inventory done before anything else. List every object, every custom field and every report anyone depends on, with its fill rate and when it was last used. Mark the fields nobody uses as candidates for deletion, because a migration is the cheapest moment you will get to remove them. Our guide to CRM database design covers what the target data model has to hold.
Then answer the history question in writing. How far back do you migrate cases, activities, campaigns, contracts and attachments, and what is archived instead? This one answer drives volume, timeline and tool selection. Agree retention by record type with legal and finance rather than defaulting to keeping everything. Lock the answer, get sign-off and move on, because debating it in month four costs weeks.
Decide whether to migrate as-is or redesign each process
This is the most consequential call in any Salesforce or HubSpot migration. Choosing to redesign a complex process halfway through compounds complexity in every direction. New fields reopen old automation decisions, new automation reopens old reporting decisions, and the migration quietly becomes a re-implementation.
Our Five Dots knowledge base uses a simple triage for this. Walk the customer journey end to end with the people who run it and give every process one colour.
- Green processes migrate as they are, because they work and users are satisfied.
- Yellow processes are right in principle and need minor rework, such as simpler record types, approvals or fields.
- Red processes do not fit how the business works and need a workshop with users before anything is built.
- Grey processes do not belong in the CRM at all and move to the product, another tool or nowhere.
Then run two streams. A lift stream migrates the greens and yellows quickly to secure the core. A redesign stream takes the reds through user workshops. Some reds will not fit before the deadline, so name them, keep a temporary workaround and schedule them for after cutover rather than rushing a weak design. Write each call down in a sentence, such as "lead routing migrates as-is, deal stages get redesigned, the renewal workflow migrates as-is." Avoiding hard calls, so that everything comes out yellow, just pushes the redesign into the build.
"We'll figure it out later" is how a six-month project becomes a twelve-month project.
Declare a development freeze on the old CRM, in writing
Once migration prep begins, new development in the source system has to stop. That covers custom fields, automations, layouts, integration tweaks, validation rules and page layouts. Otherwise you are migrating a moving target.
Agree the freeze date up front with every affected team. Anything built after the freeze lives outside the migration. If a truly urgent change appears, route it through change control with one owner and a written approval trail. Informal quick adds after the freeze cost more in testing time than the changes themselves.
Bring compliance, legal and finance in during discovery
Teams skipped during scoping show up in the final week, when changes cost the most. Finance, legal and compliance consistently surface requirements late. Typical examples are audit dependencies on opportunity data, separate agreement objects used by legal, ARR field definitions that differ from what RevOps assumes, and retention rules tied to regulatory obligations. Each of these is cheap to handle in week two and expensive in week twenty.
Run a compliance and legal requirements workshop during discovery. Map every regulated data element and document who owns it. Keep a stakeholder list that includes the quiet teams, not just the ones who showed up to the kickoff.
Audit every automation before you move a record
Most CRMs carry years of undocumented automation. Workflows built by someone who left two years ago are still firing in production and quietly touching records.
Inventory all of it, including workflow automations, assignment rules, validation rules, scoring logic, field triggers, sequence enrolments and third-party integrations. For each one, record what it does, why it exists, who built it, when it last changed and how critical it is. Then make one call per automation.
- Migrate it as it is.
- Rebuild it for the new platform.
- Retire it.
Automations that "probably still do something useful" and get migrated by default are how complexity moves from one system to another without ever being resolved. Watch for automations whose conditions name specific record types, because every one of them breaks when record types are merged. Size the rebuild work as its own workstream. Logic that took five minutes to configure in one platform often needs a different approach in another, so it is not a final-sprint task. If HubSpot and Salesforce will run side by side for a while, our HubSpot and Salesforce integration guide covers what to prepare before you connect them.
Treat deduplication as a workstream, not a final-week cleanup
Duplicate data is always worse than expected, and when you consolidate several systems, duplicates compound. In our client work we have seen duplicate spikes traced back to an earlier mass migration and to target-account uploads, so the cleanup often starts with the last project's leftovers.
The sequence matters. Clean each source separately first, then reconcile the combined dataset. Skipping the first step produces merged duplicates that carry conflicting field values nobody can untangle afterwards. Match on more than names. Use domains and company relationships, and preserve activity history and contact-to-account associations when you merge.
Know how the target platform behaves on import. HubSpot, for example, deduplicates contacts by email address and companies by domain name when you import, but companies created through the API are not deduplicated by domain. A load script that ignores that difference creates the duplicates you just cleaned. Our walkthrough of updating a CRM with Python without creating duplicates shows the matching logic in practice.
Build deduplication in as a named workstream with an owner, a timeline and a clear definition of done.
Align the security and access models before testing
A heavily restricted, territory-based model and an open, role-based model cannot simply be merged. Pretending they can produces a testing phase where half the users cannot see their own records and the other half can see everything.
Run a security model workshop in discovery. Map each system's access model side by side, identify the conflicts, pick a target model and document the decision and the migration path. Do this before testing starts. The sharing model also affects load speed. Salesforce's Large Data Volumes module on Trailhead notes that sharing is recalculated as records are added under a private model, which slows large loads.
Plan the load order and the rules you switch off
Data has dependencies. In Salesforce, child records cannot be loaded before their parents exist, and record owners have to exist before the data they own. Import parents before children, keep a mapping of old to new record IDs, and remember that auto-numbered records such as cases and contracts take their numbers in import order. Get that wrong and the sequence has gaps that are slow to fix. Files, attachments and knowledge articles are usually the slowest part, so confirm they are needed before you migrate them.
Teams often deactivate validation rules, assignment rules and triggers to speed up a large load, as the same Trailhead module describes. That is fine as long as the step to turn them back on is on the checklist. Rules disabled during the load have to be re-enabled systematically, and the data has to be checked against them, because records that skipped validation will not fix themselves.
Protect testing time and keep one UAT template
When a migration runs late, testing is the first thing squeezed. It should not be. If the data migration runs over, the go-live date moves and testing time stays fixed. Agree this as governance before the project starts, not as an argument you lose after the schedule slips. Budget user licences and time for user acceptance testing well before cutover.
Two testing traps are worth naming. Staging is not production. Layouts, validation rules, user profiles and disabled workflows all drift between environments, so keep a staging-to-production change log and review it before every go-live checklist. And UAT needs one template. Discovering that one team has an excellent template while everyone else improvised is a quality control failure. Standardise the template at kickoff, covering objects, fields, automations, integrations and user roles, and apply it the same way across every team.
Back up data and configuration more than once
A single backup at kickoff is not a backup strategy. Take named checkpoint exports throughout the project.
- A pre-migration baseline, with data and configuration exported separately.
- An export after deduplication.
- An export after each object group is loaded.
- A final export before go-live.
Label each one with a date and a description. These become your rollback points when something breaks downstream.
Data and configuration need separate backups. A data export does not cover automations, field definitions, page layouts or permissions. Salesforce's native Data Export Service, for instance, produces a zip archive of CSV files and can run once every 7 days for a weekly export or every 29 days for a monthly one, with attachments only if you select them. Scheduled native exports kept in restricted shared storage can be enough if your restore needs are modest. Specialist backup products mainly make restoring easier.
Test your restore. A backup you have never restored is a backup you do not actually have, so run a sample restore from the baseline before you need it. Store exports in a shared, access-controlled location with a naming convention that still works if the project lead is on holiday when an incident hits.
Build visible buffer into the timeline and write down Plan B
Experienced CRM implementation leads are sceptical of aggressive go-live dates for good reason. If a licence expiry date sets your deadline, work back from it and leave weeks, not days, between the planned cutover and the expiry for delays, fixes and support. Label that buffer in the plan. Hidden buffer gets spent on optimism, while labelled buffer survives.
Pick the cutover date with the sales calendar in mind. Cut over when sales pressure is lowest, often right after a quarter close, not in the last weeks of a quarter. Keep a small number of licences on the old system for a period after cutover, read-only, so people can still reach history while the new system settles.
Before go-live, write down Plan B. What happens if you need to extend the freeze, push the go-live date, pre-migrate non-critical objects and hold the rest, or cut scope? Decide the criteria now, write them down and share them with the steering committee before the decision matters.
If you want help setting up these first 30 days, our HubSpot and Salesforce implementations start with discovery, the data model and the migration plan, built alongside your own team.
Keep one decision log and enforce it
Decisions made in meetings need to be recorded, and everyone needs to use the same place. Notion, Confluence, Jira or a single shared doc all work, because the tool matters less than the discipline. Pick one, establish the protocol at kickoff and assign someone to enforce it. Make documentation a prerequisite for closing any decision.
When decisions live in three tools, two Slack threads and one person's head, they get relitigated, and relitigated decisions are where timelines go to die. Keep decision authority with a small core team as well. Broad sign-off rounds slow every decision down, and decision speed is the main risk in a migration.
Why CRM migration mistakes trace back to the first 30 days
Every lesson here has the same root cause. Decisions that belong in the first 30 days get made in the final 30 days instead. Discovery, history and retention, migrate or redesign, the freeze, the automation inventory, the stakeholder map, the security model, the load order, backups, buffer, Plan B and one decision log all belong at the start.
Settle them before anyone touches a record and the migration gets easier. If you are still choosing the platform, our HubSpot vs Salesforce comparison covers that decision first. If you are starting a migration this quarter, book a call and we will help you plan the first 30 days.
Frequently asked questions about CRM migration
What should happen in the first 30 days of a CRM migration?
The first 30 days should settle scope and history, the migrate-or-redesign call for every process, the development freeze, the automation inventory, the stakeholder and compliance map, the security model and the backup plan. Building and loading come after those decisions, not before.
Should we migrate all historical data to the new CRM?
Usually not. Agree a history cutoff by record type with legal and finance, migrate what people actually use, and archive the rest in restricted storage where it can still be retrieved.
Should we deduplicate before or after a CRM migration?
Deduplicate before and during the migration. Clean each source system first, then reconcile the combined dataset, so you do not load merged duplicates with conflicting values into the new CRM.
What is a development freeze in a CRM migration?
A development freeze is the date after which nobody builds new fields, automations, layouts or integrations in the old CRM. Anything urgent goes through change control with one owner and a written approval, so the team is not migrating a moving target.
When is the best time to cut over to a new CRM?
Cut over when sales pressure is lowest, which is often right after a quarter close. Leave a buffer of weeks before any licence expiry date, and keep read-only access to the old system for a while after go-live.
What should a CRM migration backup include?
A migration backup should include data and configuration, exported separately, at several checkpoints. Take a baseline before the migration, then exports after deduplication, after each load and before go-live, and test a restore from the baseline before you need it.
