Saving and Reusing Import Column Mappings
How to save a CSV import's column mapping and value choices by name, set a default, and reuse it so a recurring file is only mapped once.
A saved mapping remembers how a file's columns line up with BackOps fields, so the export you receive every month, or the price sheet a regular vendor sends, only has to be mapped once. Saved mappings belong to your organization and are shared with everyone who can run that kind of import.
What a Saved Mapping Holds
A saved mapping stores which file column goes to which field, the event type chosen as the default for rows without one, the column used to match existing records, and the value choices made on the Review values step: names you pointed at a different option, and values you excluded. Each mapping belongs to one import target, so an events mapping is never offered for line items.
Save a Mapping
The best moment to save is on the Preview import step, once you have checked the result. Select Save mapping, give it a name such as "Monthly ticketing export", and choose whether to Set as default. You can also save from the Map columns step, before any value choices have been made.
If you loaded a saved mapping and then refined it, the Preview import step offers to update that mapping by name, or Save as new to keep the original. Updating a mapping changes it for everyone in your organization.
Use a Saved Mapping
On the Map columns step, choose a mapping from the Saved mappings list. Its columns and value choices are applied to the file you uploaded. When your organization has a default mapping for the target, it is applied automatically to each new file, and you can switch to another mapping or to No saved mapping at any time.
When a file or your fields have changed since the mapping was saved, everything that still lines up is applied and the parts that no longer do are named, so you can map them again.
Rename, Change the Default, or Delete
Use the menu beside the Saved mappings list to rename the loaded mapping or delete it. Only one mapping per target can be the default; setting a new default clears the old one. Deleting a mapping removes it for everyone, and deleting the default leaves the target with none. Imports that already ran keep their own record of the mapping they used.