Seven checks before moving work to the cloud
Assess cloud collaboration, continuity, records, security responsibilities, growth costs, email and online sales against the work your business needs.

Moving a business function to a cloud service changes who operates the technology. It also changes the tasks your own organization needs to manage.
Choose one function and compare the proposed service with the current arrangement. These seven checks cover common uses. Some records and applications may be better left where they are.
1. Test collaboration with the real participants
Use sample files to test an edit, a review and a handoff. Include staff working remotely and external participants where required.
Check ownership, permissions and version handling. Check that guests and staff on phones can open and edit what they need, since some features work only in the desktop app or for internal users.
2. Test continuity when the service is unavailable
Identify what staff can do during an Internet, identity or supplier outage. Check whether the alternative workflow depends on the same failed service.
Syncing isn’t the same as a backup: a file deleted or encrypted on one device is deleted or encrypted everywhere it syncs. Check what the service can restore, for how long, and who’s responsible. The Cyber Centre’s backup guidance covers copies and restoration.
3. Place records according to their requirements
Identify which records the function creates and where they will be stored. Review access, retention, location, export and deletion requirements.
Keep an owner for shared work after an employee leaves. Test a representative export before committing important records to a new service.
Paperless work still needs a process for records that arrive on paper or through another system.
4. Map security responsibilities
The provider protects its data centres and platform. Your organization still sets up accounts, sharing and devices. Ask which security controls come with the plan you’d buy.
The Cyber Centre’s cloud contract guidance explains how responsibilities are shared.
Assign someone to review alerts and exceptions.
5. Model growth and recurring costs
Compare current usage with a plausible increase in users, storage or transactions. Include add-ons, support, integration, export and renewal commitments.
Check whether a smaller plan can be used again after growth or whether data and terms make that difficult. Even a service that grows easily needs someone watching licences and usage, or unused accounts keep billing.
Record the work your staff or provider will continue to perform.
6. Review a hosted-email workflow
Test account setup, shared mailboxes or other required functions, departures and recovery. Include devices or applications that send mail, such as a scanner or an accounting system.
Hosted email takes the mail server off your hands. Your organization still manages accounts, the domain’s DNS records and mailboxes.
Confirm the migration and continuity arrangements before retiring the existing service.
7. Test the complete online-sales process
If evaluating a hosted store, run a test order through payment, fulfilment, cancellation and reporting. Include the records needed by finance and customer service.
Review platform terms, integration costs and how you’d get your data out if you leave.
Use the trial results and outstanding responsibilities to decide whether to move the function, revise the proposal or keep the current arrangement.


