Pick the Payload collection that contains the destination fields; avoid assuming all collections share one schema.
Import Payload Collections
Prepare a collection import without changing its schema.
Select the target collection
Prepare a collection import without changing its schema.
Pick the Payload collection that contains the destination fields; avoid assuming all collections share one schema.
One controlled path from source to sync.
Every step stays visible before anything changes in your CMS.
Include meaningful column headers and a reliable identifier for any records you intend to update.
Review destination field types, including required fields, nested data and references where supported.
Inspect proposed creates and updates, resolve invalid values, then execute the approved batch.
See what will happen before anything changes.
Automation can help with the work. Approval stays with you.
Pick the Payload collection that contains the destination fields; avoid assuming all collections share one schema.
Include meaningful column headers and a reliable identifier for any records you intend to update.
Review destination field types, including required fields, nested data and references where supported.
Inspect proposed creates and updates, resolve invalid values, then execute the approved batch.
What teams usually need to know.
Select the target collection
Pick the Payload collection that contains the destination fields; avoid assuming all collections share one schema.
Upload CSV or Excel
Include meaningful column headers and a reliable identifier for any records you intend to update.
Map fields
Review destination field types, including required fields, nested data and references where supported.
Validate the batch
Inspect proposed creates and updates, resolve invalid values, then execute the approved batch.
Review first.
Sync when you are ready.
Smart Sync keeps mapping, validation and review visible before changes reach your CMS.