Migrate from monday.com
One board at a time, and you do the mapping.
Spodus has no monday.com preset, so this is a plain column mapping: export the board to Excel, upload it, and point each column at a field yourself. Spodus reads .xlsx directly, so there is no CSV conversion step.
What this move actually is.
Four facts that decide most of the work, before any column is mapped.
- 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. Growth carries unlimited custom objects.
- 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.
Column by column.
What each monday.com column becomes, and what the importer deliberately leaves alone.
| monday.com column | Lands in | Notes |
|---|---|---|
| A typical work board, into Tasks | ||
| Name / Item | Title | The primary field, and what duplicates are checked on |
| Status | Status | Matched case-insensitively against your Spodus options. Anything else is kept as typed and counted |
| Priority | Priority | Same rule. Low, Medium, High and Urgent are the options that exist |
| Person / People | Assignee | Split on commas, then matched against your Spodus roster by name |
| Date | Due date | Read as a calendar day |
| Timeline | One cell holding two dates. Spodus keeps Start date and Due date apart, so split the column in the sheet first | |
| Board name | Project | Only if you add it as a column; a monday export does not carry one |
| Numbers, text, long text | A field you create first | Nothing maps into a field that does not exist yet |
Because there is no preset, this table is a suggestion rather than something the wizard does for you. Two mechanical rules are worth knowing before you upload. The first row of the sheet is read as the column headers, so if your export opens with the board name or a blank row, delete those rows first. And nothing in Spodus recomputes a formula: whatever a formula or mirror column wrote into the export arrives as a plain value with nothing behind it.
What does not come across.
A spreadsheet holds text. Everything below is either not in the export or has no field here to land in.
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.
How to do it.
In this order. Steps two and three are the ones people skip and then repeat.
Pick one board and finish it
Do 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.
Decide what the board is
If 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. Custom objects are unlimited on every plan, so this is a decision about how you want the data shaped rather than a quota to spend.
Line up the option lists before you export
Status 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.
Export the board and tidy the sheet
Export 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.
Upload and map every column by hand
Open 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.
Read the preview before you commit
It 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.
How long it realistically takes.
Measured in the phases the work actually falls into, including the ones that are not importing.
- 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.
True of any import into Spodus.
The same four rules apply whichever tool you are leaving.
- It is a file, not a connection
- Spodus reads .csv and .xlsx. Not .xls, which no spreadsheet parser here can open, and not JSON. There is no public API and 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.
Do not migrate off monday.com if:
- 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. There is no monday.com preset and no service that will map the columns for you. If mapping by hand for fifteen minutes a board is unacceptable, this is the wrong move.
There is no migration service and no engineer here who will do this for you. It is your export, your mapping and your afternoon.
Questions, answered.
Is there a monday.com preset?
Do I need to convert the Excel file to CSV first?
What happens to a status value Spodus has never seen?
Can a board become something other than tasks?
Coming from something else?
The same page, for the other tools people leave behind.
