Migrate HubSpot owner to Odoo user fields by email

Shuttio now links a Pipedrive field that holds one of your Pipedrive users to a real Odoo user. Shuttio writes this link through the Odoo API-key connection: URL, database, login and API key. On the field review you pick an existing Odoo field that links to users, or create a new field of the type "link to an Odoo user", which needs an administrator's API key.

What changed

A Pipedrive field that holds a user, for example "Assigned to", can now be written into an Odoo field that points at an Odoo user.

For each value, Shuttio looks for an Odoo user whose email matches. If none has that email, it tries the login. Shuttio never creates an Odoo user. Shuttio matches internal users only. A portal user never matches.

When no Odoo user matches:

• The field stays empty on that record.
• The run summary counts it, for example "3 user fields (Creator, Assigned to ...) had no Odoo user with the same email and were left empty."
• On contacts, companies and products, the record's internal note gets a "Users not linked (no Odoo user with this email)" entry with the field name and the email. Deals and leads have no such note, so only the run summary count records it.

How to use it

1. Start a migration from Pipedrive to Odoo and choose your objects.
2. Connect Odoo with a URL, database, login and API key. To create new fields, use the key of an administrator.
3. Open the field review and find the Odoo section. Each of the source's own fields has a select.
4. For a user column, open the select. It lists the Odoo fields that link to users. Pick one, or pick "Create a new field (link to an Odoo user)". Shuttio adds new fields only on contacts and companies, deals and leads, products, and helpdesk tickets.
5. Start the free sample. Open a few sample records in Odoo and check that the user field shows the right person.
6. Run the full migration when the sample looks right. The price is shown before it starts.

If the connected key is not an administrator's, Shuttio says so on the review and offers only existing fields or Skip. Create stays unavailable until you reconnect with an administrator's key.

What it does not cover

• Import package. In an Odoo import package, a source's own fields go into each record's internal note, so the value is not linked to a user.
• No new Odoo users. A person who is in Pipedrive but not in Odoo stays unlinked. Add the user in Odoo first, then run the migration, if you want the link.
• Email is the key. A person whose Pipedrive email matches neither the email nor the login of an Odoo user will not match, even if it is the same human.
• Record owners are a separate setting. The owner of a deal or contact is matched by email too, but its fallback is the "Owner when no Odoo user matches" choice on the review. This guide covers the extra user columns.

FAQ

Does this change how deal and contact owners are assigned? No. Owners follow their own rule: Shuttio gives a record to the Odoo user with the same email as its source owner. If there is none, the record goes to the fallback owner you choose on the field review, or to Odoo's default if you choose none.

Can I put a user column into a text field instead? No. For a user column the select lists only Odoo fields that link to users, the create option for a new user link, and Skip. Skip fills no Odoo field from that column.

What if I roll the migration back? Cancelling deletes what the migration created, in reverse order. An Odoo field added by the migration is dropped only while no record holds a value in it and Odoo accepts the removal. Otherwise it stays in Odoo and Shuttio names it.