Import Set Tables hold raw data from external sources before it gets transformed and loaded into your production tables. This guide walks you through creating the staging table that serves as the landing zone for your import process.
What import staging solves
Before Import Sets, loading external data into ServiceNow meant writing custom scripts to parse files, validate data, and handle transformation errors inline. When something broke, you lost data or corrupted records with no easy way to retry. Platform admins and developers who manage data integrations inherit these fragile processes where a single malformed CSV row can crash an entire import job.
How import staging works
An Import Set Table is a staging area with a u_ prefix that holds raw imported data exactly as it arrives. ServiceNow loads your CSV or web service response into this table first, then uses Transform Maps to move cleaned data into production tables. Start with a basic staging table that matches your source data structure — ServiceNow auto-creates columns when it encounters new fields. Add validation and error handling in the transformation layer, not the staging table.
Production-quality improvements
Once your basic import works, add coalesce fields to prevent duplicate imports, create custom columns for data validation flags, and implement cleanup jobs to purge old staging records. Well-designed staging tables include audit fields to track import batches and error states. Consider adding business logic to pre-validate data in the staging table before transformation runs.
Before you start
- •import_admin role or admin role
- •Sample data file or knowledge of source data structure
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Step by step
Navigate to Create Table
Go to System Import Sets > Administration > Import Set Tables and click New. This creates the staging table where your raw data will land before transformation.
Set table name and label
Enter a descriptive Name — ServiceNow automatically adds the u_ prefix to create the actual table name. Set the Label to something users will recognize in lists. Keep both concise but specific enough to distinguish from other import tables.
Configure table properties
Check 'Create module' if you want this table to appear in the application navigator for manual review. Leave 'Create access controls' checked — you'll want to control who can view staging data. The system handles the rest of the table creation automatically.
Add staging columns
Click Submit to create the base table, then return to add columns that match your source data. Click New in the Columns tab for each field you expect. Use String for most data types — you'll handle conversion during transformation. Don't worry about getting every column upfront; ServiceNow creates missing columns automatically during import.
Add a 'batch_id' column (String, 40 characters) to track related import records together.
Test table creation
Navigate to System Import Sets > Import Set Tables and find your new table in the list. Click on it to verify the structure looks correct. The table name should show with the u_ prefix and include the standard import set columns (sys_id, sys_created_on, etc.) plus any custom columns you added.
Best practices
Always add a batch_id or import_date column to group related records from the same import run.
Use String data type for staging columns even when the target field is Date or Number — handle conversion in the Transform Map where you can catch and log errors.
Don't add business logic or complex field validations to staging tables — keep them as simple data containers.
Create cleanup jobs to purge staging records older than 30-90 days to prevent table bloat.
Include the data source name in your table name (u_hr_employees, u_asset_feed) to distinguish multiple imports for the same target table.
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue