Migrations

AutoBoarding brings your projects, boards and tasks across from Trello, Jira Cloud, ClickUp or Asana. It finds out what is in the other tool, shows you exactly what will and will not come across, waits for someone to approve it, and only then writes anything into your organization.

The four steps#

1. Find out what is there — discovery counts everything in the source. Nothing is written.
2. Review what will and will not come across, what the connector cannot bring over, how people are matched and the suggested field mappings.
3. Approve — someone with the approval permission authorizes writing the data in.
4. Migrate — the records are created, and a report accounts for every item.

Who can do what#

Which tools you can migrate from#

Jira Cloud, ClickUp and Asana start switched off. UnitX turns one on for an organization once it has been checked against that platform’s current API. A source that is not available yet is still listed, greyed out, with — not enabled yet. If you try to use one, you will see a message naming it — this is not a permission problem, and signing in again will not help. Contact UnitX support to ask for it.

Start a migration#

1. Connect the source tool first

   Under Integrations, connect the tool you are moving from. Only connections whose status is connected can be used.

2. Choose New migration

   On the Migrations page. The Start a migration dialog opens.

3. Pick the Source and Connection

   Choose the tool, then the connection to read from. If there is none, the dialog says Connect the source under Integrations first.

4. Choose Create

   You see Migration created — run discovery next. Open it from the list.

1. Find out what is there#

On the migration’s page, choose Run discovery. It reads the source and counts what is there, without writing anything to your organization. When it finishes you see Discovery finished — review what was found. If it fails, the page shows a Reason saying what went wrong.

2. Review#

Will migrate and Will not migrate#

The review puts what will not come across next to what will, each with a count and — for what will not — the reason. Read the Will not migrate column, not just the readiness number: anything listed there will not be brought across at all.

Readiness is the share of everything found that has a UnitX equivalent. It counts what will not migrate, so treat it as a floor rather than a headline.

People#

UnitX matches people in the source to members of your organization and shows how many were matched automatically. People it could not match confidently are listed as Same domain only or No match. They will be invited rather than linked to an existing account — a near-match is never merged automatically. Choose Invite them to UnitX to send UnitX’s ordinary invitations; people with no email address in the source cannot be invited. No one’s password is read or carried across.

2b. What this connector cannot bring across#

A list of features the connector cannot migrate at all — true of the connector whether or not your account uses them — with a reason for each and, where discovery counted some, how many were found in your account. Anything here stays in the source tool and needs a plan of its own.

2c. Suggested field mappings#

UnitX suggests where each source field should go, with its reasoning and how confident the match is:

Same name

The field names match.

Known equivalent

A recognised equivalent, such as a synonym.

Same type

Matched on the kind of value the field holds.

Same value

Matched because the values overlap.

Needs a decision

Nothing was proposed — you decide.

Suggestions are never applied on their own. The mapping is frozen once the migration is approved.

3. Approve#

When discovery has finished, someone with migration.approve chooses Approve. Approval records who authorized writing this data into your organization. People without the permission see Someone with the approval permission needs to sign this off.

4. Migrate#

After approval, choose Start migration. The result is one of: all items migrated, N item(s) need attention, or The migration failed. You can choose Cancel at any point before a migration finishes.

Reading the result#

• Migration fidelity — a score, never shown alone: each part of it states what it measures, its value and its weight.
• Every item found — counts by outcome: Migrated, Transformed, Partly migrated, Not supported and Needs your attention. Nothing found in the source is left out.
• Needs attention — each failed item with the reason it failed.
• Checked against the source — the source is counted again after the migration, and each category shows Match or Differs.

Retry a single item#

1. Read the reason

   Under Needs attention, each failure names what went wrong — a missing title, a container that was not migrated, and so on.

2. Choose Retry this one

   UnitX re-attempts that item alone and tells you whether it came across or failed again, with the reason.

• A retry uses what was already read from the source; it does not read the source again. Correcting the record in the other tool and retrying will not pick up the correction — start a new migration for that.
• Only failed items can be retried. Items that are simply not supported would fail again.
• Retrying cannot create a duplicate.

Migration statuses#

created

Set up; discovery has not run.

discovering

Reading the source.

ready

Discovery finished; waiting for review and approval.

running

Creating records.

paused

Paused from the browser extension; can be resumed.

completed

Finished with everything accounted for.

completed with warnings

Finished, with items that need attention.

failed

Stopped with a reason shown on the page.

cancelled

Cancelled before finishing.

Completed, failed and cancelled migrations are final. To try again, start a new migration — items already brought across are skipped.

Related pages#

• AutoBoarding browser extension
• Integrations
• Projects
• Members and invitations