If you’ve ever been in the middle of a Salesforce implementation, you know this question is coming:

“Are we migrating everything?”

And that’s usually when the room goes quiet.

Because technically, yes — you can migrate everything. But strategically? You probably shouldn’t.

One of the biggest mistakes I see during Salesforce implementations isn’t technical. It’s prioritization. Teams treat migration like a storage exercise instead of a revenue decision. The real question isn’t how much data you can move. It’s what data actually needs to exist in Salesforce on day one to keep revenue moving.

If you’re thinking about overall implementation planning, we recently covered how sequencing impacts rollout timing in our article on How Long Does It Take to Implement Salesforce?. Data migration strategy plays a major role in whether your go-live feels controlled or chaotic.

Let’s talk about what should come first.

Start With What Protects Active Revenue

When implementing Agentforce Sales (formerly Sales Cloud), the priority is not historical reporting depth. It’s continuity.

Active accounts.
Active contacts.
Open opportunities.

If a rep logs in after go-live and their live pipeline is missing or incomplete, adoption drops immediately. Salesforce only works if it reflects the current state of revenue. Everything else is secondary.

Revenue operations exists to protect execution. If the system interrupts the selling motion, trust erodes fast.

Clean Before You Move

Migration is not copy and paste. It’s curation.

Salesforce emphasizes data quality and governance in its Data Management Trailhead module for a reason. If you import duplicates, inconsistent lifecycle stages, and undefined fields, you’re not just moving data — you’re scaling confusion.

Before migrating anything, ask:

• Is this data accurate?
• Is it standardized?
• Does it support a defined process?
• Will anyone actually use it?

If a field doesn’t tie to a reporting need or workflow, it probably shouldn’t make the move.

Clean data builds trust. Trust drives adoption.

Open Pipeline Before Historical Deals

Once accounts and contacts are solid, prioritize open opportunities.

Closed-won deals from five years ago are helpful — but they don’t matter more than the deals currently in motion. Leadership still needs forecast visibility. Sales managers still need stage integrity.

Salesforce outlines practical migration tools in its Import and Export Data Trailhead module, including Data Import Wizard and Data Loader. The mechanics are straightforward. The sequencing is the strategic part.

Stabilize the current funnel first. Then bring in historical opportunities to enhance reporting once the foundation is stable.

Be Strategic With Marketing Data

If your rollout includes Agentforce Marketing (formerly Marketing Cloud), there’s often pressure to migrate every historical campaign interaction.

Pause.

Does your team need five years of email opens on day one? Or do they need clean lead routing, lifecycle definitions, and accurate attribution going forward?

In many cases, rebuilding attribution logic inside Salesforce is healthier than importing legacy complexity.

This becomes even more important if you’re using Data 360 (formerly Data Cloud) to unify profiles across systems. Data unification is powerful — but it only works well when the underlying records are standardized. Migrating inconsistent marketing logic into a unified model just scales confusion.

Forward-looking structure is more valuable than backward-looking clutter.

Layer in Customer and Renewal Data Next

After acquisition data is stable, bring over active customers, contract terms, renewal dates, and current case data.

If you’re aligning sales and service workflows, this phase is critical. But again, sequencing matters. Trying to stabilize pipeline and service complexity at the same time can overwhelm users and extend timelines.

What Usually Doesn’t Need to Move Immediately

Inactive leads from years ago.
Custom fields no one can define.
Every historical activity record.

Just because Salesforce can store it doesn’t mean it should.

Every field you migrate becomes something you maintain. Every object impacts reporting architecture. A clean data model at launch prevents technical debt six months down the road.

Data Migration Is a Revenue Strategy Decision

It’s easy to treat migration like an IT task. But for Revenue Operations professionals, it’s a strategic decision about what the business needs access to immediately after go-live.

Prioritize active revenue.
Clean before you migrate.
Phase in complexity.

Salesforce is powerful. But its value isn’t measured by how much data you import. It’s measured by how intentionally you build the foundation.

And that starts with moving the right data first.