Platform Exit and Data Portability Review (Handoff)

Platform Exit and Data Portability Review (Handoff)

1. 01

   Inventory every object, table, and workflow the client's app depends on before any migration conversation starts

   Export a schema map covering record counts, field types, automations, and external API calls. A client portal built on Noloco that pulls from Airtable and HubSpot will have dependencies that never appear in the visual editor.

2. 02

   Score each dependency on portability: native export, API extraction, or manual rebuild

   Flag anything that only exists inside the platform's proprietary runtime. Semantic application definitions, as used by Buzzy, do not transfer to a conventional stack without a rebuild estimate attached.

3. 03

   Run a full data export and verify row counts against the live system on the same day

   Reconcile attachments, linked records, and file storage separately, since these are the fields most often dropped or truncated during export.

4. 04

   Document the rebuild cost in hours and dollars for the two most likely exit paths

   Price a conventional build and a migration to a second no-code platform. Agencies that quote only one path leave the client negotiating from a weak position at renewal.

5. 05

   Confirm who owns the account, the domain, and the underlying database before handoff

   Platforms differ on whether workspaces transfer between organizations. Establish ownership in writing while the retainer is still active, not after the final invoice.

6. 06

   Test the exported data inside the destination environment with a read-only user

   Load a sample of 200 records and confirm relationships, permissions, and calculated fields survive the move. Failures here surface as client-visible errors weeks later.

7. 07

   Deliver a written exit memo listing what transfers, what breaks, and what the client must rebuild

   Include the platform's export limitations in plain language. A client who understands that a Glide app's logic layer does not export will not blame the agency when the rebuild takes longer than expected.