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

Move a record from one unit to another

Turn a “Lead” into a “Client” without losing its history. The record moves with its chats, comments, tasks and change history, and you can undo the move.

5 min
Open in Corteksa
Before you start · for owners and managers
The edit permission on the source unit, and the add permission on the target unit
  • You need: The edit permission on the source unit, and the add permission on the target unit

Steps

1
From the row menu, choose Move to Another Unit, or press Move on the record page.
The Select Target Unit step opens.
2
Choose the target unit and press Preview Move.
The Resolve Field Conflicts step shows the fields in sections.
3
Make your decisions in each section, then press Next. See Field mapping options when moving a record.
4
In Confirm Move, check the Move Summary and the assignee After Move. Type a Reason (optional) if you want; it’s saved with the move.
5
Tick Remember these choices for the two units to apply your choices automatically next time.
6
Tick I understand the changes and want to proceed with the move., then press Confirm Move.
The record disappears from the first unit and shows in the target, usually with the same link.

What moves with the record

Chats, email, comments and replies with their read positions, @@ mentions of it, tasks and child records, assignees, change history, ad touchpoints, automation runs, and the lead form that created it.

New chats from the same number follow the record to its new unit, and don’t create a new client.

What doesn’t move

Duplicate links are deleted. Relations stay only if the target has a matching relation. Relations between the source and target units are lost.

The assignee after the move

The assignee stays if they can see the target unit. Otherwise, the longest-standing of the other assignees who can see it becomes the primary assignee. Confirm Move shows the Current Assignee and who it will be After Move. To give the record to someone else, change its assignee after the move.

Automations and distribution

Moving doesn’t run A new record is added automations in the target, and doesn’t distribute the record again. Your teammates’ screens update straight away.

Preview warnings

Warning
What it means
Links may be lost
The record is linked to other records whose links may not move
Different field type
The value can’t be copied directly; choose what to put
The option doesn’t exist
The current value isn’t available in the target field; choose the closest option
The assignee will lose access
The assignee can’t see the target unit; another assignee who can see it takes over, or the record arrives without an assignee
The unit isn’t one of yours
The record will move, then disappear from your lists
Pending required fields
The target needs fields filled in before the move

If something goes wrong

What you see
Why
What to do
“Required fields must be filled in before moving”
A required field in the target is empty.
“The target unit’s rules aren’t met”
A value breaks a rule in the target; the message names it.
Correct the value it names.
“Another user is moving this record right now. Try again in a moment.”
A move is already running on the same record.
Wait and try again.
“You don’t have permission to add in the target unit”
Your role doesn’t allow adding there.
The record disappeared from my lists after the move
You can’t see the target unit.
This is expected; that unit’s teammates see it.

A real example

Namaa Academy
The situation

A lead enrolls in a course and needs to become a “Student”.

What they did
  1. The advisor moved the record to the “Students” unit.
  2. She copied “Course of interest” into the “Enrolled course” field.
  3. She ticked Remember these choices for the two units.
The result

The student moved with all their earlier WhatsApp chats, and the next move took two clicks.

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

Good to know

The name always moves.
Types that are directly compatible: the same type, text ↔ long text, date types with each other, and mobile ↔ WhatsApp.
If the record’s link is already used in the target, the record gets a new link, and old links redirect to it.
Did this guide solve it?
If not, we’ll ask what was missing.
Next, you might need
Field mapping when moving
Look it up · 5 min
Move several records
Step by step · 4 min
Undo a move
Step by step · 3 min
Open in Corteksa
Did this guide solve it?

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