Keep one column per field and use consistent names, such as Name, Slug and Description.
CSV & Excel Import Guide
Prepare structured files before importing content.
Use a clear header row
Prepare structured files before importing content.
Keep one column per field and use consistent names, such as Name, Slug and Description.
One controlled path from source to sync.
Every step stays visible before anything changes in your CMS.
Include a stable identifier or unique slug if you need to match existing records during updates.
Reference fields may require matching existing CMS records. Verify the destination collection and relation format before applying changes.
Use mapping and validation to confirm that the imported values will land in the intended fields.
See what will happen before anything changes.
Automation can help with the work. Approval stays with you.
Keep one column per field and use consistent names, such as Name, Slug and Description.
Include a stable identifier or unique slug if you need to match existing records during updates.
Reference fields may require matching existing CMS records. Verify the destination collection and relation format before applying changes.
Use mapping and validation to confirm that the imported values will land in the intended fields.
What teams usually need to know.
Use a clear header row
Keep one column per field and use consistent names, such as Name, Slug and Description.
Keep identifiers consistent
Include a stable identifier or unique slug if you need to match existing records during updates.
Check relationships
Reference fields may require matching existing CMS records. Verify the destination collection and relation format before applying changes.
Review before syncing
Use mapping and validation to confirm that the imported values will land in the intended fields.
Review first.
Sync when you are ready.
Smart Sync keeps mapping, validation and review visible before changes reach your CMS.