Previewing and Running the Import

Once your mapping is confirmed (see Reviewing and Fixing Column Mappings), the wizard validates everything and shows you exactly what will happen — before a single record is written.

Step 3 — Validate & PreviewCopy Anchor Link

The validation step summarizes the outcome in four cards:

• Ready To Import — rows that passed validation and will be sent.
• Invalid Rows — rows that failed validation (missing required values, bad numbers/dates…). These are left out of the import; each one is listed further down with its row number in the original file and the exact reason.
• New Records — how many rows would create brand-new records, according to a server dry run. The dry run checks your rows against real data without writing anything; for large files it covers the first 200 rows, and the rest are validated during the import itself.
• Will Skip (Existing) / Will Update (Existing) — depending on the duplicate handling you chose, how many rows matched records that already exist.

Below the cards, a preview table shows the first 30 records exactly as they will import — after all transforms, with one column per mapped IoTOMS field. This is your last chance to spot a mis-mapped column: if something looks wrong, click Back to mapping.

If the dry run finds rows the server would reject (for example a reference to an ID that doesn't exist), they're listed in red so you can fix them before running anything.

When you're happy, click Import N records.

Step 4 — ImportCopy Anchor Link

The import runs in batches with a live progress bar. Keep the tab open until it finishes — closing it stops the remaining rows (rows already processed stay imported).

When it completes you get a summary: Created, Skipped/Updated (existing records, per your duplicate setting), and Failed.

If some rows failCopy Anchor Link

1. The Failed Rows panel lists each failure with its original row number and the reason — both rows that failed validation locally and rows the server rejected.
2. Click Download error report (CSV) — it contains only the failed rows, in your original column layout, with the error reason attached.
3. Fix the values in that file and upload just that file again through the same wizard. Re-importing is safe: records that already exist are skipped (or updated, if that's the mode you chose), so nothing gets duplicated.

Click Import another file to run the next migration, or head to the relevant module (Items, Customers, Purchases → Vendors) to see the imported records.