This page is generated from the product itself — the same source the built-in assistant answers from — so it cannot disagree with either.
Migration
Read the message first — it is written to say what is wrong and, where there is one, the fix. If it says to set something in settings, that means the app’s own settings screen or Company settings. If it quotes a reference, keep it for support.
That import is no longer here.
migration.error.batchNotFound
This file has no column called “{column}”, which {field} is pointed at. Choose one of the file’s own columns.
migration.error.columnNotInFile
“{currency}” is not a three-letter currency code.
migration.error.currencyInvalid
This mapping has a money column, so tell us which currency the file is in. We will not assume your own — a catalogue priced in one currency and read as another is wrong on every row.
migration.error.currencyRequired
Tell us how the dates in this file are written. 03/04/2026 is 3 April or 4 March depending on who exported it, and we will not guess — a guess is right most of the time and silently wrong for the rest.
migration.error.dateFormatRequired
Tell us which character separates the decimals in this file. 1.234 is one thousand two hundred and thirty-four in some countries and one point two three four in others.
migration.error.decimalSeparatorRequired
Import {requires} before {entity}. This file points at records that have to exist first, and importing it now would fail on every row.
migration.error.dependencyNotImported
Two columns are both called “{column}”, so a mapping onto that name would be ambiguous. Rename one of them.
migration.error.duplicateHeader
We cannot import {entity} yet. Everything above it in the list works today, and this one is coming.
migration.error.entityNotServed
{entity} needs a column for {field}, and none is chosen. Pick the column that holds it, or type a value to use for every row.
migration.error.fieldUnmapped
No file arrived. Choose a CSV or Excel file and try again.
migration.error.fileEmpty
That file has no header row, so there are no columns to map. The first row must name the columns.
migration.error.fileNoRows
That file is {size} bytes and the limit is {max}. Split it by entity — customers in one file, products in another — and import them in order.
migration.error.fileTooLarge
That file could not be opened. It may be damaged, or password-protected — try saving a fresh copy from your spreadsheet.
migration.error.fileUnreadable
“{name}” is not a CSV or an Excel workbook. Open it in any spreadsheet and save it as .xlsx or .csv.
migration.error.fileUnsupported
You already have a saved mapping called “{name}” for this. Pick another name, or open that one and change it.
migration.error.profileNameTaken
That saved mapping is no longer here.
migration.error.profileNotFound
This workbook has no sheet called “{sheet}”.
migration.error.sheetNotFound
The file behind this import has been removed from your files. Upload it again to run the import.
migration.error.sourceFileGone
Choose the column that identifies each row in your old system. Without it we cannot tell a re-import from a new one, and a second run would duplicate everything.
migration.error.sourceIdColumnRequired
That uploaded file is no longer here. Upload it again to carry on.
migration.error.sourceNotFound
“{domain}” is not a kind of migration this product does.
migration.error.unknownDomain
“{entity}” is not part of the {domain} migration.
migration.error.unknownEntity
Was this page helpful?
Thank you.
Your answer is kept on this device only. Nothing is sent anywhere — there is no service behind this button yet, and this page will say so until there is.