Saved mappings reuse a source file layout within your workspace. They contain mappings, not the imported records themselves.
Save
- Complete Map columns and Pre-flight check.
- In Review & submit, turn on Save this mapping for next time.
- Enter a descriptive name, then click Start Import.
- Check the separate Mapping saved notification. Saving happens after job creation; a mapping-save error does not mean the import job failed.
For a pipeline, each entity step is saved separately with the entity type appended to the supplied name.
Reuse
Select a CSV with the same header names and choose its entity types. In Map columns, matching saved layouts appear as named buttons under Saved mappings for this file layout:. Click the appropriate name to load it, then review every field and the pre-flight results.
The layout match is based on header names; column order may change, but renamed, added or removed headers change the layout match. Mappings to columns absent from the file are not loaded. Recheck date format and current custom-field definitions rather than assuming the saved mapping supplies every import setting.
Manage
The current wizard offers loading and saving, but no Saved mappings management section or delete button. Use clear versioned names when replacing a layout. An administrator or integration maintainer can inspect available operations in the Importer API reference; do not look for a deletion control on the main Import page.