Check exported records, attachments, dates and relationships before cancelling a cloud app, then test whether you can read and use them outside the service.

Direct answer: Keep the subscription active until you have reconciled the exported records and files, opened representative material outside the service, and completed a real task with it in the intended destination. Check attachments, relationships and dates separately from row counts. If essential material is missing or still requires the old account to open, the export has not yet passed a useful exit test.

A downloaded archive can look reassuring while containing links to files rather than the files themselves. A spreadsheet can contain every visible row but omit the relationships that made those rows meaningful. The relevant question is whether you can recover useful work after access changes, not whether the download completed.

My recommendation is to budget a short period of overlapping access when the records matter. Avoiding one extra renewal is a poor trade if the alternative is cancelling before you know what survived. This takes the exit questions from the technology retrospective for small teams and turns them into a bounded acceptance decision.

Applies to: authorised exports from cloud document and database applications. Notion and Airtable examples are based on current documentation, not hands-on migration testing. Actual permissions, formats and destination requirements must be checked for your account.

Define the export acceptance test

The export acceptance test is an editorial method: decide what must remain usable, compare it with what actually left the service, then demonstrate the intended future use. It separates a readable archive from a working migration because they have different acceptance conditions.

An archive may only need to preserve a report and its supporting evidence. A migration may need editable records, links between tables, attachments, permissions and ongoing work. State which you need before selecting a format. A PDF that preserves appearance can be appropriate for reading yet unsuitable for continuing a database workflow.

Prerequisites are authorised export access, sufficient approved storage, a destination you can test, the renewal deadline and a named person able to judge the retained material. Check who is allowed to see the export before downloading it. Exported files may no longer inherit the application's access controls. Keep sensitive material in an approved protected location, and do not upload it to a trial service until its access and data terms are acceptable.

Keep the source unchanged while testing and preserve an untouched copy of each export. Record when it was taken and what it includes. Cancellation, access removal and deletion are separate decisions; do not use deletion to test recovery.

Establish what should be present

List the records, date range, attachments, linked tables, comments and other material needed for the future task. Record any deliberate exclusions. An authorised export may legitimately omit private material, but you must know whether that omission affects the job you are trying to preserve.

Use the application's documented counts and export scope, not the number of items visible on the current screen. Check filters, hidden fields and permissions. In Airtable, the CSV export guidance explains that exporting all records requires an unfiltered view, and only visible field values are included. Tables are exported separately; this is not a whole-base restoration file.

Notion documents that workspace exports omit pages the exporter cannot access, and some teamspace settings can exclude content. It also says reuploading an export does not instantly recreate the workspace. Those limitations matter if your acceptance condition is an operating workspace rather than readable pages. Notion export documentation.

Create a short inventory of expected material, with counts where available and a reason for each requirement. This inventory is your comparison point. If you cannot establish the scope, ask the provider or account owner before claiming that the export is complete.

Check records and files independently

Open the exported tables in a suitable approved application using an explicit import process where format interpretation matters. Keep the original file unchanged. Compare total records and required columns, then inspect examples containing blank values, leading zeros, punctuation, long text and ambiguous dates.

An identifier such as a product code should remain an identifier, not become an altered number. A date should retain its intended day, month and, where applicable, time zone. Compare against the source rather than deciding that a plausible-looking value must be correct. If the destination interprets something differently, adjust the import mapping or field type and retest from an untouched copy.

Treat attachments as their own set. Airtable documents that CSV attachment fields contain filenames and URLs, while the actual files need separate handling. Its attachment URL guidance explains that download links expire. A link that opens immediately after export does not establish that you have retained the file.

Verify that required files exist in your approved destination, retain meaningful names or an index, and open without relying on the source account. Use a separate browser session or an appropriate offline test for genuinely local files. Do not make private files public to remove a login obstacle. A permission problem needs an authorised transfer, not weaker protection.

Rebuild meaning before trusting matching totals

Check relationships between records. Can you still identify which project an attachment belongs to, which organisation a contact represents and which note qualifies a decision? A relationship may survive as text without functioning as a clickable or enforceable link in the destination.

Choose a complete example and follow it through the exported material. Start with a project, find its contacts and documents, then answer a question a colleague would actually ask. Record any manual reconstruction. If that effort is required for every case, include it in the migration estimate rather than calling it an isolated inconvenience.

Check material that may fall outside ordinary rows, such as explanations stored in comments or field descriptions. Airtable explicitly lists several exclusions from its CSV exports, including record-level comments and field descriptions. Export scope and limitations. Decide whether you need to retain such context separately before the account changes.

Work through a small archive example

These are explicitly illustrative assumptions for a design studio, not a measured migration. The source contains 1,200 project records: 900 text-only records, 240 with one attachment each, and 60 with three attachments each. Expected attachments total 240 + (60 × 3) = 420 files.

The first export shows 1,200 rows, but the downloaded attachment folder contains 396 files. The deficit is 420 − 396 = 24 files. Matching row totals have therefore not established completeness. The studio must identify the absent files, including whether repeated attachments are deliberately stored once, before deciding whether the discrepancy represents loss.

Suppose an illustrative inventory expects those attachments to total 840,000,000 bytes, while the download contains 792,000,000 bytes. The difference is 48,000,000 bytes. File sizes provide another discrepancy signal, not proof of which files are missing or whether the others are valid. Where the export transforms files, compare against the documented transformation rather than demanding identical sizes blindly.

For content inspection, the studio initially chooses ten records from each of the three groups, plus every known unusual case. Thirty routine examples are 30 ÷ 1,200 × 100 = 2.5% of records. This is a practical starting sample, not a statistically certified accuracy rate. Any systematic failure triggers checks across all affected records. Essential evidence may require complete inspection.

Assume one additional month of the old subscription costs £36 and the replacement costs £18. The overlap month costs £36 + £18 = £54, versus £18 after transition. The incremental cost of keeping the old access for verification is therefore £36. These are invented planning amounts, not quoted prices. Staff checking time is additional, and the overlap does not guarantee recoverability unless you use it to resolve the discrepancies.

Make the destination pass a real task

For an archive, ask an authorised colleague to locate a named record and its supporting document without opening the original service. Success means they can find and interpret the evidence, not merely search a filename.

For a migration, import a representative subset into a separate test area and complete an ordinary update or reporting task. Verify the imported result against the source and document what must be rebuilt. Retain the test separately until the acceptance conditions are met, so a failed import does not contaminate live work.

Decide whether to cancel within one working week

  1. On day one, record the deadline, required scope and permitted storage. Take the export and preserve an untouched copy.
  2. Over the next two days, reconcile counts and files, then inspect representative content and relationships. Expand checks wherever a failure appears.
  3. By day four, complete the destination task with an authorised colleague. Record remaining defects and any needed manual reconstruction.
  4. On day five, cancel only if essential requirements pass and changes since the export are accounted for. Otherwise retain access and resolve the named gap. Stop the exit if critical records cannot be recovered, permissions remain disputed or the destination cannot perform the required task.

Use a longer schedule when provider export times or the volume of records require it. The sequence matters more than forcing a risky migration into five days.

Frequently asked questions

Is a CSV export a complete backup of my application?

Usually you should treat it as an export of particular tabular content, not assume that it restores the whole application. Check the provider's documented scope and test what your destination can reconstruct. Relationships, permissions, comments, attachments or configuration may need separate treatment. A CSV can be entirely appropriate when the future task only requires a table of values. The mistake is expecting more than the format and product export promise. Keep a written acceptance condition so you can distinguish a useful limited archive from an incomplete migration rather than describing both simply as a backup.

Do matching record counts prove that nothing is missing?

No. Equal totals can conceal altered values, duplicated records replacing missing ones, absent attachments or lost context. Compare stable identifiers where available, inspect required fields and reconcile the separate file inventory. Use a representative sample to discover systematic problems, then widen the check according to what fails. The consequence of an error matters: an archive of replaceable planning notes and an essential evidential record warrant different inspection effort. Counts are a valuable first signal, but they cannot tell you whether the retained material still means the same thing or supports the intended future work.

Can I wait until after cancellation to download attachments?

Do not assume you can. Access, retention and exported-link behaviour depend on the provider and account, so preserve required files while your authorised route is available. Some export links are temporary, as Airtable documents for attachment download URLs. Check that you have the actual files in controlled storage, not a folder of shortcuts. If cancellation only takes effect later, use the verified remaining period deliberately rather than relying on it from memory. Where the deadline is close, prioritise essential files and seek provider help, but do not claim an incomplete download has passed the exit test.

Should I use PDF, HTML or a spreadsheet for the archive?

Choose the format against what you need to do afterwards. A fixed reading copy, navigable pages and editable tabular values have different purposes, so a single format may not preserve every required use. Test an example in the intended reader or destination before exporting everything. If both appearance and reuse matter, retaining more than one documented export format can be justified. Include the extra checking and storage in the plan. Do not infer that a format is superior because it opens easily; a readable page may still omit attachments or the structure needed to continue working.

How do I handle records changed after the first export?

Record the export time and agree how subsequent changes will be captured before the final transition. Depending on the product, that may mean a documented final export or a controlled list of changes that you reconcile into the destination. Do not assume an incremental export feature exists. Avoid a prolonged period in which both systems accept changes without a named source of truth, because differences become difficult to explain. If you cannot account for intervening updates, delay cancellation and resolve that gap. A valid test of last week's data does not preserve the work added since then.

Can I delete the old account once the export passes?

Passing the export test supports an exit decision, but it does not by itself settle account deletion. Check the provider's cancellation and deletion rules, organisational retention requirements, ownership and any continuing contractual obligations. Keep the approved archive accessible to the people who need it, with its sensitivity reflected in storage permissions. Requirements vary by country, sector and agreement, so obtain qualified local advice for a specific disputed retention or privacy decision. Avoid retaining everything indefinitely merely because storage is available, but do not destroy the source until the responsible owner has approved the separate deletion decision.

Sources and verification

The parent was read in the publication's project; its public category URL could not be retrieved. Internal links follow the supplied article register. Example counts, costs and checking times are illustrative editorial assumptions.

Twokq Tech

This article is practical guidance. Apply it in proportion to your tools, evidence, risks, and responsibilities.