- Template item
A CRM migration consultant owns the half of a CRM move that quietly breaks revenue when nobody scopes it: the data, lifecycle, consent, and attribution rebuild that lives inside the marketing stack. If your migration brief ends at "map the fields and move the contacts," you have a database project, not a CRM migration. The result is a go-live where sales records transfer cleanly, the inbox dies, lifecycle emails stop firing, and nobody can tell you where last month's pipeline came from.
This guide gives you the brief the engineers in the room will not write for you. You will get a scope definition, a seven-part marketing workstream checklist, a compliance table, a hiring model comparison, and a copy-paste consultant brief you can hand over on day one.
What a CRM migration consultant actually owns on the marketing side
A CRM migration consultant owns the marketing-system half of a CRM move: lifecycle and stage mapping, consent and subscription preservation, workflow and automation rebuilds, UTM and attribution continuity, template and sender identity, and QA against live traffic before cutover. The RevOps engineer owns the database. The consultant owns everything downstream of the database that marketing touches.
Here is the scope you should expect them to carry:
- Lifecycle and stage mapping. The source system's definition of "MQL" or "lead stage 3" rarely maps 1:1 to the target. The consultant audits the taxonomy, proposes the target state, and runs the swap record by record.
- Consent and subscription preservation. Every email subscription state, opt-in level, legal basis, and timestamp must land in the target with provenance intact. More on this in the compliance section below.
- Workflow and automation rebuilds. Branching logic, enrollment criteria, delays, and goal conditions are not objects you can migrate, they are rebuilt in the target platform.
- UTM, source, and campaign continuity. First-touch, last-touch, and multi-touch values live in custom fields that break silently when the schema shifts.
- Templates, tokens, and sender identity. Transactional templates, dynamic tokens, domain authentication (SPF, DKIM, DMARC), and sender reputation need a parallel setup.
- QA against the live book. Pre-cutover, the consultant runs sample sends, workflow enrollments, and attribution checks against mirrored data.
This is a different job from the one a RevOps engineer or a Salesforce admin runs. The engineer makes the schema valid. The consultant makes the schema usable by a marketing team the morning after cutover.
A fractional marketing automation specialist is usually the right profile for this scope, someone who has shipped three or four migrations across HubSpot, Salesforce Marketing Cloud, Braze, or Marketo, and knows which fields drop when nobody is watching.
Why marketing owns half of a CRM migration (and most briefs miss it)
Most CRM migration briefs are written by IT, product, or RevOps. They scope objects, schemas, integrations, and API contracts. They assume marketing operations will "figure it out" after the data is moved. That assumption is where migrations fail. Marketing systems hold state, opt-ins, enrollments, lifecycle positions, attribution, that engineering migrations do not preserve by default.
When state disappears, you see it in three places first:
- Deliverability drops. New sending domain, no warm-up plan, consent records that cannot prove when a subscriber opted in. Your inbox placement falls and your transactional mail starts going to spam.
- Lifecycle enrollment holes. Workflows that were running against 40,000 contacts restart with zero. Your welcome series, re-engagement flow, and churn-risk campaigns stop firing for everyone mid-funnel.
- Attribution goes dark. Source, UTM, and first-touch values live in custom fields that get renamed in the target. The CFO's revenue-attribution report starts showing "unknown" for 60% of the pipeline.
The HubSpot State of Marketing report consistently finds that marketers rank "data quality" and "connecting tools together" among their top ops frustrations. A CRM migration is the single largest opportunity in a given year to either fix those problems or make them permanent.
The fix is simple. Add a marketing workstream to the brief. Hire a specialist who owns it. Make the acceptance criteria explicit before the cutover date gets locked in. If you need to see where that specialist slots into the broader org, the marketing team structure guide walks through the common patterns.
The 7-part marketing workstream checklist for your CRM move
Every CRM migration brief should include these seven items as named deliverables, each with an acceptance criterion. If your brief does not scope all seven, your marketing team is going to inherit the gap at cutover.
- Lifecycle and stage mapping. Audit the source system's lifecycle definitions (lead, MQL, SQL, opportunity, customer, churn), propose a target taxonomy, and run the record-by-record swap. Done when every active record carries a lifecycle value in the target that round-trips with the source dashboard.
- Consent and subscription state preservation. For every email subscriber, preserve opt-in level, legal basis, consent timestamp, source IP (where applicable), and unsubscribe tokens. Done when a sample of 500 subscribers verifies identical consent state in source and target, with original timestamp and source preserved.
- Workflow and automation rebuild. Document every active workflow in the source, rebuild in the target, and verify enrollment criteria + branch logic + delay windows + goal conditions. Done when every active workflow runs against a staging contact and produces the same output as the source.
- UTM, source, and campaign attribution continuity. Preserve first-touch, last-touch, and multi-touch custom fields; verify that the attribution report in the target returns the same values as the source for a sample of 100 recent closed-won deals. Done when revenue attribution for the last 90 days reconciles within 2% between source and target.
- Segment and list parity. Static lists migrate as-is. Dynamic segments (active lists) must be rebuilt against the target schema. Done when every active segment returns a membership count within 1% of the source segment on the same date.
- Template, token, and sender identity. Transactional and marketing templates rebuilt in the target. Dynamic tokens remapped to target field names. SPF, DKIM, and DMARC records configured for the new sending domain, with a two-week warm-up schedule planned. Done when a test send from the target delivers to a seed list across Gmail, Outlook, and Yahoo with inbox placement verified.
- QA against live traffic and rollback plan. Pre-cutover, run parallel sends from source and target to a mirrored test audience. Document a rollback procedure that can be executed in under four hours if cutover fails. Done when the rollback has been dry-run end-to-end and the on-call engineer has signed off.
Hand this list to your consultant on day one. Ask them which items they have shipped before, and ask for the acceptance evidence (screenshots, reconciliation reports, QA logs) from a prior migration. If they cannot show you evidence from items 2, 4, and 7, keep looking.
Consent and compliance, what breaks in a sloppy migration
Consent is the single highest-risk element of a CRM migration. Email subscription state is a legal record, not a preference. Under GDPR, CAN-SPAM in the US, CASL in Canada, and the Australian Spam Act, you must be able to prove when and how a subscriber opted in, and you must honor unsubscribe requests across any system that holds the record. A migration that corrupts consent provenance is a compliance incident.
The hard rule: a migration can downgrade consent (double opt-in collapses to single opt-in in your records, fine, the signal is weaker but no promise is broken) but can never upgrade it. If a subscriber opted in on a single-opt-in form in 2021, your target system cannot record them as double opt-in in 2026. That is a lie you will discover at the first regulator audit.
| Regulation | What must survive the move | How to verify |
|---|---|---|
| GDPR (EU) | Legal basis, consent timestamp, opt-in method, right-to-be-forgotten log | Sample 500 EU records, confirm each has basis + timestamp in target |
| CAN-SPAM (US) | Unsubscribe honor list (10-day rule), sender identification, physical address | Export source suppression list, verify 100% land in target suppression |
| CASL (Canada) | Express vs implied consent flag, consent expiry date (24 months for implied) | Verify CA-flagged records carry consent-type field; expired records moved to suppression |
Your consultant should produce a consent audit before the cutover. If the audit finds gaps, you fix them in the source before the move, not in the target after. Salesforce developer documentation covers the subscriber-state objects on the target side if you need the technical reference.
Lifecycle, workflow, and attribution rebuilds you cannot skip
Three subsystems inside the marketing stack get rebuilt during a CRM migration. Each one has its own QA profile and its own failure mode. A good consultant will not treat them as one job.
Lifecycle parity. Every active contact carries a lifecycle stage, a lead score, and (often) an active workflow enrollment. The source taxonomy will not match the target taxonomy exactly. Your consultant proposes the mapping, runs the swap, and verifies that the funnel report in the target shows the same stage counts as the source on the same date. QA checks: stage count reconciliation, score distribution histogram, enrollment count per workflow.
Workflow rebuild. Workflows are logic, not data. They cannot be migrated, only re-authored. Document every active workflow in the source (name, trigger, enrollment criteria, branch logic, delay windows, goal conditions, exit criteria). Rebuild in the target. Run a staging contact through each workflow and confirm it produces the same output. QA checks: trigger firing on test record, branch selection, delay honor, exit criteria.
Attribution continuity. First-touch, last-touch, and multi-touch attribution values live in custom fields that are read by reporting tools (your BI stack, your CRM dashboards, Salesforce campaign influence, HubSpot attribution reports). If the field names change in the target without the reports being updated, the CFO's revenue report starts showing "unknown" for most of the pipeline. QA checks: field-name mapping documented, reports updated to point at target fields, 90-day revenue reconciliation within 2%.
A marketing analyst is often the right second seat on this workstream, someone to own attribution reconciliation while the migration consultant owns the systems rebuild.
Fractional vs full-time vs agency, when to hire which
Three hiring models fit a CRM migration. The right one depends on your timeline, your team's post-migration capacity, and whether you need the specialist again after cutover. Most mid-market companies pick fractional for the migration itself and keep a full-time ops owner for the long tail.
| Model | Best when | Watch-out |
|---|---|---|
| Fractional specialist | 8-16 week migration, no in-house MarTech lead, need senior work from day one | Scope creep after cutover, define a clean exit |
| Full-time hire | Ongoing CRM/MarTech ownership needed, 3+ migrations on the roadmap | 3-6 month ramp before productive; delays migration |
| Agency | Multi-system migration (CRM + MAP + CDP + data warehouse), need PM layer | Junior staff on the account; harder to pull expertise mid-project |
For a single CRM migration with a defined cutover date, a fractional specialist usually wins. You get senior pattern recognition from the first week, you pay for the work you need, and you can keep them on month-to-month for the post-cutover stabilization period. If you need help choosing, the fractional vs agency vs full-time framework walks through the trade-offs in more depth.
If the migration is one piece of a broader restructuring, new team, new tooling, new go-to-market, a fractional CMO can oversee the brief while the specialist executes the workstream. That is a two-person team, not one. For scoping the lifecycle work specifically, how to hire a lifecycle marketer covers the role-specific signals.
The CRM migration consultant brief template (hand this to your hire)
Below is the brief. Copy it, fill in the brackets, and send it to candidates before you book an intro call. A specialist worth hiring will push back on at least two sections. Push-back is a buy signal.
1. Goals
- Primary: migrate from [source CRM] to [target CRM] by [cutover date] with marketing operations fully functional on day one.
- Secondary: fix [specific data quality issue, e.g. "unknown source on 60% of pipeline"] during the move rather than after.
- Non-goal: redesigning the marketing stack beyond the CRM boundary. Scope creep is a known failure mode.
2. Current state
- Source CRM: [HubSpot / Salesforce / Pipedrive / etc.], seat count, record counts (contacts, companies, deals), active workflow count, template count.
- Email volume: sends per month, warm sending domain(s), current deliverability stats (inbox placement, bounce rate).
- Attribution model: first-touch / last-touch / multi-touch / none.
- Known debt: list the top three data quality issues you want fixed during the move.
3. Target state
- Target CRM: [name], target go-live date, seat count, planned record counts.
- Marketing automation platform: [name], if different from the CRM.
- Required integrations at cutover: [BI tool, ad platforms, enrichment, data warehouse].
4. Marketing workstream deliverables
- Deliver all seven items from the workstream checklist above.
- Produce a consent audit before cutover.
- Produce a rollback plan and dry-run it with the on-call engineer.
- Produce a 30-day post-cutover stabilization plan with named owners.
5. Acceptance criteria
- Each of the seven checklist items has a named acceptance criterion. Sign-off happens item by item, not as a bundle.
- Revenue attribution reconciles within 2% of source for the trailing 90 days.
- No regression in email deliverability (inbox placement within 2 points of pre-cutover baseline across Gmail, Outlook, Yahoo).
6. Timeline
- Discovery and audit: weeks 1-2
- Mapping and target build: weeks 3-6
- Rebuild and QA: weeks 7-10
- Dry-run and cutover: weeks 11-12
- Stabilization: weeks 13-16
7. Reporting
- Weekly 30-minute status call with marketing ops lead.
- Written status update every Friday, green/yellow/red per checklist item.
- Final migration report at week 16, what shipped, what broke, what remains.
Across 30,000+ MarketerHire matches, the pattern holds: the briefs that get a clean cutover are the ones that scope the marketing workstream before the engineering kickoff, not after. Hand this template to your hire before you book the first call. For teams that want to outsource the whole workstream, the brief still applies, give it to the vendor before the SOW gets drafted.
FAQ
A fractional CRM migration consultant typically runs $7,000-$15,000 per month for a 10-16 week engagement, depending on seniority and scope. Agencies package the same work at $40,000-$120,000 for the full migration. Full-time ops hires cost $110,000-$160,000 base plus benefits, with a 3-6 month ramp before productive on the migration itself.
Plan on 10-16 weeks for a mid-market migration (10,000-100,000 contacts, 20-60 active workflows, one marketing automation platform). Enterprise migrations with multi-brand sending, CDP integration, or data warehouse rebuilds run 20-30 weeks. Budget 25-40% of the project calendar for QA and dry-runs, this is the stage most teams underscope and the one that catches the migration-killing bugs.
Occasionally yes, usually no. The RevOps engineer and the marketing automation specialist are different skill sets with limited overlap. A unicorn who has shipped both exists but is rare, expensive, and often a 20-hour-per-week bottleneck. The common pattern is two people, RevOps on data and schema, migration consultant on marketing systems, with a shared standup.
Three failure modes repeat. First, workflow enrollment resets to zero on cutover because triggers are not re-fired against the migrated book. Second, UTM and source fields change names and the Salesforce campaign influence report breaks silently. Third, consent records lose their timestamp and legal basis, which creates a GDPR exposure the compliance team catches six months later.
Hire fractional when the migration is a single defined project with a clear cutover date and your team can own the post-migration operation. Hire an agency when you have multiple systems moving at once (CRM + MAP + CDP + data warehouse) and you need a PM layer coordinating the work. For a single CRM move, fractional almost always ships faster and cheaper.
Yes, usually. RevOps teams own the database and the schema. The marketing workstream, consent, lifecycle, workflow logic, attribution continuity, template rebuild, deliverability, is a different scope and a different skill set. A good RevOps team will tell you this directly. The CRM migration consultant works alongside them, not in place of them.
The brief is the deliverable before the hire
A CRM migration without a scoped marketing workstream is a database project with a revenue problem waiting at cutover. The brief above is the asset to produce before you book an intro call with a candidate. Hand it over, ask for pushback, and ship a migration your marketing team can actually use the day it goes live.
About the author: Jenny Martin is a Growth Marketing Editor at MarketerHire. She has led growth across DTC and B2B SaaS, scaled revenue to $50M, and cut CAC by 40%. She writes about growth hiring, marketing operations, and what works at the $2-50M stage.
