Migrate owner fields to Attio users, pipelines as lists

Moves into Attio can now create each pipeline as an Attio list, and they link source user columns (Owner, Creator and similar) to Attio users by email. Lists are preselected when the source has two or more pipelines. A deal's owner column fills Attio's built-in Owner.

What changed

Pipeline lists. With the "A list per pipeline" layout, each pipeline is created as an Attio list. Lists are created with full access for everyone in the workspace and no per-member overrides.

User columns. From HubSpot and Pipedrive, a source column that points at the source's users, such as an owner or a creator, becomes a user attribute in Attio:

• A deal's owner column fills Attio's built-in Owner.
• Any other user column, such as Creator, gets a user attribute of its own.

Shuttio matches the source user's email against your Attio workspace members. The match ignores capitalisation and surrounding spaces.

How to use it

1. Start a migration at /intake, pick HubSpot or Pipedrive as the source and Attio as the destination.
2. Connect both sides on the Connect step.
3. Choose your objects. Tick the objects whose owners you want carried over, and tick deals if you want pipelines.
4. Open the field review. User columns appear as user fields with the note "Linked to users (matched by email)".
5. Start the free sample. Shuttio picks 5% of the records of each top-level ticked object at random (at least 10, at most 1,000) and keeps the records of other ticked objects that link to them. Open a few records and check the Owner field and the pipeline lists.
6. If the sample looks right, press "Run full migration". Into Attio the full run is free at any record count.

What it does not cover

• A person with no matching Attio user. A user attribute such as Creator stays empty, and Shuttio keeps the person's email, or the source id when the source gives no email, in a note titled "Users not linked" on the record. A deal's Owner goes to the person who started the migration when they are a member of the Attio workspace, and stays empty otherwise. Shuttio lists unmatched people once in the object's run summary. The summary shows up to 20 and then says how many more.
• Plus-addressed emails. ann+crm@example.com and ann@example.com are different addresses to the matcher. The first will not match a member registered under the second.
• No users are created. Shuttio never invites anyone to your workspace. To get a match, add the person to Attio first, then run the move.
• Matching needs permission to list users. Shuttio reads workspace members through Attio's user_management:read scope. It reads source users through HubSpot's optional crm.objects.owners.read scope or Pipedrive's users:read. Without Attio's scope the migration still runs, and the run shows one note that owners were not set.
• Rollback of lists. Shuttio cannot delete the lists it created. Rollback renames each list and names it in the rollback summary, so you can delete it yourself.

FAQ

Do I need to add my team to Attio before the move? Yes, if you want owners carried over. Matching is by email against existing workspace members. For a user attribute such as Creator, anyone who is not a member leaves the field empty and gets a note. A deal's owner goes to the person who started the migration, if they are a workspace member.

Will the sample show me which owners failed to match? The unmatched people are listed once per object in the run summary. Read it after the sample, add the missing users in Attio, then run the full migration.