Account transitions

If access is going to change,
archive before it does.

Closing an old account, leaving a job, shutting down a business, switching providers, cutting a storage bill, or losing a company login all create the same timing problem: the safest moment to preserve authorized history is while the source still works. The details differ, so use the path that matches your situation.

schedule
Before access changesConnect · preserve · let the job finish
fact_check
Before you rely on itOpen known records · check dates · search important items
power_settings_new
Then make the provider decisionClose · downgrade · leave · disconnect · or keep it

What should usually be on the transition checklist?

The exact answer depends on the source and your rights to the records, but these are the recurring categories.

mail

Email and attachments

Approvals, receipts, contracts, introductions, old addresses, decisions, client history, attachments, and conversations often become valuable only after the account is gone.

folder

Files with context

Keep important files with enough path, naming, date, and provider metadata to understand what they are later.

calendar_month

Meetings and recurring commitments

Calendars can preserve the shape of work and relationships in ways that a raw file folder cannot.

groups

People and organizations

Correspondence can become a private relationship history, but work/company data still requires the correct authorization boundary.

fact_check

Verification before closure

The preservation workflow is only complete when you have checked that the records you care about are usable from the archive.

shield_lock

Security and ownership

Provider permissions, tenant isolation, deletion, source ownership, and model processing matter more during transitions because the records are often sensitive and the decision can be irreversible.