Sage 300 People on a private cloud
Payroll and employee records on dedicated servers, with the access controls, audit trails and backups your auditors check first. Moved between payroll runs, supported by people who know Sage 300 People.
The security stack
The controls your auditors will ask about, in one list.
Salaries, bank details, ID numbers and medical notes are the most sensitive data a company holds. Every control below is part of the standard service. None of them is an optional extra.
Payroll and employee data sit on servers used only by your company. Nothing is shared with another organisation.
Data is encrypted with 256-bit AES when stored and when it travels between the user and the server.
Every user proves who they are with a second factor, wherever they log in from.
Payroll officers, HR, managers and employees each see only the records their role allows.
Access to employee records is logged, and the logs are available when your auditors ask.
Backups can't be changed or deleted once written, with a recovery point of 5 minutes and a 15-minute recovery target.
You choose where the data lives: Middle East, Asia or Europe. Backups stay in the same region.
Why host payroll with a Sage partner
A general hosting company can keep a server running. It can't tell you why the payroll run failed to post to the general ledger, or why a payslip template stopped printing.
We look after both the server and Sage 300 People, so a problem during a payroll week is one call. The hosting facilities are independently audited, which gives your auditors evidence rather than a promise.
The international standard for information security management: people, physical access, systems, networks and continuity.
An independent auditor tests that the controls actually worked over a period of months, rather than checking that a policy exists.
The payment card industry's rules for physical security and access to customer equipment at the data centre.
Certification scope applies to the hosting facility and is confirmed for your chosen data centre in the proposal.
Field note, anonymised
"Our board wanted to know exactly where 2,000 employee records were kept and who could see them. With a dedicated server and the audit logs, we could answer both questions in one meeting. The payroll sync has run without issues since the move."
How the move works
Your users keep working until the last evening.
Moving Sage 300 People 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 300 People cloud questions
When do you move payroll to the cloud?
Between payroll runs. We plan the final sync for the quiet days after a run has been paid and before the next cut-off, so no pay period is ever split across two systems.
Can employees still use self-service?
Yes. Employee self-service for payslips, leave requests and approvals keeps working, and it is reachable securely from outside the office without a VPN.
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.