Sage X3 Import Template Worksheet
Sage X3 loads data through import templates that map a file layout onto an object such as items, customers or orders. This worksheet gives migration teams one place to list each object, template and file, and to see how many records were extracted, loaded and rejected.
| X3 object | Import template name | Source file | Records extracted | Records loaded | Records rejected | Reject rate | Status | Owner | Target date | |
|---|---|---|---|---|---|---|---|---|---|---|
24 | 0.5% | |||||||||
5 | 0.4% | |||||||||
0 | 0% | |||||||||
210 | 10% | |||||||||
380 | 100% |
Template names are examples from a naming convention. Sage X3 import templates are defined in the application and the object codes shown are common ones, so confirm names and folders in your own environment. Reject rate counts records not loaded, including those not yet attempted.
Profile my migration extracts
Optional: we can run a data quality review on sample extracts before your first load.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Add one row per object and source file. Enter the number of records extracted from the legacy system and update the loaded count after every test load. The worksheet calculates rejects and a reject rate for each row and for the whole migration. Use the status column to show where each object stands, and export to Excel to share with the steering group or with the data owners who must fix rejected records.
Load order and dependencies
Master data usually has to load before transactions. Item and business partner records come before bills of material, orders and open balances, and reference tables such as units, categories and tax codes come before everything else. A bill of material import fails if its components do not exist. Track dependencies by sequencing the target dates in this sheet so no object is scheduled before the data it depends on.
- Reference and setup tables first
- Items, customers and suppliers next
- Bills of material and routings after items
- Open orders and balances last, after reconciliation rules are agreed
Reading the reject rate
A small reject rate in a test load is normal and shows validation working. A high rate on one object points to a mapping or cleansing problem, such as missing mandatory fields, invalid codes or duplicate keys. Review the import log, fix the source data rather than loosening validation, and reload. Aim for zero unexplained rejects before the production load, and keep the final counts as reconciliation evidence.
Frequently Asked Questions
What is an import template in Sage X3?
It is a definition that maps columns in a file to fields of an X3 object and controls how records are validated and created. Templates can be run interactively or in batch, so a migration team can reuse them for each test load.
How many test loads should I plan?
Plan at least two or three full dress rehearsals before the production load. The first finds mapping errors, the second proves the fixes, and the last proves timing and reconciliation. Complex manufacturing data often needs more.
Why were my records rejected?
Common causes are missing mandatory fields, codes that do not exist in reference tables, duplicate keys, wrong date or number formats, and violating dependency order. The import log gives the line and message, which you should copy into your tracker.
Should rejects be fixed in X3 or in the source file?
Fix them in the source or in the transformation step so the process is repeatable. Manual fixes in the target are lost on the next reload and make reconciliation harder.
If your Sage X3 migration includes years of legacy history, we can help profile and clean the extracts before the first test load.
Related Tools
Sage 100 to Cloud Migration Assessment
A 10-question readiness score for companies on Sage 100 deciding when and how to move to a cloud ERP, with recommendations by result band.
Costing & FinanceSage Intacct Dimension Design Worksheet
An editable worksheet for designing Intacct dimensions: which standard and custom dimensions to use, value counts, requirements and examples.
Costing & FinanceSage 300 Period End Checklist
A module-by-module month end close checklist for Sage 300: subledgers, inventory, costing, bank and general ledger, with critical steps flagged.
More Other ERPs tools
See all- Infor VISUAL Work Order Status and Structure Reference
- Infor VISUAL Manufacturing Scheduling Checklist
- Infor XA (MAPICS) Period End Close Checklist
- Infor VISUAL Database Table Reference
- Infor XA (MAPICS) Application Module Reference
- IBM i Commands for Infor XA Administrators Reference
- Acumatica Generic Inquiry Design Template
- Acumatica Manufacturing Edition Setup Checklist
- Acumatica Implementation Budget Estimator