One board at a time.

The files

One export per board. monday exports a board to Excel, and Spodus reads .xlsx without you converting anything first. If you would rather work in CSV, that is read too.

No preset

Spodus ships presets for seven vendors and monday.com is not one of them. Nothing recognises the file, nothing pre-fills the mapping, and no status value is translated. Every column is pointed at a field by hand on the Map step.

The target

A work board usually belongs in Tasks. A board that is a different kind of thing entirely is a custom object you create first. Free has one custom object, Starter 5 and Growth 25.

The direction

One way, once. There is no sync and no way to run both systems against the same data, so a board moves on the day you move it.

• Board structure

  Groups, column colours, column widths, the board view and any dashboard built on it. What comes across is rows and values. How the board looked is rebuilt in Spodus using its own table, board, calendar and timeline views.

• Updates and the activity log

  The conversation under each item, mentions, and every entry in the board's activity log. These are the part of monday people miss most, and no export carries them into another product.

• Files on items

  A spreadsheet holds text. Attachments stay in monday and have to be downloaded and re-uploaded to the record here, or left where they are.

• Subitems

  Nothing in the import fills a parent relationship, so every row arrives as its own task. If subitems carry real work, decide whether they become tasks in their own right or get folded into the parent before you export.

• Automations and integrations

  monday's automation recipes and its connected apps have no equivalent definition to import. Spodus has its own automations, and rebuilding the two or three you actually depend on is a short job.

• Connected boards and mirrors

  A connect-boards column is a relationship monday holds internally. In an export it is text, and on the way in it is text, unless the target is a Spodus relation field and the value happens to be the related record's name.

1. 1Pick one board and finish itDo not export everything. Take the board you would notice most if it disappeared, move it end to end, and look at the result for a day. Everything you learn about your own data on that board applies to the next twenty, and doing it in that order costs one board's worth of rework instead of twenty.
2. 2Decide what the board isIf it is work with owners and dates, it is Tasks. If it is a list of a thing Spodus does not already model, it is a custom object you create first, with the fields spelled the way you want them. Starter carries 5 custom objects and Growth 25, so this is mostly a decision about how you want the data shaped rather than a quota to spend.
3. 3Line up the option lists before you exportStatus and Priority in Spodus are select fields with their own options. A monday status that is not already an option arrives as plain text and is counted under the cells the importer could not read. Either rename the Spodus options to match your board, or fix the values in the sheet. Doing it afterwards means editing records one at a time.
4. 4Export the board and tidy the sheetExport to Excel from the board menu. Then open the file: delete anything above the header row, split a timeline column into two, and delete the columns you have already decided not to bring. Ten minutes here removes an hour of squinting at the Map step.
5. 5Upload and map every column by handOpen Tasks, press Import, upload the file. With no preset, nothing is pre-filled: you point each column at a field, and anything you leave alone sits under Ignored columns where you can see exactly what you are dropping.
6. 6Read the preview before you commitIt counts duplicate rows, unreadable cells and links pointing at nothing, all before the write. Skip duplicates is on by default and automations are off by default, which is what you want for an import.

Exporting one board

2 minutes. No queue, no email.

Tidying the sheet

10 to 20 minutes. Header row, timeline split, dropped columns.

Mapping by hand

15 to 30 minutes. The cost of there being no monday preset.

Creating fields or an object first

15 to 45 minutes. Once per board shape, not once per board.

Fixing what the preview flags

20 to 60 minutes. Almost always status values that do not exist here yet.

Updates, files and automations

Not included. None of the three comes across.

The first board takes most of a morning, because you are deciding things as much as doing them. Boards two through ten take about half an hour each once the fields and the option lists are settled. A workspace with sixty boards is a week, and it is worth using that week to not move the twenty boards nobody has opened since spring.

It is a file, not a connection

Spodus reads .csv and .xlsx. Not .xls, which no spreadsheet parser here can open, and not JSON. Nothing keeps two systems in step, so what you get is a copy of your data as it stood the moment you exported it.

One file per object

You import into an object, not into the workspace. Open Contacts and import contacts; open Deals and import deals. A vendor that keeps people, companies and deals in three exports needs three passes.

Links are stored as names

A deal points at an account by name, and the link resolves the moment a record with that name exists. So importing accounts before deals is a convenience rather than a rule, and a link that lands unresolved starts working when the missing record arrives.

Nothing is written until you press Import

The preview counts duplicates against the records already in your workspace, counts the cells it could not read, and counts the rows pointing at something that does not exist yet. All three are on screen before the write.

• Your boards live on formulas, mirrors and connected boards. Those are computed relationships, and an export flattens them to text. Spodus recomputes nothing, so what you get is a snapshot of yesterday's numbers.
• You depend on dependencies, workload or capacity views. Spodus has no resource or capacity planning of any kind, and nothing on a Spodus timeline blocks anything else.
• The updates thread is where the work happens. Item conversations do not export into another product, and a board whose value is its comments will arrive stripped of most of its value.
• You want a preset to do it and you are on Free. There is no monday.com preset, so on Free you map each board by hand. On a paid plan, send us the export and we move it in for you, free.

On a paid plan, we do the move for you, free: send us your export. On Free, it is your export, your mapping and your afternoon.

• Project management

  Migrate from ClickUp

  Preset mapping, then your decisions.

• Sales CRM

  Migrate from Pipedrive

  Preset mapping, then your decisions.

• Work management

  Migrate from Asana

  Preset mapping, then your decisions.