# UI Bakery vs AT Migrator: Airtable to PostgreSQL tools compared

UI Bakery and AT Migrator both move data from Airtable into PostgreSQL, and both start the same way: connect Airtable, connect Postgres. What decides whether the result is actually usable afterward is not how the setup form looks. It is whether your base's relational and computed structure, linked records, lookups, rollups, formulas, and attachments, survives the move, or whether Postgres just ends up holding the same cell values with none of the logic that made the base work.

## Key takeaways
- UI Bakery does not support linked records, rollups, lookups, or formulas, at least not that its product page or FAQ say anywhere, and that is exactly the part of a base that determines whether a migration is complete. AT Migrator maps linked records to foreign keys or junction tables by cardinality and translates rollups, lookups, and formulas into SQL.
- Attachments are explicitly listed as a supported field type on UI Bakery's page, but where the files end up and what happens to one that fails to copy is not specified. AT Migrator copies files to your own S3-compatible bucket, stores each file's URL, name, and size, and only retries the files that failed on a re-run.
- Airtable caps every tool at 5 requests per second per base. UI Bakery's FAQ gives no specific number for the largest base it handles or what happens if a run is interrupted. AT Migrator retries automatically when it hits that limit, resumes an interrupted run instead of starting over, and covers self-serve bases up to 100,000 records and managed migrations up to 500,000 and beyond.
- The setup mechanics differ too: UI Bakery has you type in each table name and whitelist a fixed IP address on your database firewall. AT Migrator reads your base automatically and needs no IP allowlist. These matter less than whether your data actually arrives complete.

## What each tool is
UI Bakery is a low-code platform for building internal tools and admin panels on top of a database. This Airtable-to-PostgreSQL tool is one of its free, no-signup utilities. AT Migrator is a dedicated migration product: moving Airtable data into PostgreSQL is the whole product, not a feature attached to something else.

## Does UI Bakery migrate linked records, rollups, lookups, or formulas to PostgreSQL?
**No, not as far as UI Bakery publishes anywhere.** UI Bakery's product page lists its supported data as "text, numbers, dates, attachments, and more." Linked records, rollups, lookups, and formulas are not on that list, and not mentioned anywhere else on the page or in its FAQ either. If your base is a handful of flat tables with no links or formulas, that will not matter to you. If it has any relational structure at all, UI Bakery is not built for that part of the move.

AT Migrator treats this as the core of what a migration has to do. It reads the setting Airtable stores on each side of a link field for whether that side allows one record or many, and maps the relationship accordingly: one-to-many becomes a foreign key column, many-to-many becomes a junction table. Rollups and lookups are recreated as SQL, joins and aggregate queries that read from the new foreign keys rather than a stored snapshot. Formulas are translated into SQL expressions, so a value that used to be computed by Airtable is computed the same way by Postgres.

> What makes a migration complete: If a migration tool does not say how it handles linked records, rollups, or formulas, take that as a no for now. It is the hardest and most valuable part of moving off Airtable, and worth confirming for yourself before you commit a complex base to any tool.

## Does UI Bakery preserve attachments as usable files?
**Yes, attachments are explicitly listed as supported, but where the files end up and what happens to one that fails to copy is not specified.** UI Bakery's page names attachments as a supported field type, so this is one area where its documentation is direct. What it does not say is where a file lands once it is out of Airtable, or how a migration behaves if a single attachment fails to copy partway through a large run. AT Migrator copies attachments to your own S3-compatible bucket and stores each file's URL, name, and size in the database alongside the row it belongs to. If a file fails to copy, only that file is retried on a re-run, not the whole table.

## Will a large or complex base survive the migration intact?
**On a large base, assume an interrupted run means starting over: UI Bakery does not document a way to resume, and its FAQ will not commit to a size limit.** Airtable limits every tool, UI Bakery and AT Migrator alike, to 5 requests per second per base. UI Bakery's FAQ says the size it can handle "depends on server capabilities and network speed" rather than giving a number, and says nothing about retrying or resuming once that limit is hit. It runs in the open browser page with no mention of saving progress, so a run that stalls or gets interrupted is a run you restart from scratch.

AT Migrator reads Airtable one table at a time and retries automatically when it hits the rate limit, rather than reading several tables in parallel and risking a block. A migration keeps running after you close the tab, shows which step is running and how many rows have moved, and emails you the status when it finishes. If it is interrupted, it resumes from where it stopped: tables already finished are skipped, and a partly-read table picks up where it left off. Self-serve migrations cover bases up to 100,000 records; larger bases are handled as a managed migration up to 500,000 records and beyond.

## What about setup: tables, auth, network access?
This part is worth knowing but should not decide much on its own. UI Bakery has you type each table name into a field and click Add, authenticate to Airtable with an API key, and whitelist a fixed IP address on your database firewall for it to reach Postgres. AT Migrator authenticates over OAuth or a personal access token and reads every table and field in your base automatically, including ones added later, and connects to Postgres over a standard TLS connection string with no IP allowlist needed.

## Which one fits your situation
- **Base has linked records, rollups, lookups, or formulas you want to keep:** UI Bakery does not support this. AT Migrator maps those into foreign keys, junction tables, and SQL.
- **Attachments need to land somewhere specific, or the base is large enough that a failed file is likely:** AT Migrator copies files to your own bucket and retries only what failed.
- **A base that may take a while, or that you cannot guarantee will finish uninterrupted:** AT Migrator keeps running after you close the tab, resumes an interrupted run, and emails you the status when it is done.
- **Small, flat base, no linked records or formulas:** UI Bakery's free tool covers this case well.

## FAQ
**Does UI Bakery migrate Airtable linked records, rollups, lookups, or formulas to PostgreSQL?** No. Its product page and FAQ list support for text, numbers, dates, and attachments only, with no mention of linked records, rollups, lookups, or formulas anywhere.

**How does AT Migrator decide whether a linked record becomes a foreign key or a junction table?** It reads the setting Airtable stores on each side of the link field for whether that side allows one record or many. One-to-many becomes a foreign key; many-to-many becomes a junction table.

**Does UI Bakery's tool preserve attachments as usable files?** Attachments are listed as a supported field type, but the product page does not say where files end up after the migration or what happens if one fails to copy.

**Where does AT Migrator put attachment files?** In your own S3-compatible bucket. The database stores each file's URL, name, and size alongside its row. Only files that fail to copy are retried on a re-run.

**What's the largest Airtable base AT Migrator can migrate?** Self-serve migrations cover bases up to 100,000 records. Larger bases are handled as a managed migration up to 500,000 records and beyond.

**What happens if a migration is interrupted partway through?** AT Migrator resumes from where it stopped rather than starting over. Tables already finished are skipped, and a partly-read table picks up from where it left off. UI Bakery does not document a way to resume an interrupted run, so assume it starts over.

**Does UI Bakery's tool auto-detect tables from my Airtable base?** No. It has a "Tables" text field with an Add button; each table name is typed in and added by hand. AT Migrator authenticates and reads every table, field, and view automatically, including tables added later.

**Do I need to whitelist an IP address to use AT Migrator?** No. It connects to your Postgres database with a standard connection string over TLS. UI Bakery's tool asks you to whitelist a fixed IP address on your database firewall.

---
*Considering a migration? Book a free discovery call with AT Migrator: https://www.atmigrator.com*