Bring your work over
Nothing is written until you import.
Nobody enjoys this part. A backlog is years of small decisions, and moving it usually means either losing half of it or spending a fortnight in a spreadsheet. So the import in WeMachines is built around one promise: it copies, it does not interpret.
There is no AI in the import
This is deliberate and it is the whole design. Each format has a fixed reader, so every title, description and value is written exactly as the source wrote it. The same file always imports the same way. It costs no credits. Nothing is summarised, tidied, rephrased or “improved” on the way in - which matters, because a ticket whose wording quietly changed during a migration is worse than one that never came across at all.
It also means you do not have to tell it where you came from. Every file is recognised from its own contents.
What it reads
- Linear, Jira, Asana, ClickUp and GitHub issue exports.
- A Trello board’s JSON - lists become statuses in board order, and a card’s checklists come across under its description with their ticks intact.
- monday.com and any other Excel workbook (.xlsx - no re-saving as CSV first).
- Any CSV, or a list of JSON records.
- A Notion “Markdown & CSV” export, nested or not: pages keep their folder tree, their links to each other and their images, and a database comes in as tasks or as pages, whichever fits.
- Folders of Markdown or HTML pages.
- Pasted text. A spreadsheet’s rows, a checklist (one task per item, headings become topics), or notes as one page. Cmd/Ctrl+V anywhere on the page.
PDF and .docx cannot be read - there is no honest way to turn a page layout back into fields. Export CSV, Markdown or HTML from whatever produced them instead.
One review screen, and all of it is yours to change
Nothing is written until you have seen the whole plan. On that screen you set what each spreadsheet column becomes - title, description, status, priority, labels, topic, assignee, created date, “marks it done”, kept in a table under the description, or left out entirely. You choose which of your statuses each source status joins (it matches by name, so “In Progress” finds “In progress”) or the new one it creates. You map people: matched by email, or by a name only one member has. Anyone the import cannot place lands unassigned with the original name kept under the description, and - worth saying plainly - nobody is invited or emailed by an import.
You also see every task and page with its description rendered exactly as it will be stored, and a “Left behind” list naming everything that will not come across and why. That list is the honest part of the screen. Read it before you press the button.
Statuses
1 new column goes on the board beside the ones of the same kind. The rest join the columns they match.
People
2 of 3 matched to a member here. Nobody is invited or emailed; a task whose person isn't here lands unassigned, with their name kept under its description.
Priya 
Tomas Left behind
Everything that does not come across, and why.
Fields a task has no place for - a due date, an estimate, the source’s own id like ENG-12 - are kept in a small table under the description rather than dropped. Original created dates are kept too, so your backlog does not all appear to have been written this morning.
Two things that do not come across
Comments. A comment is signed by the person who wrote it, and we will not forge that signature by attributing an old thread to a member here - or to nobody. If a discussion matters, paste it into the task’s description, where it reads as a quotation rather than as a teammate speaking.
Finished work, if you would rather. You can leave completed tasks out of the import. If you bring them, note they clear 14 days after they land, like any other done task here.
Do it in one go, with the team watching
The usual failure mode is a trickle: someone imports a slice, someone else keeps working in the old tool, and for a month the truth is in two places. Pick an hour, bring the whole thing across, and tell everyone the old board is read-only from now on. If a save fails part way, the import removes what it wrote, so a retry starts clean rather than doubling anything.
Open it from the workspace menu - click your team’s name at the bottom of the sidebar - as Import, or from “Import your data” at the foot of Home.
And the way back out
Worth knowing on the day you arrive rather than the day you leave: Settings → Danger Zone downloads the whole workspace as one .zip - every record, as JSON, with the files. We would rather you never use it. It exists because a workspace you cannot leave is a workspace you were never really given.