An Import Mapping Template (also called an Import Configuration) is a CSV that maps headers from a third-party system to Finalsite Enrollment fields, so you don't have to manually transform the file every time you import. Useful for recurring imports like test scores or inquiries, where the source system always exports the same column names.
💡Quick Answers
- What does an Import Mapping Template actually do? Translates incoming column headers from your source system to the matching Finalsite Enrollment field name and entity, so the import tool can interpret the file without manual header changes.
- How do I build the mapping CSV? Download the sample template (linked in the article). Only the first two columns are processed: column 1 is the exact header name as it appears in the source file, column 2 is the matching Finalsite Enrollment field name including the entity prefix (CHILD, PARENT1, HOUSEHOLD1, etc.).
- How do I add the template to Finalsite Enrollment? Settings > Fields & Data > Import Configurations > Add a new import configuration, upload your CSV, give it a name, click Submit. It will then appear as an option on the Import Data tool.
- When should I use a mapping template instead of just renaming columns? When the import will recur on a regular basis or when the third-party headers won't change. For a one-off import, it's faster to rename the columns yourself.
- What's the most common gotcha with mapped imports? The first row of the upload must be the headers. No blank row, no title row above the headers. The mapping tool reads the first row as field headers and expects data immediately below.
- I need help building the template, who can I ask? Support can help configure a template based on the file format from your third-party system.
How-To: Create & Configure Import Mapping Templates
Create an Import Mapping Template
Click here (or right click + save link as...) to download the sample mapping template in .CSV format. Only the first two columns of the file are processed by the import tool.
The first column must be the name of the header in the first system. This must match exactly what is output as the header on the exported file. The second column must be the name of the field in Finalsite Enrollment to which this header corresponds, including the entity to whom the data will be imported. See the following image as an example.
Configure an Import Mapping Template
Once you have created and saved your import mapping template as a .CSV file, you are ready to set it up in the Finalsite Enrollment system so that you can use it on future imports.
- Go to Settings - Fields & Data - Import Configurations.
- Click on the green Add a new import configuration button at the top of the page.
- Upload a .CSV configured file as described above and enter a name for the import configuration. Then, click on the blue Submit button.
After you have done this, the mapping template will be available the next time you are run an import from Settings - Fields & Data - Import Data. When you run an import with the mapping template selected, the importer will automatically configure the headers.
Please note: Import files uploaded with a mapping template MUST have the first row be the file headers. There should not be a row above the first row.
If you need help at any point while creating and/or setting up your import mapping template, contact Support.
Â
Comments
0 comments
Article is closed for comments.