Further to my previous piece about Sage imports, I thought I would share the templates mentioned.
I’ll reproduce the relevant parts of the guide below for your convenience.
The source CSV File
Templates will not be be a cure for all ills. I wish they were! You will undoubtedly have to massage client data into the correct format for a smooth import.
I find it useful to have the source CSVand the template open in windows. I’m lucky that I use a two-monitor setup. It really helps copy data back and forth. i would make sure the source CSV’s columns match the template column layout exactly. It’ll make things go easier in the long run.
- Do not rename, remove, or reorder the column headings within the template.
- Ensure dates, numbers, and codes follow Sage’s expected format.
- Remove any blank rows or additional worksheets before saving.
- Save the file as a CSV (Comma delimited) format.
Paste the refined data into the relevant template, such as Audit Trail Transactions.
Import the CSV File
- BACKUP YOUR SAGE DATA BEFORE ATTEMPTING ANY IMPORT!!! This is the single most important advice I can give.
- Navigate to File > Import (or the relevant import option for the data type).
- Select the appropriate import type (e.g. Customers, Suppliers, Products).
- Browse to your prepared CSV file.
- Review the field mappings (these should align automatically if the template was used).
- Run the import.
Review the Import Results
After the import completes, Sage will confirm whether it was successful or highlight any errors. If errors occur, Sage will usually indicate the row and reason (such as invalid data or missing mandatory fields). Correct the CSV file and re-import if needed.
Best Practice Tips
- Always back up your data before running an import – I know I’ve always shouted this from the rooftops but I cannot stress this enough. Go do it now!
- Keeping an untouched copy of the original template for future imports is a very smart move indeed.
- If importing transactions, ensure related records (such as customers or suppliers) already exist in Sage. Your import will fail if you try to import using
For complex imports or troubleshooting persistent errors, Sage documentation and support resources provide detailed, data-type-specific guidance.
Leave a Reply