Understanding Field Mapping

Field mapping tells TableSync which source data goes into which Airtable column.

How It Works

When you create a sync, you'll see a list of available fields from your source (like "email", "firstname", "phone"). For each field, you choose which Airtable column it should map to.

Required Mappings

Every sync needs at least one ID field mapped. This is used to:

• Match records between syncs
• Update existing records instead of creating duplicates
• Track which records are new vs. updated

Common ID fields:

• HubSpot Contacts: email
• Shopify Orders: id
• Mailchimp Subscribers: email

Auto-Matching

TableSync tries to automatically match fields with similar names. For example, if your Airtable table has an "Email" column, it will auto-match to the source "email" field.

Skipping Fields

Leave a field unmapped to skip it. Only mapped fields are synced to Airtable.

Tips

• Airtable column types should match the data (text for text, number for numbers)
• You can update mappings later by editing the sync
• Unmapped source fields are ignored, not deleted