Platform Exit and Data Portability Review (Handoff)

Platform Exit and Data Portability Review (Handoff)

1. 01

   Inventory every asset the no-code build produced before the exit conversation starts

   List the data tables, workflow logic, integrations, user roles, and any AI agents or prompts embedded in the app. A client portal assembled in Noloco or a dashboard built in Jet Admin typically hides logic in field formulas and automation rules that are invisible on the front end.

2. 02

   Confirm contractual ownership of the app, the underlying data, and the platform account

   Check whether the retainer names the client as account owner or the agency. If the agency holds the license, agree in writing who pays the next renewal and who controls the workspace after the engagement ends.

3. 03

   Export structured data in a format the client can re-import elsewhere

   Pull CSV or JSON dumps of every table and verify row counts against the live app. Screenshots and PDF reports are not a data export; a client moving off Airtable or Knack needs relational structure preserved, including linked-record IDs.

4. 04

   Document the workflow logic in plain language the client's next team can rebuild from

   Write one paragraph per automation covering trigger, condition, action, and the business rule behind it. This is the artifact that survives a platform change; the visual builder does not travel.

5. 05

   Test the export against a fresh environment before signing off

   Recreate two or three core screens in a spare workspace using only the exported data and the written logic notes. Gaps found here are cheap; gaps found after the retainer closes become disputes.

6. 06

   Re-read the platform's current terms for monetization and data-handling clauses

   Terms move faster than contracts. A ClipJury audit found 105 of 175 AI tools changed monetization-related terms between June and October 2026, so confirm the exit plan still holds under the version live at handoff.

7. 07

   Hand over credentials, admin roles, and a named contact for the transition window

   Transfer ownership rather than sharing logins. Set a 30-day support window with a defined scope so the client is not left guessing who to call when a workflow breaks.