AT Migrator Airtable to PostgreSQL Cutover (Delivery)

AT Migrator Airtable to PostgreSQL Cutover (Delivery)

1. 01

   Run the published sample migrations (48,000+ record CRM and formula-heavy projects base) through AT Migrator before touching a client base

   Confirm linked records land as PostgreSQL foreign keys and that formulas, rollups, and lookups resolve as native SQL views rather than static values. This is the evidence you show the client at scoping, and it verifies the zero-data-retention architecture before a live base is exposed.

2. 02

   Open the migration time estimator and size the client base against the plan record ceilings

   Starter covers 5,000 records at $199 one-time, Professional covers 25,000 at $499, Business covers 100,000 at $999. A base over the ceiling needs the Done-for-you option or a split run, so settle this before quoting the project fee.

3. 03

   Stand up the three target resources: read-only Airtable API connection, client PostgreSQL database, and an S3-compatible bucket for attachments

   AT Migrator reads Airtable in read-only mode and streams records through memory, so the API token needs no write scope. Attachments do not go into PostgreSQL; they land in the bucket, and the client owns both endpoints.

4. 04

   Audit the base for field types, linked record depth, and formula dependencies, then map each one to its PostgreSQL target

   Document which rollups and lookups become views and which become generated columns. Flag any formula that references a field type AT Migrator does not translate so the client hears about it before cutover, not after.

5. 05

   Execute the migration inside the agreed cutover window and download the generated migration script

   The downloadable script is included from the Professional plan up, and it is the artifact that lets the client's own engineers re-run or audit the load. Keep it in the delivery folder as handoff material.

6. 06

   Validate row counts, foreign key relationships, and view output against the source base

   Spot-check every linked table for orphaned keys and open each recreated view to confirm it returns the same values the Airtable formula did. Record the checks in the delivery doc; this is what converts a one-time migration into a referenceable case study.

7. 07

   Hand off the final schema, the migration script, and the bucket location, then close the engagement

   AT Migrator is one-way and one-time, so there is no sync to monitor after cutover. Set expectations in writing that ongoing PostgreSQL work is a separate scope, since this cannot be resold as a monthly retainer.