Attio

Sign in with Attio (read-only for this move), and give Clarify's workspace slug and a Personal API key. Shuttio never writes to Attio.

Object by object: What objects are supported for Attio migrations.

What Shuttio reads and moves

The list below describes the move into Clarify. Where Clarify or Odoo differ, the destination's own article says so.

• Companies, people and deals with their fields. A person's company, and a deal's company and people, are linked in a second pass.
• Notes, on the deal, person or company they were attached to.
• Tasks, with the due date and the completed state.
• Calls: Attio's phone calls, with the time, length and direction.
• Other activities: the activities you added yourself, each record with its title, time and text.
• Lists, with their entry attributes.

Where each thing lands

Notes, tasks, meetings, calls, files, owners and lists depend on the destination. This is the row for Attio, generated from the same tables the runner uses:

Each destination's own article says how its data is written: Attio, Clarify, Odoo, HubSpot, Pipedrive, Breakcold, Twenty.

Permissions and why

The same Shuttio app serves Attio as a source and as a destination, so its full scope list is on Using Shuttio with Attio. As a source it is read-only.

Known limits

• Custom objects: On this pair Shuttio reads Attio's companies, people and deals. A custom object in your workspace is not offered on the Objects step.
• Meetings and files: Shuttio does not read Attio's meetings or files on this pair. Clarify builds its own meetings from the calendar you connect to it, and a file stays in Attio.
• Interactions, email history and call recordings: Attio computes interactions from the connected inbox and calendar, and Shuttio does not read them or the recordings. Connect the same inbox and calendar to Clarify.
• Emails: Shuttio reads no emails from this source.
• Large and linked files: a file over 50 MB, and an entry that is only a link, is listed as a failed row and not copied.
• Owners: an Attio assignee is not carried to Clarify, so a task arrives unassigned.

Attio into Attio

• Objects and fields, by slug: Each object and attribute keeps its slug and its type: text, number, currency with its code, select and status with their options in order, location, personal name, rating, checkbox, dates, and links to other records. A slug the destination already holds with another type gets a field of its own.
• Custom objects: Created in the destination under the same slug. One that already exists there is reused, and a link between two of your objects is created as the same link.
• Owners and assignees, by email: Owners, assignees and other member fields are matched to members of the destination workspace by email. An owner with no match goes to the person who started the migration.
• Lists with their entry values: Lists on any object, with each entry attribute at its own type: statuses, member fields, locations and dates arrive as such, not as text.
• Notes, tasks and meetings: On the records they belong to, custom objects included. A note written in Markdown stays Markdown. Each note is written as the user who connected the destination. The source's author is not kept.
• Calls and other activities: Phone calls become Phone calls records again, with time, length, direction and outcome. Each activity you added yourself is created in the destination under its own name and keeps its records.
• Files: Each file is copied record by record, at about one file per second. A file over 50 MB and a linked file (a link, not a file) are reported, not copied.
• The date a record was created: The date a record was created in the source is kept in a text field named "Created in source", because Attio sets creation dates itself.

• Interactions and email history: Attio computes them from the connected inbox and calendar, and has no write endpoint for them. Connect the same inbox to the destination workspace.
• Call recordings: Shuttio does not read or copy them. They stay in the source workspace.
• Values on a record that already existed in the destination: A company or person that matches an existing record in your destination by domain or email is updated, not added twice. Rollback removes what Shuttio created. It does not restore values it overwrote on a record that already existed.

Attio into Odoo

• Companies and people: into Odoo partners (res.partner), a person linked to their company in a second pass. A partner is matched by domain or email and updated, not duplicated.
• Deals: into CRM opportunities. The deal status becomes the stage, in Attio's order; a status Attio marks as won or lost is kept as such. A deal's company and first person are linked in a second pass.
• Notes, tasks and meetings: notes become internal notes in the chatter of the deal, person or company; an open task a scheduled To-Do, a completed task a Done entry; a meeting a Calendar event when the Calendar app is installed.
• Owners: a deal's owner and a task's assignee (the first one) become the Odoo user with the same email. One with no match goes to the fallback user you choose before the run.
• Other fields: each Attio attribute with no Odoo counterpart goes to an existing writable x_ field you pick, or to a new x_ field when your key has the rights.

• Custom objects, lists and files: not offered on this pair. Odoo has no place for an Attio list, and the files are read from Attio per record, which this pair does not do.
• A person's or company's location, and attributes Odoo has no field type for: not carried unless you pick an x_ field.
• Interactions and email history: Attio computes them from the connected inbox and calendar; they stay in Attio.