search shadow

Menu

Articles in this section

See more

HubSpot to HubSpot Migrator Follow

 

Index

  1. Introduction
  2. Please read before you begin
  3. Important Notes
  4. Read-Only Standard Fields
  5. Pipelines and HubSpot Features limited by license tier
  6. Setup and Activation - HubSpot to HubSpot Migrator
  7. How to Uninstall the App
  8. Migrator Functions

 

Introduction

The HubSpot to HubSpot Migrator transfers data from the Source HubSpot portal to the Target HubSpot portal. This application is GDPR Compliant and hosted/processed in the EU. Custom Objects are now able to be migrated as of 01/15/2023.

 

Please read before you begin

Please ensure that you are a Super Admin in HubSpot before initiating the migration process or it may fail to complete.

 

Upon completion of your purchase of the HubSpot to HubSpot Migrator app the migration process will automatically start. The app is a single use license so if you need to run multiple migrations you will have to purchase the app again. We do offer volume discounts and if you reach out to our support team they will discuss that with you. Please be aware of this before proceeding with purchasing the tool.

 

Important Notes

During the migration process, Owners of the Target HubSpot will have all of their relevant data associated with them. In this process, unless otherwise configured in the HubSpot portal itself, the user can potentially receive a massive amount of emails informing them of new data being assigned to them. It may be a good idea to either change this configuration beforehand on the Target HubSpot portal, or to warn your users of the upcoming emails. You can see how to change your notifications here https://knowledge.hubspot.com/settings/how-to-set-up-user-notifications-in-hubspot.

 

It is very common that you will find the need to clean the destination portal of duplicates or fields that are no longer needed after you migrate so you should plan to do that. It is also common that when you are migrating large volumes of data that some records may not be able to migrate due to various reasons such as improper characters and duplicate data. By using our tool you accept that you understand this can occur.

 

Do not feel the need to re-create custom properties or pipelines before initiating the migration, the tool will do that for you and if you attempt to do it yourself first you may experience errors during the migration process. If migrating into a sandbox you can and should use the native import feature to create your pipelines, workflows, etc.

 

If you are interested in migrating to a specific business unit we currently cannot migrate directly to a business unit because there are no APIS to control this at this time. However we create a field called "Original HubSpot ID" that you can use as an identifier for all migrated data for Contacts/Companies/Deals/Tickets. Simply create a filter view where "Original HubSpot ID" is not "NULL" then mass assign all of those records to the business unit of your choice and you are good to go. You can read how to do mass edits here. https://knowledge.hubspot.com/crm-setup/how-can-i-bulk-edit-contacts-companies-deals-or-tasks 

 

If you are using a currency in the Source portal please make sure that same currency is enabled in the destination portal prior to the migration. Otherwise certain pieces of data may fail to migrate. For example if you have line items in the EUR currency in the source portal, and EUR is not enabled as a currency in the destination portal, if you attempt the migration those records will fail to migrate.

 

Read-Only Standard Fields

All of the default and custom properties that can be written map over during migration, unfortunately there are some historical data points such as “Became a Customer On” and “Original Source Drill-Down” that are Read-Only formulas. Those we cannot write into the destination portal and therefore they will not map but rather “recalculate” the formula upon completion of the migration. The same applies to web analytics as that data is all read only and it is just not possible to write that to another portal. The source portals Deal "Created Date" property, and Ticket "Created Date" property will be migrated to the destination portal.

 

However if you are worried about losing that information don't worry! Our tool Ultimate Data Export exists to export all of that data and more out of HubSpot so that you still have access to that data for reporting purposes during the transition period. https://datawarehouse.io/product/hubspot-ultimate-data-export/ 

 

 

Pipelines and HubSpot Features limited by license tier

If you have the standard sales pipeline in the source and destination portal please change the name of the pipeline in the source portal to something else before running the migrator unless you want those two pipelines to merge. All custom pipelines will merge from the source to the destination without issue. Beyond just pipelines the migrator will abide by the limitations set by the HubSpot API. It is your responsibility to understand those limitations before proceeding.

 

Please also note that depending on your version of HubSpot not all pipelines may be able to migrate. This is due to the aforementioned limitations Imposed by HubSpot and is not a deficiency in our tool. To circumvent this you must insure the total quantity of pipelines that will end up in the source is within those limitations. Generally speaking you should only be concerned about this if you are migrating to a Free or Starter HubSpot portal.

 

You can read about those limitations and more here https://legal.hubspot.com/hubspot-product-and-services-catalog.

 

 

Setup and Activation - HubSpot to HubSpot Migrator

  1. After adding the HubSpot to HubSpot Migrator to your cart on Datawarehouse.io, you will be taken to this page:mceclip0.png
  2. The “Authorize Source HubSpot” button will allow you to connect your Source HubSpot portal to the application. Reminder, the Source HubSpot Portal is where your data flows out from.
  3. The “Authorize Target HubSpot” button will allow you to connect your Target HubSpot portal to the application. Reminder, the Target HubSpot Portal is where your data will go.
  4. After these two connections are made, the “Continue to Checkout” option will be clickable. Please click this button to continue onwards to payment.  
  5. When the payment is completed and the order is received, the migration will proceed automatically. You will receive an email informing you of the start of your migration.
  6. The migration will usually complete in 24 hours, but may take longer depending on the amount of data your Source HubSpot portal contains. You will receive an email informing you of the completion of your migration once it is done.
  7. During the process of migration, please refrain from making drastic changes to the Source HubSpot portal or the destination portal. Any changes made on the Source HubSpot portal, depending on the time of the change and the progress of the migration, may not be reflected on the Target HubSpot portal.

 

How to Uninstall the App

*Do not perform these step until you are done using the Migrator

1.  Open up your Source or Destination HubSpot Portal. In the top right section of HubSpot click on the house icon.

2. A menu will drop down. Click on the Connected apps link.

 

mceclip0.png

3.  Then click on the actions button for the HubSpot to HubSpot migration app. And click uninstall.

mceclip1.png

4. Perform this same sequence in the remaining Source or Destination portal to finish uninstalling the app.

 

Migrator Functions

 

Object Type

Process

Errors and Duplicates

Owners

The emails of the Source HubSpot Owners will be used to create new users in the Target HubSpot portal. These new users will only have default privileges, and will need to be given their correct levels of permission.
  1. If the user already exists in the Target Portal, the Source user will not be created.
  2. Users that have failed to be created for any reason will be logged.
  3. Deactivated Users that are still record owners will not migrate

Folders

The folders of the Source HubSpot will be copied and created in the Target HubSpot. The names and path of the folders will remain the same. Two extra folders named “root” and “source_hubspot_attachments” will be created.
The “root” folder will hold files that previously existed in the Source HubSpot portal’s root directory. This is due to HubSpot not allowing files to be created directly in the root directory via API.

The “source_hubspot_attachments” will contain files from the Source HubSpot that are of HIDDEN_PRIVATE status. These include attachments of objects like deals, companies, and engagements.  
  1. If the exact same folder path already exists, then the folder will not be created.
  2. Folders that have failed to be created for any reasons will be logged.

Files

Files from the Source HubSpot will be downloaded directly from the Source HubSpot into the Target HubSpot. The Migrator Application will not store any files.
Files that previously existed in the Source HubSpot portal’s root directory will be stored into the Target HubSpot portal’s “root” folder.
Attachments whose directory was otherwise hidden in the Source HubSpot Portal will now be stored and visible in the “source_hubspot_attachments” folder.
  1. Hidden attachments with the exact same name may have an additional number appended to the end of them. These will still be correctly associated with their respective objects
  2. If a file name has a character in it from a Language not supported in the Destination portal then that file may fail to migrate.
  3. Files that have failed to be added for any reasons will be logged. 

Custom Properties

Custom Properties from Deals, Products, Line Items, Tickets, Contacts, and Companies will be transferred from the Source HubSpot to the Target HubSpot.
Any property that is generated by HubSpot, but not included in a default portal, cannot be transferred over due to the limitations of HubSpot’s API. An example of which is “hs_price_usd”, a Product property.

 

*More Details about Custom Property Migration Conditions listed at the bottom of this page.
  1. If a custom property of the same internal name exists in both the Source and Target HubSpots, the Migrator will attempt to combine the options of the Source and Target HubSpots, and then update the Target HubSpot with the new list of fields.
  2. The migrator cannot migrate formula fields.
  3. Custom Properties that have failed to be migrated for any reason will be logged.
  4. The migrator will create a custom property called Origin Portal ID to designate records that were migrated and to identify which portal they came from.

Pipelines

Pipelines from Deals, and Tickets will be transferred from the Source HubSpot to the Target HubSpot. 
  1. Pipelines that have failed to be created for any reasons will be logged.
  2. If a pipeline has the same name it will be merged.

Deals

Deals from the Source HubSpot portal will be transferred over to the Target HubSpot portal. All associations to other objects will be retained.

  1. If the same Deal exists in both the Source and Target HubSpots, the deal will be recreated in the Target HubSpot, resulting in a duplicate.
  2. Any Deals that fail to be created will be logged.

Products

Products from the Source HubSpot portal will be transferred over to the Target HubSpot portal. All associations to other objects will be retained. 
  1. If the same Product exists in both the Source and Target HubSpots, the product will be recreated in the Target HubSpot, resulting in a duplicate.
  2. Any Product that fails to be created for any reason will be logged.

Line Items

Line Items from the Source HubSpot portal will be transferred over to the Target HubSpot portal. All associations to other objects will be retained. 
  1. If the same Line Item exists in both the Source and Target HubSpots, the line item will be recreated in the Target HubSpot, resulting in a duplicate.]
  2. Any Line Item that fails to be created for any reason will be logged.

Tickets

Tickets from the Source HubSpot portal will be transferred over to the Target HubSpot portal. All associations to other objects will be retained. 
  1. If the same Ticket exists in both the Source and Target HubSpots, the ticket will be recreated in the Target HubSpot, resulting in a duplicate.
  2. Any Ticket that fails to be created for any reason will be logged.

Companies

Companies from the Source HubSpot portal will be transferred over to the Target HubSpot portal. All associations to other objects will be retained. 
  1. Companies are deduplicated/merged using the domain name property in HubSpot. If the same Company Domain Name exists in both the Source and Target HubSpots, the company record will be merged in the Target HubSpot. Domain Name is the "key" for merging Companies.
  2. Companies that do not contain the same Domain Name, but have the same Company name will not be merged. This may result in duplicates.
  3. Any Company that fails to be created for any reason will be logged.

Contacts

Contacts from the Source HubSpot portal will be transferred over to the Target HubSpot portal. All associations to other objects will be retained. Contacts are mapped and merged using the contact email address. Contacts without an email address will not be migrated.

In the event that the Source HubSpot has a Contact with a Custom Property with values that are invalid for the Custom Property type (ex. Having the value “yes” for a boolean type field), then the contract will be transferred without the invalid property in question.
  1. If the same Contact exists in both the Source and Target HubSpots, the Target HubSpot’s contact will be updated with the information from the Source HubSpot. Extra information will be added, and conflicting fields will be overwritten by the data from the Source HubSpot.
  2. Any Contact that fails to be created for any reason will be logged.
  3. "Marketing Contact" status is not migrated and all contacts migrated are migrated as Non-Marketing Contacts. You can select all migrated contacts inside of HubSpot after the migration and flag them as marketing contacts as needed.

Contact Lists

Active and Static Contact lists will migrate from the Source to the Target Portal.
  1. If an active list in the source portal references a form as part of a filter it will not migrate. This is because we do not migrate forms.
  2. Active Lists that are built with a filter that references historical web traffic data will not populate with the same information. This is because we do not migrate historical web traffic data.
  3. Active lists that are built with a filter refencing marketing emails will not migrate. This is because we cannot migrate marketing emails.
  4. The migrator will create a list of all contacts migrated from the source portal.

Engagements (Notes, Meetings, Tasks, Emails)

All Engagements related to Contacts, Companies, Deals, and Tickets will migrate from the source to the Target Portal.
  1. Campaign Emails do not migrate due to HubSpot API Limitations.
  2. Engagements with a significant amount of attachments will take longer to migrate and will likely extend your migration period beyond 24 hours.
  3. Comments on engagements cannot currently be migrated due to HubSpot API limitations.

Custom Objects

All Custom Objects Schemas, Properties, Data, and Associations will migrate from the Source to the Target portal.
  1. HubSpot as of 1/14/2023 has a maximum limit of 10 total custom objects schemas per HubSpot Portal. Our application cannot breach these limits. As an example if the source portal has 5 custom object schemas, and the destination portal has 7 custom object schemas, only 3 custom object schemas from the source will be migrated. The remainder will be ignored.
  2. If a custom object schema in the source matches a custom object schema in the destination, the custom object data and associations from the source will migrate into the existing custom object in the destination. If the schema does not match exactly then the app will create a new custom object in the destination and migrate the data into that object.
  3. Any Custom Object that fails to migrate for any reason will be logged.

 

 

* Custom Properties Migration Details.

 

Property exists in Destination

Property exists in Source

Type(s)

Expected Action

True

False

any

Any new Contact created as a result of migration from the Source portal have the default value from the destination set for this property

False

True

any

New Custom Property created.
All Contacts in Destination portal have the default value set, unless there is a matching Contact in the Source portal, in which case it is set to the value of the property for that Contact in the Source portal

True

True

Same type

*Example* If the value options are a List, these are merged to a single list covering all options in both Portals. 

True

True

Different Type

Property will fail to migrate If the API name is the exact same in the Source and Destination portals but the Type is different.

 

 

Related articles