Sage X3 on a private cloud
Each part of Sage X3 gets its own properly sized server, so MRP runs, batch jobs and month-end don't slow each other down. Backups, disaster recovery and 24/7 monitoring come with it, for one monthly fee.
Sage X3 is four systems working together
A Sage X3 installation has a web server, an application server, a database server and a print server. When they share one undersized machine, an MRP run or a large batch job slows down every user on the system.
We give each part its own resources and size them from your actual workload: how many sites, how many users at month-end, how long your MRP and batch runs take today. The result is that planning runs finish in minutes and users on the sales screens don't notice them.
Four tiers, sized to work together
Each tier runs on its own resources, sized for its job and connected to the others over a fast private network.
Secure browser access for every user, kept separate from processing load.
MRP planning, batch jobs, and business logic on dedicated compute.
NVMe storage and SQL tuning for X3's transaction load and multi-site consolidation.
Report and document rendering offloaded, so printing never slows users down.
Field note, anonymised
"Faster servers were only part of it. RFR worked out with us which batch jobs, integrations and reporting windows had to be protected before we moved X3 to the cloud, and planned the move around them."
The servers behind it
Starting specification for a multi-tier X3 deployment. The assessment sizes each tier from your workload.
Fast solid-state drives for X3's heavy database traffic.
Room for MRP and batch runs while users keep working.
Error-correcting server memory, sized for multi-company processing.
Two paths between tiers, so one failed link doesn't stop the system.
How the move works
Your users keep working until the last evening.
Moving Sage X3 to our cloud is planned so the old system stays in use while the new one is built and tested. The only pause is the final data sync, which we schedule outside working hours.
The old server stays untouched after go-live, so there is always a way back.
The full migration plan- 01
Assessment
We look at the system you run today: database size, user count, branches, integrations, scheduled jobs, the reports that run slowly and your backup history. You get a sizing, a fixed monthly price and a dated move plan.
- 02
Build the new environment
We build your servers in our cloud alongside the old one. Nothing changes for your users while this happens.
- 03
Trial move
We restore a recent copy of your data into the new environment and your key users test it: reports, printing, integrations and a month-end run. Anything that behaves differently is fixed here, not on go-live night.
- 04
Final sync
In an agreed out-of-hours window, usually a Friday night or a weekend, users log off, we move the latest data across and reconcile balances, open orders and stock.
- 05
Go live
Users log in to the new environment on the next working day. The old server is left untouched for an agreed period, so there is a way back if something unexpected shows up.
- 06
Hypercare
We watch performance and tickets closely for the first weeks and through the first month-end close, then hand over to normal support.
Questions we get asked
Sage X3 cloud questions
What do the 5-minute and 15-minute figures mean?
The 5 minutes is your recovery point: backups run often enough that, in a serious failure, at most the last five minutes of work would need re-entering. The 15 minutes is the recovery target for bringing the environment back from disaster recovery. Larger databases can take longer to restore, and we state the figure for your system in the proposal.
What does the 99.9% uptime SLA cover?
Availability of your hosted servers and the connection into them, measured monthly and excluding maintenance windows agreed with you in advance. 99.9% allows roughly 43 minutes of unplanned downtime in a month. Maintenance is scheduled outside your working hours.
Do we still own our Sage licences and our data?
Yes. Your Sage licences stay yours, and so does your data. If you ever leave, we hand back a full database backup and help the next provider or your own IT team restore it.
What happens if our office internet goes down?
The system keeps running in the data centre, so nothing is lost. Users who still have a connection, for example staff at home, another branch or on a phone hotspot, can keep working. We recommend a backup internet line for offices that depend on Sage all day.
Will printing, scanning and Excel exports still work?
Yes. Printing goes to your local printers, and exports download to the user's own machine. We test printing and your key exports during the trial move, before anyone depends on them.
Can we keep our customisations and integrations?
In most cases, yes. Customisations, add-ons and integrations move with the system. The assessment lists anything that needs a change, such as an integration that connects to a local file share, and we fix it before go-live.