Your Airtable formulas are the migration. Everything else is a CSV.

Description and use

Migrating Airtable bases to Appdor requires reconstructing formulas because CSV exports only contain evaluated results. Most formulas translate automatically, but unsupported functions like PREVIOUS_VALUE need manual handling.

Problem

Migrating Airtable bases to Appdor loses formula logic because CSV exports freeze formula results instead of expressions.

Outcome

Appdor can translate most Airtable formulas with minimal changes, but functions like PREVIOUS_VALUE are unsupported and require manual intervention. Linked records, views, buttons, interfaces, and automations also need special handling.

Workflow

• Inventory formula columns before migration
• Import base and review the fidelity report
• Rebuild unsupported formulas manually
• Diff sample computed values against Airtable before switching users

Evidence

Getting your records out of Airtable is not the hard part. There is a button for it and the rows come out fine.

Source

The hard part is that a CSV export gives you what each formula column last said, not what it means.

Source

Appdor reads 7 formula dialects and compiles them into its own expression language, so the expression moves and stays live.

Source

Some Airtable functions have no counterpart, and the compiler says so rather than guessing. Unknown function "PREVIOUS_VALUE" in dialect airtable.

Source

Both import routes show you what they are about to do before anything is written, and both name what they could not carry — the formulas they translated, the field types that fell back to text, and the ones that failed outright.

Source