A plant can't move to the cloud the way an accounting office does. Email and files can go tomorrow; the machines can't. Here's how Ontario manufacturers decide what moves, what stays and in what order.
TL;DR Move the office side of a plant first: email, files, Teams, backups and reporting. Keep anything that has to keep running when the internet drops close to the machines. Check your server’s support date (Windows Server 2016 ends January 12, 2027), check the plant’s internet before you depend on it, keep machine networks off the internet, and move in phases around production, not in one weekend.
Most cloud migration advice is written for offices, where every system is a laptop, a browser and a subscription. A plant is different. The same building runs email and quoting in the front office and machine controllers, scanners and label printers on the floor, and the two have very different tolerance for an internet outage. This article sits alongside our guide to cloud migration services for Ontario businesses.
I’m Adam Bowles, Partner and CEO at ACT360. Below: what usually moves first in a plant, what should stay on site, the server deadlines forcing the question this year, what the internet connection needs, how to keep the floor secure, and a phased order that doesn’t stop production.
What Does Cloud Migration Mean for a Manufacturer?
For a manufacturer, cloud migration means moving business systems such as email, files, backups and some applications from servers in the building to hosted services, while keeping the systems that run production close to the machines.
It’s rarely all or nothing. Statistics Canada’s Survey of Digital Technology and Internet Use found cloud computing was the most used technology among Canadian businesses with five or more employees in 2023, at 48%. In practice, most plants that say they’re “in the cloud” have moved email and a few applications, and still run a server in a back room for the ERP, the file shares or a machine-data system.
That mixed setup, usually called hybrid, is often the right end state for a plant, not a halfway point. The question isn’t whether to move everything. It’s which systems gain from moving and which ones would become fragile if they depended on an internet connection.
Which Plant Systems Should Move First, and Which Should Stay?
Move the systems that office staff use and that can tolerate a short internet outage. Keep anything on site that has to keep working, second by second, when the connection drops: machine controllers, HMIs, label and scanning stations tied to the line.
| System | Usual move | Why |
|---|---|---|
| Email, calendars, Teams | Move first | Low risk, easy to test, removes an old mail server |
| Office files and shared drives | Move early, after a clean-up | Remote access for sales and management; permissions need fixing first |
| Backups | Add an off-site copy now | A fire or ransomware hit shouldn’t take the backup with it |
| Reporting and dashboards | Good cloud candidate | Reads data rather than running the line |
| ERP | Case by case | Depends on the vendor, integrations with the floor and how the plant copes offline |
| Machine controllers, HMIs, SCADA | Stay on site | Must run without the internet; shouldn’t be reachable from it |
| Floor scanning and label printing | Usually stay local, or cache locally | Shipping stops if every scan waits on a cloud round trip |
A useful test for anything on the floor: if the internet were down for four hours on a Tuesday, would this stop product going out the door? If yes, it either stays local or needs a design that keeps working offline. Microsoft’s own documentation for its edge devices makes the same point from the other direction: Azure IoT Edge is built so that devices can keep working “with intermittent or no internet connection” once they’ve connected once.
Why Are So Many Plants Looking at the Cloud Right Now?
Because the servers many plants run on are reaching the end of Microsoft support. Windows Server 2016 extended support ends January 12, 2027, and SQL Server 2016, common under older ERP systems, already ended on July 14, 2026.
- Windows Server 2016: extended support ends January 12, 2027, per Microsoft’s lifecycle page.
- Windows Server 2012 R2: extended support ended October 10, 2023, and even the paid Extended Security Updates ran out in October 2026, according to its lifecycle page.
- SQL Server 2016: extended support ended July 14, 2026; paid security updates are available into 2029, per the SQL Server 2016 lifecycle page.
When a server is due for replacement anyway, the honest comparison is new hardware on site versus moving some or all of what it runs. Sometimes the answer is a smaller on-site server for the floor and the ERP, with everything else moved. Sometimes it’s a straight hardware refresh, because the ERP vendor or the plant’s internet makes a move a bad bet. Either is fine if the decision is made on purpose rather than in the week the old server fails.
If the ERP is the sticking point, our page on ERP support for manufacturing in Ontario covers who owns which layer and what to check before any change.
Is Your Plant’s Internet Ready for the Cloud?
Check it before you depend on it. Once email, files and backups live in the cloud, the plant’s internet connection becomes a production system, so it needs enough capacity, steady performance and a second connection from a different provider.
Plants are often outside town centres, on industrial land or rural roads where options are thinner. The Rural Ontario Institute’s 2025 internet factsheet, drawing on the Ontario Broadband Resource Hub, reports that 84% of rural households had access to 50/10 Mbps service as of December 2024. That figure is about households, not industrial parks, but it shows why a plant shouldn’t assume a fast, redundant connection is available until someone checks.
- Measure what you use today, especially upload, which backups and file sync lean on.
- Add a second connection from a different provider and a firewall that fails over on its own.
- Plan for the outage anyway. Decide what the floor does if both links drop, and make sure production systems don’t need either one.
How Do You Keep the Plant Floor Secure During a Cloud Move?
Keep the machine side off the internet and separate from the office network. A cloud move touches firewalls and remote access, which is exactly when an old shortcut to a machine controller gets left open.
The Canadian Centre for Cyber Security’s June 2025 advice on securing operational technology puts “remove OT connections to the internet” first, warning that attackers actively look for exposed industrial systems. It also recommends segmenting IT and OT networks so a breach in one doesn’t spread to the other.
In a migration, that means three practical checks: list every remote connection into the plant (including OEM and integrator access), close the ones nobody can explain, and make sure the new cloud-connected office network doesn’t have a flat path to the floor. Our page on cybersecurity for manufacturing in Ontario covers the common ways into a plant and what closes each one.
Where your data lives matters to some customers too. Microsoft’s Azure regions list includes two in Canada: Canada Central in Toronto and Canada East in Québec. If a customer contract or questionnaire asks where your data is stored, choose the region on purpose and write it down.
What Order Should a Plant Migrate In?
In phases, around the production schedule, with each step tested before the next one starts. A plant should never find out on Monday morning that something broke over the weekend cutover.
- Inventory. List every server, application, integration, machine connection and remote access path, and who uses each.
- Decide per system. Move, keep, replace or retire, using the four-hour outage test above.
- Fix the foundations. Internet redundancy, MFA on every account, and network separation between office and floor.
- Move email and collaboration. The lowest-risk step and a good test of how your team handles change.
- Clean up and move files. Fix permissions first, then move departments one at a time.
- Add off-site backups for whatever stays on site.
- Decide the ERP and the server last, with the vendor involved and a rollback plan written down.
Time the disruptive steps for shutdowns, slow shifts or holiday weeks, and keep the old system available until the new one has run a full production cycle. Our cloud migration checklist for Ontario businesses has the general pre-move checks; the plant-specific additions are the outage test, the floor network and the production calendar.
Does Cloud Migration Help With AI and Data Projects?
It can, because reporting and AI tools work best when data from the office and the floor is in one reachable place rather than spread across old servers and spreadsheets. But the data has to be clean and the foundations secure first.
A sensible sequence is migration first, then reporting, then automation. A plant that has its files, ERP data and production counts organized can start with dashboards, then look at the repeat tasks worth automating. Our page on AI automation for manufacturing in Ontario covers where AI fits in a plant and what needs to be in place before it’s worth trying.
How Does ACT360 Approach Cloud Migration for Manufacturers?
We start on the floor, not with a product list. Through the Assess and Comprehend steps of our ACTION approach, we walk the plant, inventory what runs where, and ask the people on each shift what can’t stop. The recommendation spells out what to move, what to keep and what we’re deliberately not recommending yet.
Implementation is phased, not big-bang: critical systems go first, get validated, then we expand. Putting people before technology was the theme of our post from ADM Toronto 2025, and it applies here: a migration that works technically but confuses the floor hasn’t worked. For plant-specific IT more broadly, see our manufacturing IT page.
Final Thought
A plant’s cloud move works when the office gets the flexibility and the floor doesn’t notice. Move the systems that can survive an outage, keep the ones that can’t close to the machines, check the internet and the server dates now, and phase the work around production.
If you’d like a second opinion on what your plant should move, our free IT Readiness Assessment is a 30-minute review of your servers, internet, backups and plans, with a short list of what to do first. You can also call 705-739-2281 or email [email protected].
