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

Undo a record move or a bulk move

Return a record to its previous unit from its Logs tab. Your edits after the move stay, and the fields that were dropped come back. You can undo a whole bulk move right after it finishes.

3 min

The Logs tab, where you undo a single record’s move, may not be turned on for your account yet. Contact support to turn it on.

Before you start · for owners and managers
The edit permission in the current unit, and the add permission in the unit it returns to
  • You need: The edit permission in the current unit, and the add permission in the unit it returns to

Steps

1
Open the record in its current unit and go to the Logs tab.
A banner shows “Moved here from” and the previous unit, with Undo move.
2
Press Undo move, then confirm with Undo move.
The record goes back to its previous unit, and its change history and assignee go back too.
3
To undo a bulk move, press Undo in the message that shows when the move finishes, or next to the job in Bulk jobs.
“Undoing the move…” shows, then how many records were moved back.

How it works

Undo reverses only the last move. You can repeat it: a record moved from A to B, then to C, goes back to B, then to A.

Edits made after the move stay. Fields the move dropped are restored from the saved copy.

The assignee is removed if they can no longer see the original unit.

Undoing a bulk move

The Undo button shows only to the person who ran the move, in the same session. After that, undo the records one by one from their Logs tab. Records that were moved again since the bulk move are skipped, with the reason given.

If something goes wrong

What you see
Why
What to do
“There is no move left to undo for this record.”
The record wasn’t moved, or you’ve undone all its moves.
There’s nothing to undo.
“The current values aren’t valid for the unit it’s returning to”
A value edited after the move breaks the original unit’s rules.
Correct the value, then undo.
“Another user is moving this record right now. Try again in a moment.”
A teammate moved it at the same moment.
Reload and try again.
“Nothing of this move is left to undo in this unit.”
All its records were returned or moved again.
Review the records one by one.

A real example

Shield Security Co.
The situation

60 quotes were moved to contracts by mistake.

What they did
  1. The manager pressed Undo in the message that showed when the move finished.
The result

The 60 quotes went back to their unit with all their values.

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

Good to know

There’s no time limit for undoing a record’s move from its Logs tab.
An undo can’t itself be undone; move the record again instead.
You can’t return a record to an original unit that’s deactivated.
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.