Moving the ERP to the cloud without breaking the plant floor
Cloud ERP migrations are sold as finance projects. In a plant, the risky seams are everywhere the ERP touches production: scanners, labels, EDI, the MES handoff and the shop-floor logins nobody documented.
· Jake Schaaf, Founder of Atticus Rowan
The ERP vendor’s end-of-life letter eventually arrives at every manufacturer running a decade-old on-premise system. Support is ending, the replacement is cloud-hosted and the sales deck is all dashboards and quarterly releases. The project gets framed as a finance-and-operations upgrade, the steering committee fills with accounting and the implementation partner’s plan devotes 1 line to “integrations.”
In a plant, that 1 line is where the risk lives. The ERP is not just the books. It is the system the shop floor touches a thousand times a shift, through barcode scanners posting completions, label printers pulling order data, the MES or scheduling board reading routings and the EDI translator turning customer releases into orders. Finance can tolerate a rocky cutover month. The floor finds out at 6 a.m. on day 1 whether anyone mapped those seams, because the label printer either prints or it does not.
We are not an ERP implementer, and this post is not about choosing one. It is about the infrastructure and security layer underneath the migration, the part that determines whether go-live is an accounting story or a production story, and it is the layer that plant IT (or the plant’s IT partner) owns regardless of which software wins.
The seams to map before anyone signs
Walk the data paths that cross between the ERP and the physical world, because each one is a cutover task with a failure mode:
- Scanners and shop-floor terminals. What do they actually talk to today, and does the cloud ERP’s shop-floor module replace that path or sit beside it? Devices running ancient Windows CE or browser versions the new system will refuse are a hardware line item nobody put in the project budget
- Label printing. Compliance labels, customer-specific formats, print servers with hard-coded IPs. Label failures are invisible in testing and catastrophic on a shipping dock
- EDI. The translator that feeds orders today has to point at the new system on cutover weekend without dropping a release. Your biggest customer’s scorecard does not pause for your migration, the exposure covered in EDI and the customer connection layer
- The MES and scheduling handoff. Routings, BOMs and completions flowing both directions. If the old integration was a nightly file drop a consultant built in 2016, the knowledge of what it does may exist nowhere but in the file itself
- Bandwidth and the single circuit. An on-prem ERP survives an internet outage. A cloud ERP is down when the circuit is down, for the office and the floor alike. A plant moving to cloud ERP almost always needs a second internet path with automatic failover, and that order has a lead time measured in months, not weeks
The security work the migration should carry with it
A migration is the one moment you can fix identity and access sins without fighting the installed base, because everything is changing anyway:
- Individual logins this time. The old ERP’s shared “SHOPFLOOR” account that 40 people use is a known problem nobody would fund fixing. The new system starts clean or it never will: named accounts, badge-tap or quick-switch where the line needs speed, and an answer for the auditor who asks who posted that transaction
- SSO and MFA from day 1. Tie the ERP to your existing identity platform at go-live, not as a phase 2 that never comes. MFA on the system of record is now a cyber insurance expectation, and go-live is the cheapest moment it will ever be
- Roles rebuilt, not copied. Migrating the old permission set imports a decade of accumulation, including the purchasing clerk who could approve her own POs. The implementation partner handles config; someone on your side has to own the question “who can do what, and who checked”
- The integration credentials. Every seam above gets a service account, scoped and vaulted, instead of the admin credential pasted into a config file. The accounts created during migration week are the ones that live for the next decade
Cutover is a production event. Run it like one
The go-live plan should read like a shutdown-week plan, because it is one: staged in advance, executed against a checklist, with a proving run before the first real shift. Freeze reference data early, rehearse the cutover on a copy including the scanners and a label printer, decide the point of no return in advance and write the fallback honestly, can the old system take orders for 1 more week if the seams fail? The restart-morning test is the same as after any outage: take 1 real order from entry to a printed, correct label on a real dock before declaring victory. And keep the old system readable, somewhere isolated and cheap, because 7 years of lot traceability and customer history have audit value long after the license dies.
One more thing worth saying plainly: cutover weekend is a social-engineering window. Everyone expects strange emails about new systems and new logins, which is exactly the cover a phishing campaign wants. Tell the whole plant in advance precisely how credential instructions will arrive, and that anything else, however urgent it sounds, gets reported. The same logic as the acquisition-week phishing wave, different trigger.
A cloud ERP migration done with the seams mapped is genuinely good for a plant: less hardware to defend, a system that patches itself and an identity layer that finally matches how people work. Done with the seams ignored, it is the most expensive way to discover how many things touched the old server. Atticus Rowan sits on the plant’s side of these projects, owning the network, identity, integration and cutover layer while the implementation partner owns the software. If an end-of-life letter is sitting in a drawer and the demos have started, start a conversation before the statement of work is signed.
Related insights
More on Operations & OT →October 27, 2026
That urgent call from the owner might be an AI. Verification beats detection.
Voice cloning turned the fake-CEO wire request from a clumsy email into a convincing phone call. The defense is not spotting the fake. It is a payment process that does not care how convincing the voice is.
October 23, 2026
The holiday shutdown is your best IT window of the year. Plan it now.
Plants that go dark between Christmas and New Year get a free maintenance window most businesses would pay for. The work that fits in it gets decided in October, not December.
October 21, 2026
Building the 2027 IT budget: what to fund first when everything looks urgent
Budget season is when security wish lists meet reality. A priority order for mid-sized companies deciding what IT and security money actually buys next year.