Before an MVP handoff, test whether its data can leave

A working MVP can still be difficult to hand over if its business records only make sense inside the original application. Before choosing the next development phase, try exporting one complete customer workflow and explaining it without opening the app. This is a practical scope check, not a demand to build a universal migration system in the first release.

1. 01

   Imagine a repair business with customers, jobs, visit notes and photos. A spreadsheet of job titles looks like an export, but it is not enough to reconstruct which customer requested a visit or which photos belong to that visit. Start by naming the records that matter to the business and the relationships needed to understand them. Give each exported record a stable identifier and use those identifiers consistently in related files.

2. 02

   Choose one representative example with a completed job, a follow-up visit and an attachment. Export it, then ask someone unfamiliar with the app to trace the sequence. They should be able to identify the customer, distinguish the visits and connect each attachment to its source record. Include a short field guide for status values, dates and units. A column named total is ambiguous if nobody knows what it counts.

3. 03

   Separate an operational export from a backup. An export can help staff reuse selected business records, while a recoverable backup may also need configuration, permissions and other application state. Do not promise disaster recovery just because a CSV download works. Write down exactly what the export includes and which recovery questions remain outside its scope.

4. 04

   Attachments deserve their own check. A list of temporary download links can become unusable later. Decide whether the handoff includes the actual files, durable access controlled by the customer, or a documented retrieval process. Record filenames or identifiers that connect files to exported rows. Test with two attachments that originally had the same filename so a copy operation cannot silently replace one with the other.

5. 05

   Export access should follow the sensitivity of the records. A staff member allowed to view one assigned job does not automatically need permission to download the entire customer directory. For the first release, an administrator-run export may be a reasonable tradeoff: fewer self-service controls, but a clear owner and a documented turnaround. Keep customer values and exported file contents out of general analytics.

6. 06

   Define a small acceptance exercise for the handoff. Check expected record counts, missing relationships, date interpretation and attachment availability. Use representative test data to reconstruct a few records in a separate scratch environment. Record what was lost or required manual interpretation. The goal is not to reproduce the whole product; it is to expose dependencies before they become an urgent migration problem.

7. 07

   This work has a cost, so constrain it to the records the business would need to keep operating. A readable export and a short field guide can be enough for an early pilot, while a recurring integration may need a more formal contract later. Measure the exercise by whether another person can explain and reuse the records, and by the unresolved gaps they find. Counting successful download clicks would miss the main question: did useful business information actually survive the handoff?