Colour theme
Book a consultation

Leaving a cloud service without losing records

Plan a cloud exit around tested exports, replacement sign-ins, contract dates and record retention before you cancel access or request deletion.

Laptop, monitor and external drives on an office desk.

Cancelling a subscription can remove access to years of invoices, messages and customer records. The final bill and the final day you can retrieve those records may fall on different dates.

Give someone responsibility for the exit before pressing Cancel. They need to confirm what the business is keeping, test the replacement and obtain the provider’s current access and deletion terms.

Confirm what cancellation means for this account

Read your contract alongside the provider’s documentation. Record the notice period, remaining commitment, final charge and dates when staff and administrators lose access. If you bought through a reseller, confirm the process with them too.

Microsoft’s subscription guidance shows why you can’t count on a grace period you remember from elsewhere. The timeline depends on how you bought the subscription and whether you let it lapse, cancel it or delete it. Once a subscription is disabled, only administrators can reach the data. Deleting a subscription outright removes SharePoint and OneDrive content immediately.

Google’s Workspace cancellation guidance also separates subscription cancellation from deleting the organization’s account. Export what you need first and confirm how your particular edition and account type are affected. Third-party application data needs its own exit process.

Inventory records and connections

Ask the people who use the service what they need to carry forward. Include attachments, comments, transaction history, audit records, reports and settings as well as the main records.

List incoming and outgoing connections: website forms, accounting imports, scheduled reports, mobile apps and automated workflows. Check whether the account supplies sign-in for other tools. Losing access to your identity provider can affect services you’re keeping.

Choose a cutover date and explain where new work will be recorded during the move. Otherwise, staff can continue adding information after you’ve exported the old system.

Test the export in the place you’ll use it

Download exports using a business-owned account and store them in a protected location the organization controls. Check what the export tool leaves out. A spreadsheet may preserve invoice amounts while losing the relationship between invoices and customers.

Open samples of each file type. Check dates, accents, attachments and links. If you’re migrating, import representative records into the replacement and have staff complete normal tasks with them. Confirm permissions separately; an import can succeed with the access rules still wrong.

Record any gaps and resolve them while the old service remains accessible. If you need a final export after cutover, schedule and verify it before access ends.

Move sign-ins before removing the old account

Test new administrator and staff sign-ins, recovery methods and integrations. Keep recovery information under business control. Confirm that billing, domain management and backup administration don’t depend on an account you’re about to close.

Revoke obsolete API keys and connections after the replacement works. Keep a written record of the change, including who verified each dependency.

Separate retained records from data to delete

The migration copy may contain personal information that doesn’t belong in the replacement. Apply your retention policy and check legal holds, accounting needs and sector requirements before deciding what to remove.

Under PIPEDA, outsourcing processing doesn’t transfer the organization’s accountability to its supplier. The Privacy Commissioner’s processing guidance describes using contractual or other measures to protect that information. Ask how the exit terms address return, deletion, subcontractors and backups.

Obtain written confirmation of what the provider will delete, what it will retain and the reason and schedule for that retention. Backup copies and billing records can outlast the cancellation.

Close the service with an exit record

Keep the tested export inventory, replacement checks, cancellation notice, final invoice and deletion correspondence together. Assign an owner and retention schedule to any archive you’ve kept.

Before closing the ticket, have staff test a real transaction in the new system. Check that new enquiries, invoices and reports arrive where they should. That final check can catch a connection missed in the inventory.


Featured Image Credit