Log inTry for free

Bring your work with you.

Export what you have, import it into one workspace, and keep a route back out. Nobody re-types a client list.

Try for free

The import wizard ships on every plan.

What does it mean to migrate?

Migrating to Scrambl means taking the records your business already runs on, your clients, contacts, deals, projects, hours, and the documents that explain how you work, out of the tools that hold them today and into one workspace where they share the same records. It is an import, not a rebuild. You export a file, the wizard maps its columns to Scrambl fields, and connections like the project and the person an hour was logged against come across with it. You move one list at a time, and everything can export back out.

One list at a time

Start with the records that hurt most. The rest can follow when the team is ready.

Fields stay fields

A column in your export becomes a field in Scrambl, so the data is still filterable and reportable, not pasted into a note.

Reversible

Every run is recorded, a wrong file has a recovery path, and everything exports back out.

Coming from

Asana, Monday.com, Trello, ClickUp, HubSpot, Harvest, Notion, Confluence, Google Sheets, Excel. If it exports a CSV or a document, it moves.

What would we actually need to do?

Six steps. Three of them are yours, and none of them is re-typing.

  1. You do this

    Choose what moves first

    Pick the list that hurts most. Usually that is clients, then the deals and projects that belong to them, then hours. Nothing has to move at once, and each list imports on its own.

    You need

    A decision, not a file

  2. You do this

    Export from the old tool

    Every tool on the list above has an export somewhere: a CSV of clients, deals, projects, or hours, or a document export for a wiki. That file is all the wizard needs.

    You need

    A CSV, or a document export

  3. You do this

    Set up the workspace

    Create the workspace, invite the team, and switch on the capabilities you will use. Add people before you import, so account owners and hours have someone to land on.

    You need

    Your team list

  4. The wizard does this

    Map your columns

    The wizard reads your headers and maps each column to a Scrambl field on its own. You review the mapping and change only what it should not guess. Describe the mapping to Benny and he drafts it for you.

    You need

    Your review

  5. The wizard does this

    Validate before anything is written

    Validation checks the whole file first and flags the rows to fix or skip. Nothing lands until the file passes, so a bad export costs you a correction, not a cleanup.

    You need

    Nothing

  6. You do this

    Check the run and switch over

    Every run lands in a history that shows exactly what it created. Spot-check it, recover the run if the file was wrong, and then the team stops working in the old tool.

    You need

    A look at the run history

What comes across?

The records the rest of the workspace runs on. Documents come in through their own path and arrive as articles.

Clients

Your account list, with the fields you already track and an owner on each account.

Contacts

The people at each client, 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 their person.

Documents

Wiki and doc exports become knowledge articles with categories and review dates, so the pages that explain how you work come with you.

From Notion, Confluence, Google Docs, Slack canvases.

What needs a decision before it moves?

Most of a migration is mechanical. These four are not, and each is easier to settle before the file is uploaded than after.

01

The order

Clients first, then the contacts and deals that belong to them, then projects, then the hours logged against those projects and people. Each list should be able to point at records that are already there.

02

Columns with nowhere to land

A column with no matching Scrambl field can become a custom field before you import, or stay behind. Decide which per column, so the mapping step is a review rather than a debate.

03

Owners and stages

Account owners should be people already in the workspace. Lifecycle and deal stages are assigned in Scrambl, so agree on the stages you will use before the team starts moving records through them.

04

How far back

Open deals and active projects earn a place. Hours from three years ago may not. An archive export of the old tool is a fine home for history nobody will query.

What if the file was wrong?

That is the question every migration 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. A bad run has a recovery path, not a cleanup weekend. And everything exports back out, because the data is yours.

Validated first

The whole file is checked before anything is written.

Recorded

Every run is kept, with what it created.

Reversible

A wrong file has a route back out.

Yours

Everything exports back out, whenever you want it.

Who helps?

The help center

Inside the app, and it covers the wizard step by step.

The people building it

The contact form reaches the team that ships the product, not a queue.

Included on Business

Onboarding, migration and training ship with the Business plan.

Questions people actually ask.

Don't see your question? Contact us

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, or describe the mapping to Benny and review his draft.

In what order should we import?

Clients first, then the contacts and deals that belong to them, then projects, then time entries, which keep their project and their person. Add the team to the workspace before any of it, so owners and hours have someone to land on.

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.

Is help with the migration included?

The in-app help center covers the wizard step by step on every plan, and the contact form reaches the people building the product. On the Business plan, onboarding, migration and training are included.

Ready to crack the chaos?

One workspace for projects, clients, finance, and everything in between. Try for free.

Try for freeSee pricing