Fixing import problems

When a Syncek import finishes, its row on Imports shows how many rows were created, updated, skipped and failed, but not which rows. So fix the file before the run: fill in required fields, make numbers and dates readable, convert dates written day first, and delete spreadsheet rows that look empty but still count as rows.

Rows that fail

A failed row is not imported, and the rest of the file still is. A row fails when:

• a required field is empty, such as the name of an account
• a number, amount, date, time or yes-or-no value cannot be read
• in an update run, its match value belongs to more than one record

Review values marks dates it cannot read and options it cannot match as Needs review before anything is written. Fix them there or in the spreadsheet.

Dates written day first

Syncek reads a date such as 03/04/2026 month first whenever it can, as March 4. Only a date that cannot be month first, such as 13/04/2026, is read day first. A column of day-first dates imports without a single error, with day and month swapped on every date up to the 12th.

To read a column day first, open it in Map columns, add the Convert date format transform and set it to EU (dd/mm). Review values then shows each date as it will be stored.

• Dates with dots, such as 03.04.2026, cannot be read and fail. Add Find and replace first, replacing . with /, then Convert date format.
• Month names are read in English only.
• The swap shows up in .csv files and in Excel cells with a custom day-first format. An ordinary Excel date cell arrives in the right order.

Rows that look empty

A spreadsheet where formulas were copied down keeps those cells even when they show nothing. Syncek reads them as rows: a file with 3 customers can report 499 Rows found. In most objects those rows fail for a missing name. In Contacts, where the name has two parts, they can stop real contacts from being imported, as the next section explains. Delete them in the spreadsheet and upload again.

Many rows skipped at once

Syncek writes a file in groups of 500 rows. When one group cannot be written, every row in it is skipped, not only the row at fault. It happens with:

• a field marked Unique, when a value repeats inside the file or already belongs to another record
• a contact row with both parts of the name blank, which is what empty spreadsheet rows turn into
• a required field that is not mapped, or a required cell that holds only spaces

Remove the repeats or the blank rows, or map the missing field, then import the whole file again with Add new & update existing, matching by a field that is unique. Rows that made it in the first time are updated instead of created twice.

A run that will not start

A workspace runs up to three imports at a time. Wait for one to finish, then start yours.