Monday tracks the board. Orbit finishes the job.

Import from Monday is being built. Export a board, map the statuses once, and see exactly what will come across before anything is saved. Tell us about your boards and you’ll be first to try it.

Tell us about your boards See the steps

Preview before saving Statuses mapped once One-click undo

The difference

A board is not a studio.

Monday is a shape you bend into a studio. Orbit starts as one: a project has a client, a delivery has a version, a version has notes, and the invoice knows which project it belongs to.

Review inside the projectNo "paste the Frame.io link in the update" step. Versions and notes live on the asset.
Money is nativeInvoices, payments and expenses sit next to the work that earned them.
Clients don't need a licenceSend one link. Clients review, comment and approve without a seat or a login.

Board mapping

example

Monday	Orbit	Behaviour
Board	Project	Clients, dates and status come with it.
Group	Status column	Groups collapse into one of five statuses.
Item	Task	Assignees and due dates preserved.
Subitem	Subtask	Nesting kept one level deep, as in Monday.
Update	Comment	Author and timestamp kept; files re-attached.
Column: Files	Assets	Uploaded to storage, not linked.
Automation	Not imported	Orbit’s post-production rules cover the common ones — see below.

How it will work Coming

Four steps, one afternoon.

Do one board first. If the mapping is wrong you'll know before you touch the other nine.

Export from Monday

Board menu → Export → CSV. Tick "include subitems" and "include updates". One file per board.

Drop it in Orbit

Upload the export, or connect your Monday account. Orbit reads the columns and shows you the mapping before importing anything.

Map, then dry-run

Choose the client for each board, map groups to statuses, and run the dry-run. Nothing is written until you confirm.

Recreate the rules

Orbit’s built-in post-production rules cover most Monday automations. The report lists what it couldn't translate.

IMPORT REPORT — SPRING_CAMPAIGN.CSV example

Rows read184

Tasks171

Assets66

Warnings2

Two rows reference a person who isn't a member of this studio. Orbit will import them as unassigned and list the names.

What moves

Honest about the edges.

Comes across

Projects, clients and statuses
Tasks, subtasks, assignees, due dates
Updates as comments, files as assets
Invoice records and their numbers

Stays behind

Live automation recipes (rebuilt, not exported)
Monday Docs and WorkForms
Time-tracking entries unless exported as a column
Board permissions (rebuilt as roles)

Keep the Monday account read-only for one billing cycle. When nothing has been missed, cancel it.

Post-production rules Coming

The rules that matter, already connected.

When a version is uploaded, set the project to “In review”

Rule: asset created on a project → set project status to In review. This replaces the "notify client" automation and removes the manual step of remembering to move the item.

When a client approves, create the phase invoice

Rule: delivery approved → draft an invoice from the project's billing template, line items pre-filled from the quote. You review and send; Orbit doesn't invoice without a human.

When an invoice is 7 days overdue, flag the project

Rule: invoice overdue by 7 days → add an "On hold — unpaid" flag and notify the owner. Outstanding is a number, not a mood.

When a note is resolved, close the matching shot task

Rule: review note resolved → close the task linked to that timecode. Nothing escapes into the next cut.

Want it first? Tell us about your boards.

Send a line about how your studio uses Monday. Studios that write in get the import first.

Tell us about your boards Ask a question