How do you ensure every IT support ticket or new employee record looks professional and contains the same essential information without typing it from scratch each time? Templates and data management tools are the answer, enabling you to create consistent records instantly and move data in and out of ServiceNow efficiently. For the SNOW-CSA exam, mastering these tools is vital because they directly test your ability to automate work, reduce errors, and handle bulk data operations, which are daily tasks for any ServiceNow administrator.
Jump to a section
A simple way to picture Templates and Data Management
A professional kitchen's recipe collection is the backbone of its consistency and efficiency. A head chef does not write out a full recipe from scratch every time a customer orders a dish. Instead, the chef reaches into a filing cabinet and pulls out the standardised recipe card for 'Mushroom Risotto'. That card is a template. It lists every ingredient with exact quantities, every step in the correct order, and the specific cooking temperature. It ensures that every risotto served to every customer tastes exactly the same, regardless of which junior chef on the line cooks it.
Now, imagine the restaurant receives a large shipment of new, high-quality porcini mushrooms. To update the menu, the chef does not rewrite the recipe card. She takes the existing 'Mushroom Risotto' template, saves a copy as 'Porcini Risotto Special', and edits the ingredient list. She has created a new record from a template, saving hours of work and eliminating the risk of forgetting a critical step like the stock temperature. This same principle applies to data management. When the restaurant needs to find every dish that uses 'arborio rice', the chef does not flip through every physical card. She uses a data import tool to scan the recipe index, or she exports the entire recipe collection into a spreadsheet to analyse costs. The template guarantees consistency, while the data tools allow the chef to organise, search, and update her recipes efficiently, preventing a chaotic kitchen where every chef cooks a different version of the same dish.
In ServiceNow, a 'template' is a pre-defined set of values that you can apply to a new record or an existing record to fill in fields automatically. Think of it as a form that someone has already partially completed for you. When you open a new incident ticket, instead of typing the priority, category, and assignment group every time, you can click a button called 'Apply Template' and all those fields are filled in instantly. This saves time and, more importantly, enforces consistency across your organisation. Every 'High priority' incident will always have the same category and assignment group because everyone uses the same template.
There are two main types of templates in ServiceNow. The first is a 'Record template'. This is a template you apply to a specific type of record, like an Incident or a User record. You create it by going to the appropriate module (for example, Incidents), opening a record, filling in the fields you want to save, and then clicking the 'Save as Template' option. You give the template a name and save it. The second type is a 'Global template', which can be used across different record types. This is less common in the exam but important to know exists.
Now, consider 'Data management'. This is the set of tools that let you bring data into ServiceNow (import) and take data out of ServiceNow (export). The primary tool for this is the 'Data Source' and the 'Import Set'. A 'Data Source' defines where your data is coming from, for example a spreadsheet file, a database, or an LDAP directory. An 'Import Set' is a temporary table where the data lands after being read from the source. Think of the Import Set as a parking lot. Your data arrives here, parked row by row. Once it is in this staging area, you run 'Transform Maps' to map each column in your spreadsheet to a field in a ServiceNow table (for example, mapping a column called 'Email' in your spreadsheet to the 'Email' field in the User table). This is called 'data transformation' because you are transforming the raw data into a format that ServiceNow can use.
Another critical data management tool is the 'Export' functionality. You can export any list of records from any table directly to a CSV (Comma Separated Values) or Excel file. This is useful for creating reports, auditing data, or sharing information with people who do not have access to ServiceNow.
The final major concept in this area is 'Data Source and Transform Map configuration'. You create a Data Source of type 'File' to upload a CSV. You then create an Import Set table (or use an existing one). Then you create a Transform Map. The Transform Map is the brain of the operation. It contains one or more 'Field Maps'. Each Field Map tells the system: 'Take the value from column X in the Import Set and put it into field Y in the target table.' You can also add 'Scripts' or 'Conditions' to a Transform Map to change data during the import. For example, you might write a script that converts a date format from 'MM/DD/YYYY' to 'YYYY-MM-DD' as it moves from the Import Set to the User table. Without these tools, entering hundreds of new users would take days of manual data entry. With them, it takes minutes.
Create the Data Source
Navigate to System Import Sets > Data Sources and click New. Choose 'File' as the type (for a CSV or Excel file). Give it a name, and upload your source file. This step defines where the data comes from and triggers the automatic creation of an Import Set table.
Verify the Import Set Table
After creating the Data Source, ServiceNow automatically creates an Import Set table named after your Data Source. Go to System Import Sets > Import Set Tables and locate your table. This is the staging area where the raw data sits before transformation. Verify the columns match your file headings.
Create the Transform Map
In the Data Source record, click the 'Transform Maps' related list and click New. Set the 'Target table' to the table where you want the data to end up (e.g., User). This map is the instruction set that tells ServiceNow how to process each row.
Define Field Maps
Within the Transform Map, click the 'Field Maps' related list and add a new map for each column. For each field map, select the source field (from the Import Set column) and the target field (from the target table). You can also add default values or simple scripts for data transformation here.
Run the Import
Return to the Data Source or Transform Map record and click 'Import' or 'Run Transform'. ServiceNow processes each row of the Import Set, applying the field maps and transforming the data into new records in the target table. Review the results for errors.
Create and Test a Record Template
Go to the target table (e.g., Incident), open a new record, fill in the fields you want to standardise, and click 'Save as Template'. Name it descriptively. Then open another new record and test applying the template to ensure the fields populate correctly.
Imagine you are a ServiceNow administrator for a large company called 'GreenLeaf Energy'. The HR department has just hired 50 new employees who all need user accounts created in ServiceNow. They send you an Excel spreadsheet with columns: First Name, Last Name, Email, Department, and Manager. Without templates and data import, you would have to manually create 50 new User records, typing each field one by one. This is slow and error-prone.
Instead, you use ServiceNow's data management tools. Here is exactly what you do step by step:
First, you go to the 'Data Sources' module in ServiceNow and create a new Data Source. You select 'File' as the type because you have a spreadsheet. You name it 'HR New Hires Q4'.
Next, you upload the Excel file. ServiceNow reads the file and creates a new 'Import Set' table. This table has columns matching the headings from your spreadsheet (First Name, Last Name, etc.). The data now sits in this staging table, but no User records have been created yet.
Then, you create a 'Transform Map' for this Data Source. You tell ServiceNow that the target table is 'User'. You create field maps for each column. For example, you map the 'First Name' column to the 'First name' field in the User table. You map the 'Email' column to the 'Email' field.
You also add a conditional field map: if the 'Department' column says 'Sales', you automatically set the User's 'Location' field to 'City Office'. This uses a simple script in the transform map.
Once the transform map is configured, you run the import. ServiceNow processes the 50 rows, creating a new User record for each one, filling in all the fields according to your maps. The whole process takes about five minutes instead of three hours.
Finally, you use a 'Template'. You go to the Incident module and create a template called 'Hardware Request - New Hire'. This template pre-fills the category (Hardware), the subcategory (Laptop), the priority (3 - Moderate), and the assignment group (IT Support). Now, when anyone in the company needs to report a hardware issue for a new hire, they simply open a new incident, select your template, and most of the form is already completed. This ensures every hardware request is tracked consistently and assigned to the correct team automatically.
As an IT professional, you also regularly use the 'Export' feature. Once a month, your manager wants a list of all active users. You go to the User table, filter for 'Active = true', select all the records, and click 'Export to Excel'. You send this file to HR so they can verify the list is accurate. This simple action replaces a manual audit process that used to take a day.
The SNOW-CSA exam tests your knowledge of Templates and Data Management with several specific question types. Expect questions that ask you to identify the correct sequence of steps for importing data. The exam loves to test the difference between a Data Source and an Import Set. A common trap is asking: "What is the first step to import data from a spreadsheet?" The correct answer is always 'Create a Data Source'. Many beginners think the first step is to 'Create an Import Set', but the Import Set is created automatically when you create the Data Source. The correct sequence is: Data Source, Import Set (auto-created), Transform Map, Run Import.
Another exam topic is the order of operations in a Transform Map. They ask: "Which happens first, field mapping or running a script?" The answer is field mapping happens first, before any script runs. The exam also tests your understanding of what a Template can contain. They might ask: "Can a template contain attachments or assignments to groups?" Yes, a template can contain values for any field on the form, including assignment groups and attachments. However, it cannot contain dynamic values like 'current date' unless you use a special variable. Traps include: "You can only apply a template to a new record." This is false. You can apply a template to an existing record by opening the record and selecting 'Apply Template' from the context menu.
Concepts the exam loves to test:
The difference between a Record Template and a Global Template.
The specific location in the navigation menu to find Templates (usually under the specific application's module or under System Definition > Templates).
The fact that you can apply multiple templates to a single record, but the last applied template's values overwrite any previous ones.
The requirement that a Data Source must be defined before an Import Set can be created.
The rule that an Import Set is a separate table from the target table; it is a staging area.
The ability to create a 'Scheduled Import' that runs automatically on a schedule. This is a common exam scenario for managing regular data feeds.
Trap patterns to memorise:
Do not confuse 'Import Set' with 'Update Set'. An Update Set is for moving customisations between instances, not for data import.
Do not confuse 'Template' with 'formatter' or 'workflow'. A template only fills form fields; it does not run business logic or workflows automatically (unless you configure an advanced script).
Watch out for questions that suggest you need to write complicated code for data import. The exam emphasises using the built-in wizard and field maps for most scenarios.
To prepare, practise creating a simple Data Source from a sample CSV file in a personal developer instance. Create a Transform Map and run the import. This hands-on experience will cement the steps in your memory far better than memorising them.
A Template pre-fills fields on a record to ensure consistency and speed, whereas data import tools move raw data into the system from external sources.
The Data Source defines where your data comes from and automatically generates an Import Set table to hold the raw data temporarily.
The Transform Map contains field maps that tell ServiceNow which Import Set column goes to which target table field, and it can run scripts to clean or convert data.
You can apply a template to both new and existing records, but it only overwrites the fields included in the template, leaving other fields unchanged.
Exporting data is done through the list view by selecting records and using the 'Export to CSV' or 'Export to Excel' option, which is essential for reporting and audits.
Scheduled data imports can be set up to automate the process, making regular data loads from HR systems or external databases hands-off after initial configuration.
These come up on the exam all the time. Here's how to tell them apart.
Record Template
Applies pre-filled values to a single record manually.
Does not create multiple records; only fills fields on one form instance at a time.
Used primarily for consistency when creating or editing individual records.
Data Import (Import Set + Transform Map)
Automates the creation of many records from bulk external data.
Creates multiple records in one operation (hundreds or thousands at once).
Used for onboarding large data sets, like migrating users or importing asset inventory.
Template (Record Template)
Applied from within the same table it was created for.
Cannot be used on different table types (e.g., an Incident template only works on Incident forms).
Stored in the specific table's template list.
Global Template
Available across multiple application modules, but still restricted to the table it was created for.
Can be accessed from a broader navigation context, but still only applies to its intended table.
Stored in a global scope list, making it easier to find across the system.
Import Set Table
Temporary staging table that holds raw imported data.
Data here has not been mapped or transformed yet.
Not intended for end-user access or reporting; it is a processing zone.
Target Table (e.g., User table)
Permanent table where final, cleaned data resides.
Contains data that has been mapped and transformed according to business rules.
Used for daily operations, reporting, and user interactions.
Mistake
When I apply a template to an existing record, it completely replaces all existing field values with the template's values.
Correct
A template only overwrites the fields that are defined in the template. Any fields not in the template remain unchanged. This prevents accidentally erasing data.
Beginners often assume templates behave like 'reset to default' buttons, but they are more like 'fill in the blanks' tools. The word 'apply' sounds aggressive, which leads to this misunderstanding.
Mistake
A Global Template can be used for any record type in the entire instance, including custom tables.
Correct
A Global Template is restricted to the specific table it was created for. It does not magically apply to all tables. The term 'Global' refers to the scope of its availability within the application, not across all tables.
The word 'Global' misleads beginners into thinking it means 'universal'. In ServiceNow, 'Global' often means 'available across the application module' but not across different table types.
Mistake
I can import data directly into a ServiceNow table without using an Import Set or Transform Map by just uploading a file.
Correct
ServiceNow does not allow direct data insertion into a table from a file upload for security and data integrity reasons. Data must always pass through an Import Set (staging table) and a Transform Map (which maps and transforms the data).
People familiar with simple spreadsheet tools expect a direct import button. The extra steps seem unnecessary until you understand that the staging and mapping process protects the database from corruption and allows for data cleansing.
Mistake
If I delete a Data Source, the Import Set table created from it is also automatically deleted to save space.
Correct
Deleting a Data Source only removes the source definition. The Import Set table and its data remain in the database permanently (unless manually cleaned up). This is a common maintenance task that must be managed separately.
Beginners expect a cascade delete behaviour like in a relational database. ServiceNow's design intentionally preserves the staging data for auditing and debugging purposes, which leads to this misconception.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
A Data Source is the configuration that defines where your external data comes from (like a file or a database). An Import Set is the temporary table that ServiceNow creates to store that raw data before it is transformed and loaded into the target table.
Yes. Open any existing record, look for the 'Apply Template' option (usually found in the context menu or the form header), select your template, and it will fill in only the fields defined in the template.
You can create unlimited templates, but you can apply only one template at a time to a record. If you apply a second template, it will overwrite any fields that the second template also defines.
Deleting a Data Source removes the source definition, but it does not delete the Import Set table or its data. You must manually delete the Import Set table if you want to remove that staging data.
No. For standard imports, you can use the graphical field mapping interface in the Transform Map. You only need to write scripts for complex data transformations, such as converting date formats or combining fields.
Yes. After you create your Data Source and Transform Map, you can configure a 'Scheduled Import' under System Import Sets > Scheduled Imports. You set the frequency (e.g., daily at 2 AM) and ServiceNow will automatically run the import.
You've finished Templates and Data Management. Continue through the SNOW-CSA study guide to build a complete picture of the exam.
Done with this chapter?