Picture a mid-sized parts distributor on a Monday morning. The ERP server in the back office won’t start. Orders can’t be entered, the warehouse can’t print pick lists, and the trucks sit at the dock while someone tries to find the one employee who knows how the server was set up.
Nothing about that story needs a cyberattack or a dramatic failure. An aging disk is enough. And it points at a question most manufacturers, distributors, and retailers only ask after something breaks: where should the software that runs our business actually live?
The honest answer isn’t “the cloud” for everyone. There are three real options, each with trade-offs, and one category of equipment that shouldn’t move at all. This guide walks through the options in plain terms, explains why the single-server setup is riskier than it looks, covers what’s different for manufacturers and for retailers, and gives you a checklist to decide what fits your business.
The short answer
An ERP is the main software that runs your orders, inventory, purchasing, and accounting. You have three realistic ways to run it: on your own server (on-premise), on the software vendor’s own cloud, or on managed cloud infrastructure run by a hosting provider using your existing licence. On-premise gives the most control but concentrates risk in one building. Vendor cloud is the simplest but isn’t offered for every product or edition, and may mean changing how you work. Third-party hosting keeps the software you already run while moving the infrastructure off your premises. Most manufacturers who want to keep their current ERP, but not their aging server, end up at the third option.
The right pick depends on three things: whether your ERP vendor offers a cloud version you’d actually want, how customized your system is, and how much downtime your operation can absorb.
Why a single ERP server is a bigger risk than it looks?
For a manufacturer or distributor, the ERP is rarely just accounting. It drives purchasing, inventory, scheduling, shipping, and invoicing. When it goes down, the building usually goes quiet with it, which is why one server in one location is a concentrated risk.
Ransomware makes the risk concrete. Canada’s Cyber Centre describes ransomware as one of the most disruptive, costly, and persistent challenges facing Canadian organizations of every size. Manufacturing is consistently among the most-targeted sectors, because attackers know that a stopped line creates pressure to pay quickly.
The numbers vary by study, but the shape is consistent:
- An analysis of hundreds of ransomware incidents at manufacturers found average downtime of well over a week per attack.
- Sophos survey research, as reported by industry analysts, put the average recovery cost for manufacturers at roughly US$1.3 million, before any ransom.
- Many manufacturers run lean on inventory, so even a few days of lost shipping hurts customers.
One point deserves attention: restoring IT and restarting production are different clocks. IT teams can often bring systems back in hours. Getting scheduling, inventory counts, and shipments back in sync can take days. A recovery plan that only covers the server is only covering half the problem.
None of this means the cloud makes you immune. Attackers still target stolen passwords, unprotected laptops, and connected systems. But a hosted environment with multi-factor authentication, managed backups, and monitoring is a different starting position from an unmonitored server in a back room.
The three options, compared
| On-premise | Vendor cloud | Third-party hosted | |
|---|---|---|---|
| Where it runs | Your own server | The ERP vendor’s cloud | Managed servers run by a hosting provider |
| Your software | Your current version | Often a different product or edition | Your current version and licence |
| Control and customization | Highest | Often more limited | High, within your licence |
| Who manages the server | You or your IT contractor | The vendor | The hosting provider |
| Hardware refresh | You pay for it | None | None |
| Availability | Always an option | Not offered for every product or edition | Depends on product, edition, and licence |
| Main risk | Single point of failure | Lock-in, forced changes, migration effort | Needs a provider you trust |
A few notes on reading that table honestly:
Vendor cloud is not always a like-for-like move. Some ERPs offer a cloud edition that behaves differently from the version you run today, with different customization options and sometimes different pricing. Moving can be a re-implementation, not a simple relocation.
Third-party hosting depends on licensing. Whether a given ERP can be hosted by a provider depends on the specific product, edition, and your licence terms, which is why any reputable host starts with an assessment rather than a promise.
On-premise isn’t wrong. It can still be the right answer, and the next section explains when.
When staying on-premise actually makes sense?
On-premise remains a reasonable choice when your hardware is relatively new, your workloads are stable, you have a capable in-house or contracted IT team, and you have strong, tested backups and security. It becomes the weaker choice when the server is aging, the one person who understands it is a single point of failure, or backups have never been tested.
If you’re in the first group, there’s no reason to move for the sake of it. A well-run on-premise setup beats a poorly planned migration.
The warning signs that it’s time to reconsider:
- The server is past its expected life and replacement is coming up
- Only one person knows how it’s configured
- Backups exist, but nobody has restored from them recently
- Remote access depends on a slow or unreliable VPN
- A second plant, warehouse, or store is being added and the system can’t easily reach it
What should not move to the cloud?
Not everything in a manufacturing facility belongs in a hosted environment. Production-floor equipment, including PLCs, CNC machines, and SCADA or industrial-control systems, generally needs separate assessment and often stays on-site, managed by the appropriate industrial vendor.
This is where generic “move everything to the cloud” advice goes wrong. A sensible migration separates the business IT environment from the operational technology (OT) on the floor:
- Usually a good fit for hosting: ERP and MRP servers, SQL databases, accounting, file servers, Microsoft 365, remote desktops for office and engineering users
- Usually reviewed individually: engineering workstations, warehouse terminals, barcode systems
- Typically stays on-site: PLCs, CNC, SCADA, and safety-critical or industrial-control equipment
A provider who tells you everything can move without asking what’s on your floor isn’t being straight with you.
Connecting a plant, a warehouse, and a head office
One of the strongest reasons manufacturers and distributors move their ERP is multi-location access. When head office, plant, warehouse, and stores all work from the same hosted environment, everyone sees the same current data without relying on a slow link back to one server.
The typical pattern is an ERP running at head office, with the plant and warehouse connecting over links that were never designed for it. Sessions lag, reports take too long, and adding a location means another round of network projects.
With a centralized environment, authorized users reach the same applications and data from any approved site. It also changes continuity: if one location loses its internet connection or its local server, the hosted environment stays up, and staff can potentially reconnect from another site.
Retail and distribution: what to host, and what already lives in the cloud
Retailers and distributors usually run two layers: the checkout at the counter, and the back office behind it. Modern point-of-sale platforms such as Shopify POS, Lightspeed, Square, and Clover are already hosted by their vendors, so a hosting provider doesn’t need to re-host them. The back office is where the aging servers and growing pains usually sit.
If your stores run a cloud POS, the checkout software isn’t the problem. The systems it connects to usually are. Four areas are worth looking at:
Multi-store back office. Head-office accounting, purchasing, and reporting often depend on one server, while each store has grown its own small setup. That works until you add a location, and then every new site means another round of network and access projects. One managed environment gives head office and every store the same applications and the same current data.
Inventory databases. Stock, purchasing, and replenishment usually sit in a database that several people use at once. For distributors, order and warehouse data live there too. These databases need reliable multi-user access and backups that have actually been tested. If the link to the server is slow, or the server fails, stock counts drift and ordering goes wrong.
Microsoft 365 and shared files. Price lists, supplier files, and spreadsheets tend to live on a shared drive nobody has reviewed in years. A managed environment lets you control exactly who can reach what, which matters most in retail, where staff turnover and seasonal hiring are constant. Clean onboarding and offboarding is a security measure, not just housekeeping.
Warehouse and head-office users. Buyers, finance staff, and managers often work from different places. Secure remote access to the same systems beats a slow VPN back to one office.
What stays the same: your POS vendor keeps running checkout. What a hosting provider can manage is the technology around it, meaning head-office systems, accounting, inventory databases, file servers, remote desktops, networks, and backups. As with manufacturing, warehouse terminals and barcode systems should be reviewed individually before anything moves.
Seven questions to answer before you move your ERP
Whichever option you lean toward, work through this list first. A good provider will help you answer it.
- How long can we be down? Define a recovery time target for the ERP, and a different one for production-critical systems. If you haven’t, you can’t test whether your backups meet it.
- Can our licence be hosted? Confirm deployment rights for your ERP, edition, and version.
- What integrations depend on this server? EDI, barcode scanners, e-commerce, shipping, and reporting tools all need to keep working.
- How will the plant connect? Latency between the floor and the hosted environment matters for some workloads.
- Have we ever restored from backup? A backup you haven’t tested is an assumption.
- Who controls access? Multi-factor authentication, centralized user management, and clean offboarding.
- Where does the data live? For a Canadian business, Canadian data centres keep that answer simple.
Frequently asked questions
Can any ERP be hosted by a third party? Not automatically. It depends on the specific product, edition, and licence terms. Some products also offer a vendor-hosted cloud version, so the right option varies. A provider should assess your deployment before committing.
Is cloud ERP safer than on-premise? It can be, but not automatically. A managed environment with multi-factor authentication, monitoring, and tested backups is usually stronger than an unmonitored back-room server. Cloud systems are still exposed to stolen credentials, unprotected devices, and weak integrations, so the controls matter more than the location.
Will hosting my ERP stop ransomware? No single measure does. Hosting reduces dependence on one building and one server, and adds protections like managed backups, firewalls, and monitoring, but staff training, access controls, and a recovery plan still matter.
Do we have to replace our ERP to move to the cloud? Not necessarily. Hosting your existing ERP on managed infrastructure keeps the software your team already knows. A vendor-cloud migration is more likely to involve changes to the product itself.
Can you support our PLCs and CNC machines? Business IT hosting generally doesn’t cover PLCs, CNC, SCADA, or other industrial-control systems. These require separate assessment and often remain managed by the relevant industrial vendor.
What if we run Shopify, Lightspeed, or another cloud POS? Those are already vendor-hosted. The useful work is managing the computers, networks, Microsoft environment, and back-office systems around them.
We have several stores and a head office. What would actually move? Usually the back office: accounting, inventory and purchasing databases, shared files, Microsoft 365, and remote access for head-office staff. The checkout software stays with its vendor. A good provider will review each store’s setup before deciding what moves.
The bottom line
There’s no single right place to run an ERP. On-premise suits well-maintained, stable setups with capable IT support. Vendor cloud suits businesses ready to adopt the vendor’s own cloud product. Third-party hosting suits manufacturers and distributors who want to keep the software they run today and stop depending on one aging server. Whichever you choose, keep production-floor equipment out of the migration plan and write down your recovery targets before you start. For retailers and distributors the same logic applies to the back office: leave the checkout software with its vendor, and put your head-office systems, inventory databases, and shared files somewhere reliable.
If you’re weighing a move, Cloudnet can assess your ERP, databases, users, and locations, and tell you honestly what can move, what should stay, and what a practical setup looks like. See how we work with manufacturing and retail businesses or request a free assessment and we’ll walk through your environment with you.
