Before you begin
Use Carryover only when the selected item and destination fit the supported release boundary. You must be a writable member or administrator with edit access to both boards. Guests and viewers receive a safe-stop message before item content is read.
- The source and destination are classic boards in the same monday account and workspace.
- The selected item is a parent item, not a subitem.
- The primary Name column is preserved, and every supported source text column has one unique, unambiguous destination match.
- You are prepared to inspect monday’s native source, destination, and Activity Log if the result is uncertain.
Why Carryover asks for three scopes
| Scope | Used for | Not used for |
|---|---|---|
boards:read | Board/group choices, exact schemas, the selected item, destination rereads, and a bounded source activity snapshot | User profiles, unrelated item content, update bodies, files, or documents |
boards:write | The one operator-confirmed item move | Background automation, bulk board edits, or cross-account moves |
updates:write | The native receipt after destination verification | Reading update conversations or replies |
The five-stage workflow
1. Choose the destination
Open the item menu, choose Apps → Carryover, then select the exact destination board and group. Carryover excludes the source board, inaccessible boards, cross-workspace candidates, and unknown board types.
2. Run the safety check
Carryover compares both schemas, reads the one selected item, enforces the parent-item boundary, and captures an available source activity window. Item content is not read until the destination schema is ready.
3. Review and confirm
The confirmation repeats the destination, explicit mappings, activity window and cap, omissions, unknown activity kinds, and the five-minute expiry. No checkbox or client state can bypass the server-side authorization checks.
4. Move and verify
Immediately before dispatch, Carryover rereads the source and obtains a fresh server decision. After monday responds, it rereads the destination and compares the item identity, group, Name, hierarchy, and every mapped text value.
5. Write the receipt
Only a verified destination can authorize the receipt. Carryover rereads the destination again before writing and never blindly retries a move or receipt mutation.
What the receipt says
The receipt is a native monday item update visible under the destination item’s existing permissions. It includes the source and destination, item, exact mappings, capture window and row cap, represented and omitted activity, unknown kinds, verification checks, privacy disclosure, and native Undo instructions.
When Carryover stops
A blocker is a product result, not an invitation to bypass the check. Fix the named issue or use monday’s native move outside Carryover.
- Unsupported, unknown, or ambiguous column semantics
- A non-empty source text value without one exact target
- More than ten source text columns, or any missing, duplicate, or ambiguous destination target
- Subitems, cross-account moves, non-classic boards, or missing edit access
- Schema or item drift after the safety check
- Expired confirmation, entitlement denial, disabled write switch, or an inconsistent provider response
Recovery and native Undo
Move indeterminate: Carryover cannot prove whether monday applied the request. This state is never safe for an automatic retry.
If Carryover says the move was not dispatched, run a fresh safety check after correcting the blocker. If it reports an indeterminate or verification-failed outcome, do not retry automatically. Inspect both boards and monday’s native Activity Log first.
- Refresh the source and destination boards.
- Locate the item by its exact name and ID where available.
- Inspect the destination values and updates for a Carryover receipt.
- Use monday’s Activity Log Undo where available and appropriate.
- Contact support with the stable reason code, UTC time, and app version—never credentials or a raw board export.