What happens to lookups and relationships during import?

A lookup field points to another record. When importing, you only have text, and the system must guess which record the text refers to.

Matching by name is fragile

If the file says “Bergen Bygg” and the system says “Bergen Bygg AS,” there will be no match. If two companies have the same name, the match will be ambiguous and the row will fail. Both are very common in Norwegian customer databases.

Alternative keys solve the problem

If you define the organization number as an alternate key for the company, the import can match on that instead of the name. It is unique, and it eliminates the vast majority of this problem.

Failed rows are placed in a separate file

The import produces a file containing the rows that failed, along with the reason. Review it—it usually points to one systematic problem rather than many individual errors.