All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

The Map Fields step: column options and value checks

Corteksa matches the columns automatically by name. For each column: choose a field, skip it, or set a default value. You can import the assignee, created dates, notes and relations.

6 min

Automatic matching

It happens in this order: the system columns by their English names, then notes, then the field’s name or label, then the relation’s name, then a loose match that ignores separators, letter case and differences in hamza. If two fields have similar names, the column is left unmatched so you choose yourself.

Options for each column

Option
What it does
Field
The value is written into the field
Skip column
The column isn’t imported
Default
Used when the cell is empty
Relation
The record is linked, by name, to a record in the related unit

System columns

Column
How it’s read
Assigned To
By the active user’s name or email, ignoring letter case. An empty cell = no assignee
Created At and Updated At
As 2026-03-01, or 01.03.2026 with the time, or an Excel date number. Empty = now
Note 1 to Note 7
Turned into comments on the record, written by the assignee or by you

How values are checked

Type
Rule
Select, status, priority, tags
Match the option’s name, ignoring letter case. Options aren’t created automatically. Separate several values with a comma or semicolon
Mobile
Must be a valid number, and is saved as digits only
Date
2026-03-01, an Excel date number, or a format such as 03/01/2026. Impossible dates are refused
Text
Not longer than the field’s maximum
Relation
Matches the linked record’s name, ignoring letter case
Computed
Calculation, serial number, lookup and rollup are never imported

If something goes wrong

What you see
Why
What to do
“The name doesn’t match any active user”
The assignee’s name is written differently, or the user is deactivated.
Write the email instead of the name, or activate the user.
“Invalid value, must be one of…”
A value that isn’t among the field’s options.
Add the option in the field settings, or correct the file.
“The linked record doesn’t exist”
There’s no record with that name in the related unit.
Import the related unit first.
“Several columns are matched to the same system column”
For example, you mapped two columns to the assignee.
Choose one column and skip the other.

A real example

Namaa Academy
The situation

A client file from an old system, with an “Assigned To” column holding the advisors’ names and a “Notes” column.

What they did
  1. “Assigned To” was matched to the assignee automatically.
  2. They renamed the notes column to “Note 1” before uploading.
The result

Every client came in with the right assignee, and their old note as a comment.

A made-up company, to show the idea. The numbers are rounded.

Good to know

Only one column per system column.
The preview shows only the first 20 rows.
Options that don’t exist make the row fail. Add them to the field first.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.