Changelog

HubSpot destination: a property that clashes is left out, not added as a _2 copy#

27 October 2026 · HubSpot

When you move data into HubSpot, Shuttio no longer creates a second property with a numbered name such as score_2. If HubSpot already has a property with the same label or internal name that cannot take the values (a different type, computed, read-only or HubSpot-defined), nothing is created. The field is left out of the move and the field review shows a warning. From there you can remap it, create a custom property under your own name, or switch the field off. If a property with a different label already uses the internal name, the new property keeps your label and only its internal name gets a number. Applies to moves into HubSpot.

Activities now land as calls, emails, meetings and tasks, not merged into notes#

27 October 2026 · HubSpot, Pipedrive, Odoo, Clarify

Each source activity type now goes into the matching type in the destination. HubSpot gets calls and emails (calls used to arrive as notes, emails were not written). Odoo gets calls as Call-type entries (they were dropped before). Pipedrive receives emails as Email-type activities instead of tasks. Calls from SugarCRM, SuiteCRM, Salesflare, Vtiger, Nutshell and Teamleader Focus into Clarify are now calls, not notes. Pipedrive's Activities stay one object, and each row is routed by its type (call, meeting, email, task) into HubSpot, Odoo or Clarify. Limit: where a destination has no matching type, the Objects step names the fallback. For example, Clarify takes meetings, calls and emails as comments.

• Pipedrive to Odoo migration
• Pricing
• Migrate Pipedrive calls and emails to Odoo by type

Odoo: link user columns from HubSpot or Pipedrive to Odoo users#

27 October 2026 · HubSpot, Pipedrive, Odoo

When you migrate into Odoo with an API key, a source column that holds a user (an owner, creator or assignee) can now be linked to an Odoo user instead of being copied as plain email text. On the field review you can pick an existing Odoo field that links to users, or create a new one ('link to an Odoo user'). Each user is matched to an Odoo user by email or login. If no Odoo user matches, the field stays empty, the run summary counts it, and the email is kept in the record's internal note. Limit: the Odoo import package and the Odoo app do not write this field, so it applies to the API-key write only.

• HubSpot to Odoo
• Pipedrive to Odoo
• Migrate HubSpot owner to Odoo user fields by email

HubSpot destination: legal basis for contacts, clearer errors, existing fields reused#

26 October 2026 · HubSpot, Pipedrive

Moving a Pipedrive account into HubSpot now handles three things that failed in the first live run. HubSpot portals with GDPR on refuse new contacts that have no legal basis. You now pick one from your portal's own options, on the Options step or later on the migration's legal-basis page. Shuttio never picks one for you, and a value mapped from your source wins. A start or retry is blocked while contacts have failed for this reason and no choice has been made, and the Errors tab links to the legal-basis page. HubSpot errors on a write now name the missing property and what to do, and say what HubSpot refused. "Reconnect" advice shows only for 401 and 403 errors. A source field named like an existing HubSpot property (any case) is now mapped into that property by default, in the field review and in the run, instead of creating a duplicate. Picklist values match by label. If a HubSpot-defined list lacks a value, the record still imports and the run summary lists the missing values per field. Link and name columns no longer show up as fields left out. Limit: when two source fields map to one property, the first non-empty value is written, and the summary counts the rows where the second differs.

Guide: migrate HubSpot to Attio#

21 October 2026 · Attio, HubSpot

A new guide compares three ways to move HubSpot to Attio: Attio's Import2 flow, a CSV import and Shuttio. It lists what moves, what stays behind and how to check the result.

• Migrate HubSpot to Attio

HubSpot SMS, WhatsApp and LinkedIn messages move to Attio#

15 October 2026 · Attio, HubSpot

HubSpot messages sent over SMS, WhatsApp and LinkedIn now arrive in Attio as activities.

• HubSpot guide

Calls, logged emails and activity types land as Attio activities#

15 October 2026 · Attio, HubSpot, Pipedrive

Calls from HubSpot, Affinity and Pipedrive arrive in Attio's Phone calls, and logged emails arrive as a Logged emails activity, unticked by default. Other done Pipedrive activity types become an activity of their own. If a workspace has no activity scope or plan, Shuttio falls back to notes and tasks and counts them in the run summary.

• Pipedrive guide

A page for each source and destination pair#

14 October 2026 · Attio, HubSpot, Pipedrive, Odoo

Every pair a customer can finish today has its own page, such as HubSpot to Attio, Pipedrive to Attio and Pipedrive to Odoo. Each page lists the objects that move for the pair and links its guide.

• HubSpot to Attio
• Pipedrive to Odoo

HubSpot emails can be read with an optional scope#

13 October 2026 · HubSpot

A HubSpot connection can ask for the optional sales-email-read scope. With it, Shuttio reads the emails logged in HubSpot, so they can migrate with the records they belong to. Without the scope, the connection works as before.

Attachments: files move with their records#

6 October 2026 · Attio, HubSpot, Odoo

An Attachments switch on the Options step moves HubSpot files into Attio and into Odoo, with the file count and an estimate shown before the run. Files run as their own job after the records, and cancelling deletes the files first. Failed files are listed as rows with a reason.

• Supported objects for HubSpot

Record filters: migrate only the records that match#

6 October 2026 · Attio, HubSpot, Pipedrive

A Filters step lets you narrow each object by field values or dates before the run, and shows a live match count under the filter. HubSpot, Pipedrive and Attio apply the filter at the source, so records that do not match are not read. The run page shows how many records are in the source and how many were filtered out, and filters never lower the price.