Import existing work from Airtable

Airtable Import is an optional Source Import path for an existing workspace. Owners and admins open it from Settings → Organization → Imports. CSV and Google Sheets are shown as future import options; use Airtable or manual setup for the currently implemented flow.

Connect and choose a base

1. Open Imports and start an Airtable import.
2. In Connect Airtable, authorize access to the intended Airtable data.
3. In Choose Base, select the base and analyze its snapshot.
4. Continue to Review Mapping and select the target ConversionLab project.

A base cannot be selected until authorization completes. If the base list is unexpected, review which account and base access you granted.

Review the mapping before importing

Generate a mapping suggestion when that action is available. Review Tables, field mappings, Feedback, and Warnings. Correct the suggested destination and fields rather than assuming a source table's name expresses the intended ConversionLab concept.

For example, a table named “Roadmap” may contain ideas rather than experiments. Use the feedback field or mapping editor to state the correct interpretation. The Plan JSON tab exposes the saved import plan for closer review; ordinary imports can be configured through the table editor.

Choose Save mapping or Save and continue. An import runs from the saved mapping plan, so unsaved edits are not the plan that will execute.

Run and review

1. Open Run Import and start the background import.
2. Inspect progress rather than starting a duplicate import while one is running.
3. Open Review Results and compare imported, failed, skipped, and total records.
4. Read warnings and errors even if the import completed.
5. Open representative imported items in the target project and verify their fields and relationships.

When a step is locked, finish its prerequisite or wait for the running import. Preserve the import record when seeking help so the team can identify the failed stage. Airtable Import brings source data into ConversionLab; it should not be treated as a promise of continuous two-way synchronization.