Back to Blog

Marketing Automation Migration: The Contract Marketing Ops People Who Keep It From Breaking

Creative HiringHiringRecruiting

Last updated: November 3, 2026

A marketing automation migration off Marketo or HubSpot needs a contract platform admin, a data hygiene analyst, and an email builder for the migration months, then one admin kept after cutover. Ask each one about the last migration they ran end to end. KORE1 contractors start a median 3 days after an offer (n=1,997).

By Samantha Litman, Executive Search, Marketing, Creative & Media, KORE1

Platform admin in a teal sweater pointing at rows of sheets on a table while a data analyst in a gray sweater compares two stacks of index cards and a colleague takes notes

Nobody picks the date. That’s the funny part.

A CMO decides the company is leaving Marketo for HubSpot, or trading HubSpot up for Marketo, or out of both and into Salesforce Marketing Cloud. Everyone nods. Then someone opens the order form the company signed three years ago, back when the old platform was the shiny new one, and there it is on page four, the renewal date. That date becomes the migration plan. It wasn’t chosen by the people doing the work, and it doesn’t care how many nurture programs are still running. It never does.

So who does the work? Usually one admin. The same one who builds Tuesday’s newsletter, fixes the form that broke on Friday, and is the only person alive who knows why the lead score jumps 40 points when someone downloads a pricing sheet.

That’s the call I get. I’ve been in recruiting and executive search for more than 25 years, and these days my marketing, creative, and media searches run through KORE1, including our digital marketing staffing work. We put contract people into exactly these seats, which means I have a stake in your answer. Fair warning. If your admin has the hours and the help, you may not need me at all, and I’d tell you that up front, not in month three.

Devin Hornick, a Partner at KORE1, asks clients a question I keep stealing. “Where are you being asked to increase productivity without adding headcount?” A platform migration is the cleanest answer I know. The work is real, it has an end, and nobody wants a permanent salary for a job that’s mostly over by summer, which is a hard thing to sell to a finance team that has already turned down two other headcount requests this year. That’s what contract staffing is built for.

One thing before we start. I’m writing about the people, not the platform. Which system you should pick, and how your marketing should run once you’re on it, is a strategy question, and I’d send that to someone like a fractional CMO. My lane is who sits in the chairs. That’s it.

Which Roles Does a Marketing Automation Migration Need?

Three, for most mid-sized moves. A marketing automation migration is the project of moving your contacts, forms, emails, programs, scoring, and CRM sync from one platform to another without losing anything that matters, especially the people who asked never to hear from you again.

My rule of thumb from the hiring side, not a KORE1 benchmark. Your instance may move a row.
SeatWhat they protect during the moveJoinsLeaves
Data hygiene analystThe database. Duplicates, dead contacts, consent and unsubscribe historyWeek 1Once the final import reconciles
Platform adminThe rebuild. Fields, routing, scoring, user roles, and the Salesforce syncWeek 1After hypercare, or never
Email builderTemplates, live programs, and the send schedule nobody can pauseWeek 4When the last program is rebuilt and tested

The admin is the seat everyone thinks of. Fine. But I’d argue the data hygiene analyst matters more in the first month, because whatever you import is what you’ll live with, and a database that’s 30% duplicates in Marketo is 30% duplicates in HubSpot, just with a nicer interface. Moving dirt costs the same as moving furniture. Clean first.

Email builders get hired late. Always late. Someone assumes the templates will “come over,” and then week six arrives, nothing renders right in Outlook, and the spring webinar invite is due Thursday, with half the sales team asking where it is. Cue the panic.

Where does the CRM come in? If your Salesforce org is also changing, that’s a second project, and it needs its own people. We cover that side through Salesforce staff augmentation, and I’d keep the two teams talking every week, because the sync between them is where migrations tend to break. Watch it. And if the HubSpot side has to talk to an ERP, my colleague Colin Boothe has written about HubSpot NetSuite integration, which is a different animal with different people.

Big org, several business units, attribution reporting that finance actually reads? Add an analyst for the reporting rebuild. Most teams don’t need a fourth seat on day one. Start with three.

Which Seats Roll Off After Cutover?

Two of the three, usually. Cutover is the day you switch sending and forms to the new platform. Hypercare is the few weeks after, when things that worked in testing break in real life and someone has to be there to catch them.

The data hygiene analyst goes first. Once the last import reconciles against the old system, the record counts match on both sides, and every unsubscribe has landed on the right contact in the new platform, the job is done. The email builder goes next, after the live programs are rebuilt, tested, and sending. Then you decide about the admin. Keep, or let go?

Think about that one early. I mean it. Across 1,887 ended KORE1 contract assignments (hires 2019 to 2026, data as of October 2026), the median ran 116 days. One in four was done by day 44, and one in four lasted beyond day 227. Careful, though. That’s every role we staff, help desk to controllers, so it tells you how contract work usually runs and nothing specific about migrations. Still. A 16-to-20-week migration lands smack in the middle.

Here’s the useful part. After 1,040 hours, which is 26 weeks at 40 hours, you can hire a KORE1 contractor onto your own payroll without a conversion fee. An admin who starts in week one and stays through hypercare can get close to that line by the time you know whether you need a permanent owner. Many teams do, because the person who rebuilt the instance is the person who knows where everything is. If that sounds like you, contract-to-hire staffing is the cleaner way to set it up from the start.

Marketing operations lead in a navy blazer on an orange chair listening to a contract admin candidate in a green shirt explain a past migration at a round table

What Should You Ask a Contract Marketing Ops Admin?

I have seven questions I ask nearly every candidate, and I’ve written about them before in their plain form. For a migration seat I bend each one toward the job. Your platform lead should still run the technical interview. These are the questions that tell me whether the person will last. Just seven.

  1. Can you stay through cutover and the month after? This is my “what’s your situation right now” question, made specific. A contractor who has another start date in week ten is a risk you should know about on day one.
  2. “Which platform do you want on your resume next?” Sounds soft. It isn’t. Someone who wants HubSpot experience will work hard to learn your HubSpot. Someone who only wants a paycheck between Marketo jobs might not.
  3. Walk me through the last migration you ran end to end. The single best question on the list. No contest. I want the order they did things in, what they checked before cutover, and what broke anyway. People who’ve really done it tell it in sequence, with a mess in the middle. People who watched someone else do it skip the mess.
  4. What would you look at first in our instance? There’s no right answer. I’m listening for whether they ask about the database and the sync before they ask about the templates.
  5. What did you leave behind at your last job? Documentation, a field dictionary, a list of every active program and its owner. The habit tells me more than the certification.
  6. Who did you answer to, and how did that go? Migration admins often report to someone in marketing and get access from someone in IT. I want to hear how they handled two bosses.
  7. And the last one, about how they work. Do they want a quiet week to rebuild, or a daily standup? Remote, or in the room for cutover weekend? Nobody fails this question. They just fit, or they don’t.

Notice what’s missing. I don’t ask how many years of Marketo they have. A candidate with four years and three migrations beats one with nine years and zero, every time I’ve compared them.

What Breaks If the Migration Slips Past the Renewal Date?

Money first. If you miss the date you either renew the old platform for another term while you finish on the new one, or you sign a short extension if your vendor will offer one. Ask your account rep in writing, early, what happens to your data on the end date and how long you can still export it. Don’t find out in the last week. Ask twice.

Then the quieter things, which are worse.

Unsubscribes. The FTC’s CAN-SPAM compliance guide says you have to honor an opt-out within 10 business days, and your opt-out mechanism has to keep working for at least 30 days after you send. Each email in violation can draw a penalty of up to $53,088. And this is the line I’d tape to the admin’s monitor. Hiring another company to handle your email marketing doesn’t contract away your legal responsibility. A rushed migration that drops last month’s unsubscribes isn’t a data problem. It’s a legal one.

Deliverability is next. Google’s email sender guidelines ask anyone sending more than 5,000 messages a day to Gmail accounts to set up SPF, DKIM, and DMARC, support one-click unsubscribe, and keep spam rates reported in Postmaster Tools below 0.30%. A new platform means new sending setup. Get it wrong in a hurry, which is easy to do when the person setting it up is also rebuilding forms, and your spring campaign lands in spam folders, where no amount of good copy helps. None.

And the sync. When forms and scoring move a week before the CRM mapping is finished, leads stop routing to sales. Sales notices first. Then everybody does.

Devin’s bigger point, from the same note, is about what companies are still funding. Projects that already have a budget and an executive sponsor, and that can’t slide into 2027 without something breaking. A platform migration with a renewal date attached is one of those. It’s also exactly the kind of project that gets approved as a team for a few months when three permanent hires would get turned down.

Is the Best Candidate on Paper the Best Person for a Migration?

Not always. Sometimes not even close.

Here’s the resume that looks perfect. Eight years as a Marketo admin at one company, Marketo Certified Expert, a long list of programs built. And it might be perfect! But eight years in one instance can also mean eight years of never moving anything. Migrations are their own skill. You’re mapping one system’s logic into another system that doesn’t think the same way, under a deadline, while the old one keeps sending.

The person who’s done three messy moves, maybe at smaller companies, with a less shiny title, often knows things the eight-year admin hasn’t had to learn in a long and comfortable career at one company. Where the unsubscribe history hides. Which custom fields nobody uses. How to run old and new side by side for two weeks without double-sending to your best customers.

I’ve believed for a long time that a resume shows you what somebody has done, and doesn’t tell you much about what they can do next. That cuts both ways here. Don’t screen out the person whose title is “marketing ops specialist” if their story in question three is the best one you hear. And don’t hire the impressive one without asking it. Ask everyone.

If you’re writing the job description now, keep it short and honest. The platforms on both sides, the number of contacts, the number of live programs, the cutover date, and the name of the person who signs off. That gets me further than a page of required years.

Woman in a rust cardigan ticking a checklist on a clipboard beside a colleague in a light blue shirt reading a printed page under an orange desk lamp

What Do Contract Marketing Ops Seats Cost?

I’ll be straight with you. KORE1 doesn’t have enough marketing ops placements in its data to publish a rate for these seats, so I won’t pretend we do. What I can show you is federal wage data, plus what it costs to carry a W2 contractor once employer costs are added.

Marketing operations has no federal occupation code of its own. The closest match in the federal OEWS data tables is SOC 13-1161, market research analysts and marketing specialists, which the Occupational Outlook Handbook also profiles. National hourly wages, May 2025, with a 24% employer burden added as our planning assumption.

BLS OEWS May 2025, SOC 13-1161, national. Modeled from federal wage data, not KORE1 placements. Not a bill rate.
PointBLS hourly wageWith a 24% burdenSample migration, 1,640 hours
25th percentile$28.05$34.78About $57,000
Median$37.87$46.96About $77,000
75th percentile$52.07$64.57About $105,900

Where does 1,640 come from? It’s a sample plan, not a quote. The data hygiene analyst for 8 weeks, the email builder for 13, and the admin for 20 including a month of hypercare, all at 40 hours a week. That’s 320, 520, and 800 hours. Shorten the builder or put the analyst at 20 hours a week and the total drops fast.

Read that last column as a floor. It’s wage plus employer costs, before any staffing firm’s margin, and it prices the analyst end of the work. A senior platform admin who has run a Salesforce Marketing Cloud migration will cost more than the 75th percentile here, and should, because the hours they save you in the first month usually pay for the difference. Our page on contractor burden rates explains where the 24% comes from.

Want a systems comparison? Purely for scale, a mid-level business systems analyst, national, sits at $75 to $95 an hour with an $84 median in the KORE1 Contract Rate Index, which works out to roughly $43,700 for three months full time. That’s adjacent systems work, modeled from BLS wages and not from placements, and it isn’t a marketing ops rate. It tells you roughly where systems seats price. The method is on the contract rate card, and if you want a real number for your three seats, ask for a bill rate quote and we’ll scope it.

Questions Marketing Ops Leads Ask Before the Cutover

Realistically, how fast can a migration team be in their seats?

KORE1 contractors start a median 3 days after an accepted offer (n=1,997, all roles, not just marketing ops).

That clock only starts at the offer. Finding the right admin comes first, and when a hiring manager gets back to me the same day, my searches for a new seat usually wrap in two or three weeks. That’s my experience, not a KORE1 figure. Call about six weeks before you want the analyst in.

Should the admin convert to full time after the move?

Often yes, if nobody on your staff can own the new instance once the contractors leave.

The rebuilt instance has a memory, and it lives in whoever rebuilt it. Past 1,040 hours, they can move to your payroll with no fee from KORE1. Across all roles, 207 of KORE1’s 552 contract-to-hire placements converted to direct, about 37.5%. Decide by the end of hypercare, not after the admin has taken another offer. Timing matters.

Who owns the data cleanup, us or the contractor?

The contractor does the cleanup, and someone on your staff owns the decisions about what gets deleted.

A data hygiene analyst can find the duplicates, the bounced addresses, and the contacts nobody has emailed since 2021. Whether to delete them is your call, and so is the unsubscribe history, which should never be “cleaned” away. Write down who signs off. One name.

Can one admin run the whole migration?

On a small database with a handful of programs, a strong admin can, if the cutover date gives them room.

What one person can’t do well is clean the data, rebuild every program, and keep this month’s emails going at the same time, while also answering the sales team’s questions about why their leads suddenly look different. Something slips. Usually it’s the cleanup, and then the mess moves with you. If I had to cut a seat, I’d cut the builder before the analyst and ask your current team to cover sends.

Does it matter which direction we’re moving?

For hiring, the destination platform matters more than the one you’re leaving.

Your admin is going to live in the new system. Hire for it. Someone who knows the old platform well helps with the mapping, but that can often be your current admin, working alongside the contractor for a few weeks. Moving into Salesforce Marketing Cloud is its own case, since it leans on SQL and a different data model, so I screen for that specifically.

When’s Your Renewal?

If there’s a date on page four of an order form somewhere in your building, I’d like to hear about it. Really. Send me four things, the platform you’re leaving and the one you’re moving to, the cutover date, how many people you picture, and how many hours a week the budget covers. I’ll come back with the seat I’d staff before anything else, and the one I suspect you can skip.

Let’s talk about your migration team. If you’d rather see the full range of seats first, our marketing operations staffing page lays them out.

So, who in your building knows why that lead score jumps 40 points? And are they going to be around in March? Or say hello on LinkedIn.