The signals before an ERP migration

An ERP migration never starts with an RFP. It starts a year earlier, with a new finance leader, a line in a filing and a handful of job posts that name the platform.

Read those early and you're in the room when the scope gets written. Wait for the tender and you're one of twelve bidders on someone else's plan.

Why ERP moves are predictable

Companies don't replace their ERP on a whim. It's the most painful project a finance and IT team will run. So the decision leaves tracks. Somebody has to build the case, get budget, pick a partner and staff the program. Every one of those steps shows up somewhere public if you know where to look.

And the services work around an ERP move is enormous. Data migration, integrations, testing, change management, reporting rebuilds, support during cutover. Even firms that won't touch the core implementation have plenty to sell.

The signals, in the order they tend to appear

Business pressure usually comes first. Public companies name legacy systems in the 10-K risk factors. They talk about "finance transformation" or "systems modernization" in earnings releases. An acquisition that leaves a company running two or three ERPs is a strong tell, and so is a cost program that calls out back-office efficiency. The 3x3 for a public company shows how to pull these fast.

Then a new leader arrives. A CFO or CIO in their first 90 days often uses the ERP as the defining project of their tenure. If the last leader put it off, the new one has every reason to start.

Then tech stack signals appear in job posts. Roles that ask for experience with a specific cloud ERP, when the company runs something else today, are a clear tell. So are posts for a finance systems program manager or a data migration lead. Hiring for the problem you solve is a signal the budget is real.

Then topic signals. The CFO posts about closing the books faster. The controller attends a vendor's user conference. A finance director comments on a thread about cloud migrations.

The RFP or vendor search comes last. By then the strategy is set.

Stacking matters more than any single one

One job post is interesting. A job post naming the target platform, a new CFO and a 10-K that mentions consolidating systems after an acquisition, all inside the same couple of months, is an account you call this week.

And watch the clock. A filing from eighteen months ago with nothing new around it is stale. Signals lose weight as they age, so the freshest stack wins. The guide to buying signals covers how to weigh them.

An example opener

Say a mid-market distributor closes an acquisition. Six weeks later, a new CFO starts. Then the company posts for a finance systems manager with experience in a cloud ERP it doesn't use yet.

Noticed you joined as CFO a few weeks after the acquisition closed, and the new finance systems role asks for cloud ERP experience the company doesn't run today. My guess is the near-term pain isn't picking the platform but closing the books across two systems until the move happens. Is that accurate, or is the bigger issue something else?

That note names the events plainly. It connects them to the CFO's first months. It guesses at the misery between now and cutover, which is where most services firms can help right away. And it invites a correction.

Who's on the committee

The CFO owns the outcome and the budget. The CIO or head of IT owns the integration and the data. A finance systems lead or controller lives with the day-to-day and often runs the selection. Reach all three. Each sees a different version of the same problem.

Where to play

You don't have to be the systems integrator to win here. Plenty of firms sell the work around the core program. Data cleanup before migration. Reporting rebuilds after. Integration with the warehouse and CRM. Testing support. Interim finance operations help during the dual-running period.

Pick the piece you're best at and pitch it early, before the big integrator writes it into their scope. The signals give you that head start. Use it.