Did You Just Migrate Your Bad Habits Into a New CRM?

Uh oh. You did all that work — the planning, the late nights reconciling Salesforce records nobody could explain, the endless field mapping — and six months later you’re staring at the same problems in a shinier interface.

Don’t feel bad. It happens to almost everyone. And it’s seldom the CRM’s fault.

Here’s what nobody tells you before a Salesforce to HubSpot migration: the technology is the easy part. The hard part is recognizing that you’ve just been handed one of the rarest opportunities in RevOps — a genuine clean slate — and knowing what to do with it before the window closes.

What Is a CRM Migration, Really?

Most teams treat a CRM migration as a technical project: map the fields, deduplicate the records, get the integrations talking, flip the switch. Done. 

Except six months later, sequences are going to the wrong people, email deliverability is underperforming and sales reps have already stopped trusting the data.

A CRM migration is not just a data move. It’s a decision about the foundation underneath everything else. Treat it like a lift-and-shift and you carry everything over, including years of accumulated bad habits, stale contacts and inherited assumptions about what should trigger outreach. You’ve moved the furniture into a beautiful new house. The furniture is still ugly.

How Do You Actually Use a Clean Slate?

When we partnered with a client on a recent Salesforce to HubSpot migration, the technical work was just the starting point. The decisions that actually moved the needle happened across five areas.

1. Deliverability triage before anything goes live.

Not every contact in a migrated database deserves a spot on your active send list. We built workflows to segment hard bounces immediately, but the more interesting challenge was the gray area: contacts with uncertain deliverability status. Rather than suppressing them wholesale or blindly including them, we ran a deliberate test, adding them in controlled groups to real newsletter sends and sequences, then letting actual engagement behavior determine their fate. Opens, clicks and replies earned a place on the list. Everyone else was set to the appropriate marketing contact status and removed from active sends.

One bounce across 3,837 sequence enrollments. That number doesn’t happen by accident. That’s deliberate architecture.

2. Send-time optimization that actually has something to work with.

We use Seventh Sense for HubSpot email send-time optimization. Here’s what’s worth understanding about how it works: Seventh Sense learns from engagement history. Train it on sparse or unreliable data, and it confidently delivers emails at exactly the wrong time. Starting with a clean, validated list meant the tool performed the way it was designed to. A 36.88% open rate across a sequence audience reflects that foundation.

3. What is Enrollem, and why does it matter for HubSpot sequence enrollment?

One of the best parts of starting fresh is not inheriting someone else’s assumptions about what should trigger outreach. We rebuilt sequence enrollment criteria from scratch using Enrollem, a HubSpot app by Ogham Works that automates sequence enrollment via workflows without requiring an Enterprise portal. This unlocked something specific: the CEO could send what looked and felt like genuine personal 1:1 sales emails via sequence, at scale, without upgrading their HubSpot tier. Here’s a quick walkthrough of exactly how that works.

4. Data enrichment was added as the engagement matured.

We didn’t enrich everything upfront — that’s not always realistic, and it wasn’t how this engagement unfolded. Once the foundational infrastructure was running cleanly, we layered in data enrichment to fill gaps in contact and company records. That enrichment now drives task prioritization, so the sales team is working the right accounts in the right order rather than choosing arbitrarily. The lesson: enrichment doesn’t have to be a prerequisite to getting started. It just needs to happen before you build strategies that depend on it.

5. What do the results actually look like?

Across 2,587 contacts and 1,348 companies: 36.88% open rate, 3.21% click rate, 0.03% bounce rate, 41.69% company engagement rate and 21 meetings booked. These are sequence performance numbers, meaning they reflect sustained deliberate outreach against a clean, enriched, well-segmented database. Not a one-time blast. Not a fluke.

Why Does This Window Close So Fast?

The moment your team starts operating in the new system, entropy begins. Pipelines get tweaked. Fields get added. Reps start logging activity in ways that drift from whatever was carefully designed at launch. Within a few months, you have a new CRM accumulating the same old problem: multiple versions of the truth are building up while your dashboards look perfectly fine.

The teams that get the most out of a migration treat the clean slate as a forcing function — not just for data hygiene, but for finally making decisions that kept getting deferred. What does a qualified contact actually look like? What behavior should trigger outreach? What data do you actually need versus what you’ve just been collecting out of habit?

A migration forces those conversations. The question is whether you use that pressure productively or sprint back to business as usual.

What Does a CRM Migration Have to Do with AI?

If you’re investing in AI-powered tools — and you probably are, or soon will be — this is the part that matters most. AI amplifies whatever signal you give it. Clean data produces compounding results. Messy, semantically unstable data produces confidently wrong outputs at scale, with full executive buy-in, backed by dashboards that look completely reasonable.

A migration is the one moment where you can make a deliberate choice about which of those you’re setting yourself up for. You’re not untangling years of drift. You’re deciding what the foundation looks like before the system runs.

That decision compounds over time, in one direction or the other.

Want to see the full story? We put together a case study on this exact engagement — the migration, the deliverability infrastructure and the results. Read it here.

If you’re planning a Salesforce to HubSpot migration, or you’re already on HubSpot and not seeing the results you expected, this is usually where it starts. Let’s talk.