Resolve sync errors in HubSpot Smart Transfer
Last updated: August 25, 2025
Available with any of the following subscriptions, except where noted:
All products and plans
|
After transferring your data using HubSpot Smart Transfer, you may see sync errors. This article gives an overview of the most common sync errors you may meet and the steps you can take to resolve them.
Property sync errors
| Error message |
Steps to resolve |
| Unable to create custom mappings |
The Data Sync mappings could not be set. Revert and retry the configuration. If the error persists, contact HubSpot Support. |
| Property is already present in default mappings |
This error can typically be ignored. The source field has the same label as a property included in the default mappings. The default mapping property will be used instead of creating a custom property. |
Attachment sync errors
| Error message |
Steps to resolve |
| Related remote id for <> object was not migrated |
The record associated to the attachment wasn’t synced. To transfer the attachment, its associated record needs to be transferred first. |
| Failed to assign owners, users stage is not present |
The Configure migration action did not include users. Therefore, HubSpot is unable to assign owners to attachments. The attachments will still transfer. However, if you want to transfer the user who created the attachment, you must run the Configure migration for users first. |
| Failed to retrieve attachment |
There was a third-party API error. |
Contact tag sync errors
| Error message |
Steps to resolve |
| Related remote contact is empty |
The source contact record was deleted. The record needs to be restored at the source, and the action must be reverted and run again. |
| Related HubSpot contact is empty |
The related contact was not synced. The record needs to be synced, and the action should be reverted and run again. Alternatively, you can update the record manually. |
| Failed to process contact tags |
There was a third-party API error. |
| Found unknown tag with, tagId <> |
This indicates that while performing the Post-Sync action, a tag was found that isn't a property option in HubSpot. You need to add the tag as an option to the HubSpot drop-down property. Then, the action needs to be reverted and run again. |
Currency sync errors
| Error message |
Steps to resolve |
| Failed to import currencies, multi-currency mode is not active |
The Configure migration action won’t work until multi-currency mode is active. If multiple currencies are needed, add the currencies to your HubSpot account. Then, the Configure migration needs to be reverted and run again. |
| There is no currency code found that fits <> symbol or <> name |
This message is shown if the corresponding currency can't be found in HubSpot. |
| Failed to import currencies, no base currency found |
For Zoho CRM, a base currency needs to exist in the source. |
Deal participant sync errors
| Error message |
Steps to resolve |
| Related remote contact is not found |
The association was not created because the source record was deleted. |
| Related HubSpot contact is not found |
The association was not created because the record wasn’t synced. |
| Failed to retrieve participants |
There was a third-party API error. |
| Related remote deal is empty |
The source deal record was deleted so the data cannot be retrieved. |
| Related HubSpot deal is empty |
The deal didn't sync, so no associations could be created for it. |
Deal person sync errors
| Error message |
Steps to resolve |
| Related HubSpot deal is empty |
The deal wasn't synced, so no associations could be created for it. |
| Related HubSpot contact is empty |
The association wasn't created because the record wasn’t synced. |
| Related remote contact is empty |
The association wasn't created because the source record was deleted. |
| Failed to retrieve opportunity relations |
There was a third-party API error. |
Deal pipeline and stage sync errors
| Error message |
Steps to resolve |
| Pipeline (<>) was created with modified stages' probabilities: <> |
Pipedrive allows stages to have a probability greater than 100%. Therefore, HubSpot sets it to 100%. |
| Changed duplicate name for pipeline from <%s> to <%s> |
There was already a pipeline with the same name in HubSpot. HubSpot changed the name of the pipeline created via HubSpot Smart Transfer. |
Line item sync errors
| Error message |
Steps to resolve |
| Related remote deal is empty |
The deal record was deleted at the source. |
| Related HubSpot deal is empty |
The deal record wasn’t synced. |
| Failed to retrieve deal products |
There was a third-party API error. |
List sync errors
| Error message |
Steps to resolve |
| Related HubSpot contact is empty |
The contact record wasn’t synced so it can’t be added to the list. |
| Failed to enroll contact to the list |
There was an issue adding the contact to the list. Try again. If the issue persists, contact HubSpot Support. |
Note sync errors
| Error message |
Steps to resolve |
| Related HubSpot object is empty |
The record associated to the note wasn’t synced. To transfer the note, its associated record needs to be transferred first. |
| Related remote object is empty |
The source record was deleted, so the note cannot be transferred. |
Team sync errors
| Error message |
Steps to resolve |
| The user was not migrated into HubSpot |
Since the user wasn't transferred, they can't be assigned to the team. Revert the Configure migration for users and teams, then proceed to add the user in the setup. |
| Renamed to <> |
There was already a team with the same name in HubSpot. HubSpot created the team. HubSpot changed the name of the time created via HubSpot Smart Transfer. |
Workflow sync errors
| Error message |
Steps to resolve |
| Failed to create <> workflow, some of the required properties are missing |
The workflow wasn't created because the required properties were missing. |
| Failed to create <> workflow, no options found |
The field in Copper has no field options. Therefore, the workflow wasn't created. |
| Failed to create creation date workflow, creation time property is missing |
The required property that stores the source creation time is missing. |
| Failed to create close date workflow, some of the required properties are missing |
The required properties are missing. These properties are: wonTime, lostTime, and expectedCloseDate. |
| Failed to create a workflow: <> |
There was an issue creating the workflow. Try again. If the issue persists, contact HubSpot Support. |
