Getting your own data out, before you need it

A business runs on records it does not physically hold. That arrangement is ordinary and sensible, and it rests on one assumption nobody tests.

The assumption is that somebody could retrieve the data in an emergency. Trying it once is the only way to know.

Export it, and then open it

A file that downloads is not proof. The test is whether the contents are usable: the right rows, readable dates, and the links between records intact.

Most people discover something surprising on the first attempt, and the time to discover it is not during a crisis.

An export omits more than people expect

A table export carries the fields and rarely the attachments, the notes, the history or the relationships between tables.

Those absences matter enormously if the export were ever needed in earnest. Knowing which ones apply is more useful than the file itself.

Documents need their own copy

Records and documents usually live in different places, and an export of one says nothing about the other.

Our guide to keeping documents in your own storage covers the arrangement where the business already holds those directly, which removes half this problem.

A copy in the same system is not a backup

A duplicate held inside the same account protects against somebody deleting a record. It protects against nothing else.

A genuine copy sits somewhere the main system cannot reach, held by the business rather than by the provider.

Date it, and keep more than one

A single copy overwritten each month is one bad export away from being useless. A corrupted file replaces a good one silently.

Several dated copies, with the oldest rolling off, costs almost nothing in storage and removes that failure entirely.

Decide who may export

An export is a complete copy of the business's information, which makes it exactly what somebody leaving on bad terms would want.

Restricting it to a small number of people, and recording when it happens, is ordinary care rather than suspicion.

Some records have a retention period

Financial records, employment records and client files each carry obligations that outlast the software holding them.

A business changing systems needs the old data readable for years. That argues for exporting at the change rather than trusting an old login.

Put it on the calendar

An export nobody scheduled happens once, during the week somebody worried about it, and never again.

A quarterly reminder, owned by one person, keeps the copies current and the process familiar enough to work under pressure.

Know how long a restore takes

A copy that exists is not the same as a business back on its feet. Reloading records, relinking documents and checking them takes real time.

A rough estimate of that tells a business whether its arrangement matches the downtime it could survive.

Leaving a system is the real test

Most exports happen during a migration rather than a disaster, and a migration exposes every gap at once.

A business that has exported and read the file already knows what needs rebuilding by hand. That changes how it plans the move.

Access usually ends on the day a subscription does, which is rarely the day the migration finishes. Exporting early, rather than at the end, avoids that entirely.

A read only period after cancellation is worth asking about before anybody commits to a date.

What to change first

• The first export gets opened and read, not just downloaded
• What an export omits gets written down beside it
• Documents get their own copy, separate from the records
• The copy lives somewhere the main system cannot reach
• Several dated copies exist, and the oldest one expires
• A quarterly reminder belongs to one named person