How does a migration actually go?
Export from the old tool
Every tool has an export button somewhere: a CSV of tasks, clients, or hours, or a document export for wikis. That file is all you need.
Auto-map and validate
The wizard reads your headers and maps columns to Scrambl fields on its own; you only adjust the ones it should not guess. Validation then checks the whole file before anything is written, flagging rows to fix or skip.
Review, with a route back out
Every import run is recorded in a history that shows exactly what it created. A wrong file has a recovery path, so nobody hand-deletes records on a Friday night.
What can come across?
The wizard imports the records the rest of the workspace runs on. Start with the list that hurts most; nothing has to move at once.
Clients
Your account list, with the fields you already track.
Contacts
People, with lifecycle stages ready to assign.
Deals
The open pipeline, valued and staged.
Projects
Active work, ready for tasks and templates.
Time entries
Hours that keep their project and person.
Documents
Wiki and doc exports become articles with categories and review dates.
What if the file was wrong?
That is the question every migration actually turns on, so the wizard is built around it. Validation runs before a single record is written. Every run lands in a history that shows what it created. And a bad run has a recovery path, not a cleanup weekend.
What happens if an import goes wrong?
Every import run is recorded in a history, and a bad run has a route back out. You can see what a run created and recover from a wrong file rather than hand-deleting records.
Which records can I import?
Clients, contacts, deals, projects, and time entries come in through the CSV wizard, and document exports from wiki tools become knowledge articles. The wizard ships on every plan.
Do I have to map every column by hand?
No. The wizard reads your CSV headers and maps them to Scrambl fields automatically, using the column names and the shape of the values. You review the mapping and adjust only what it should not guess.
Do we have to move everything at once?
No. Each capability works on its own, so most teams start with the list that hurts most and bring the rest over when they are ready.
Where do I get help mid-migration?
The in-app help center covers the wizard step by step, and the contact form reaches the people building the product.