Airtable Sync: Merging Data from Multiple Bases Without Duplicates

To merge data from multiple Airtable bases without creating duplicate records, use a stable record identifier and combine the synced data through a master table. Define how conflicts will be handled before you import anything, then review flagged records before treating the consolidated table as authoritative.

Plan the merge before syncing

Decide which base will hold the consolidated records and what each source table contributes. Keep the original data in its source base so you can trace information back to where it came from.

Create a master table with fields for:

• A unique record identifier
• Links to the relevant synced tables
• Record status
• Duplicate status
• Source notes
• Review owner

Use the same identifier logic across the source bases whenever possible. An identifier may be based on an existing reference field or a formula that combines several fields.

Set up the sync connections

In each source base, choose the option to sync a table to the consolidation base. Select the appropriate destination and review the available field mappings.

Before saving each connection:

1. Confirm that identifiers use compatible formats.
2. Check that required fields map to the correct destination fields.
3. Exclude attachments or lookup fields that are not needed.
4. Add source and review fields to distinguish incoming records.
5. Save the connection and inspect the resulting records.

Repeat this process for each source table. Keep a list of the connections so you know which base supplies each field.

Merge through a master table

Synced tables should normally remain separate. Use linked records to connect them to a master table instead of placing the same entity into every destination table.

For each incoming record:

1. Compare its identifier with the master table.
2. Link the record to an existing master record when the identifiers match.
3. Create a new master record only when there is no match.
4. Record which source table supplied each linked record.
5. Flag uncertain matches for manual review.

If a source table contains the same type of information as another source table, decide whether to combine the values, select one preferred source, or display both with source labels.

Create a duplicate-review process

A matching identifier can indicate either a duplicate or two genuinely separate records. Do not merge records solely because several fields happen to match.

Use a review table or filtered view with these fields:

• Unique identifier
• Candidate record
• Matching master record
• Conflicting field values
• Source base
• Review status
• Review notes

Ask a reviewer to choose one of these outcomes:

• Keep as separate records
• Link the records without merging them
• Merge selected fields
• Mark as unresolved

Document the reason for each outcome. Consistent decisions make later reviews easier.

Define conflict rules

Two records may share an identifier while containing different values. Before consolidating them, decide which source is authoritative for each type of field.

Use a simple field-level policy:

Information	Preferred source	Review needed
Contact details	Designated customer base	Yes
Contract status	Contract base	Yes
Project notes	Keep both with source labels	No
Internal status	Designated operations base	Yes

Avoid overwriting useful information automatically. Preserve the original value in a notes or history field when the preferred source contains a different value.

Add checks for incoming records

You can create an automation that runs when a record enters the consolidation base. Have it compare the incoming identifier with the master table and set a status such as new, matched, possible duplicate, or review needed.

The automation can also:

• Notify the assigned reviewer
• Add the source table name
• Record the review owner
• Stop repeated notifications for the same unresolved match
• Create a review task when field values conflict

Test the workflow with sample records before applying it to operational data. Confirm that each possible match creates the intended status and notification.

Maintain the consolidation base

Review unresolved duplicates, missing links, broken source connections, and changes to field mappings. Assign an owner to each check and record the outcome of manual decisions.

Use a recurring checklist that asks:

• Are all incoming identifiers present?
• Are identifiers consistent across source bases?
• Are possible duplicates resolved?
• Do conflicting records have a designated source?
• Are broken links corrected?
• Do source fields still map to the correct destination fields?
• Can each consolidated field be traced to its source?

Questions to ask the vendor

If your plan depends on advanced syncing or automation, ask the vendor:

• Which tables and field types can be synced?
• What happens when a source field is renamed or removed?
• How are deleted or restored records handled?
• Can a sync be paused or repaired?
• Which permissions control access to each base?
• Are automation and notification actions subject to separate limits?
• How can administrators identify failed connections?
• What support is available for duplicate-resolution workflows?

FAQ

Can records from several source tables appear in one master table?

Yes. Treat the synced tables as separate sources and link their records to a shared master table through a consistent identifier.

Should matching records be merged automatically?

Not always. Match the identifier first, then review conflicting values or uncertain matches before combining records.

What should happen when source tables contain different values?

Define a preferred source for each field, preserve alternative values where useful, and flag important conflicts for review.

How should deleted source records be handled?

Document whether source deletions should alter the master record. You may prefer to retain the consolidated record with an inactive status rather than remove it automatically.

Who should resolve duplicates?

Assign ownership to a person or role that understands the source data and the consequences of merging records.