The annotated import templates, linked below, are some of the more common imports used during implementation and can also be used for ongoing maintenance of your website. We will continue to add templates to the library over time.
Using Templates with Excel
- Select and open the template you wish to use.
- Go to File>Download and select the Excel (.xslx) option.
- Save the file to your desktop.
Using Template with Google Sheets
- Select and open the template you wish to use.
- Go to File>Make a Copy
- Save the file to your desktop.
For additional detail on working with spreadsheet imports and exports, please refer to this article.
Best Practices for Spreadsheet Imports
-
🔁 ERP Sync Guidelines
-
Never manually update ERP-synced data in CIMcloud.
-
Always make changes in the ERP system.
-
CIMcloud will revert to the ERP value on the next sync if it detects a mismatch.
- Standard Data Synced Between CIMcloud and Acumatica
-
✅ Before You Upload
-
Test with One Record First
-
Upload a single record to verify the expected result.
-
Avoid mass issues—one mistake is easier to fix than 1000!
-
-
Name and Save Your File Clearly
-
Use a descriptive name (e.g.,
2025_Product_Descriptions_Update.xlsx). -
Store it safely—you may need it again for auditing or re-importing.
-
⚠️ Spreadsheet Formatting Tips
-
Only include fields you intend to update
-
Example: If you just intend to update product descriptions, only include these fields:
-
ID (SKU) -
Description (ds)
-
-
Do not include
Name (nm)if not updating it.
-
-
Avoid blank fields in included columns
-
A blank field = data deletion (it removes the current value).
-
- Ensure that the data you are importing is encoded in UTF-8. (This character encoding is required for proper display on CIMcloud sites.)
- Here are some steps you can follow:
- Check Source Encoding: Ensure that the source data is in UTF-8 encoding. If it’s not, you may need to convert it.
- Convert to UTF-8: You can use tools like Google Sheets or Excel to convert your data to UTF-8. Here are some guides:
- Here are some steps you can follow:
🔗 Import Dependencies
-
Do not map to records created in the same import
-
Example: When importing parent-child product relationships:
-
First import parent products
-
Then import child products, mapping to the now-existing parent.
-
-
🆔 ID Conflicts
-
Check for duplicate IDs
-
Creating new records? Duplicates can cause multiple records with the same ID.
-
Updating existing records? The last row wins—overwriting previous updates.
-
🗑️ Deletion Caution
-
Be very careful with delete options
-
The delete action will remove entire records, not just specified fields.
-
You could accidentally delete ERP-synced records if included in the spreadsheet.
-
-