Index

1. Introduction
2. Please read before you begin
3. Read-Only Standard Fields
4. Property Group Filtering
5. Pipeline Filtering
6. Pipelines and HubSpot Features limited by license tier
7. Workflow Migration (Beta)
8. HubSpot to HubSpot Migrator
   • Important Notes 
   • Setup and Activation
9. HubSpot Schema Replicator
   • Important Notes
   • Setup and Activation
10. HubSpot Portal Toolkit
    • Important Notes
    • Setup and Activation
11. HubSpot Portal Sync
    • Important Notes
    • Setup and Activation
    • Selective Sync
12. HubSpot Beta APIS
13. How to Uninstall the App
14. App Functions

    • Properties Migration Details

 

Introduction

 

The HubSpot to HubSpot Migrator transfers your schema and data from the Source HubSpot portal to the Target HubSpot portal. This application is GDPR Compliant and hosted/processed in the EU. 

 

The HubSpot Schema Replicator only copies your HubSpot Schema from the Source HubSpot portal into the Target HubSpot portal. It does not copy data. Only the configuration/setup of certain parts of HubSpot.

 

The HubSpot Portal Toolkit is designed to allow you to easily perform an unlimited amount of data migrations as often as you would like. Its perfect for merging portals, creating change sets, testing apps in dev accounts, or deploying templated sets of data to multiple portals.

 

Portal Sync continuously syncs data between multiple HubSpot Portals. This application is designed to sync data automatically between two or more HubSpot portals. Great for users with the need to push data between multiple HubSpot portals on a recurring basis.

 

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 app the migration process will automatically start.  You can visit https://datawarehouse.io/account/my-app-information-item/ to see the status of your migration/replication and to review historical runs.

 

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.

 

Read-Only Standard Fields

All of the default and custom properties that can be written will automatically map over during migration, but 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/ 

 

Property Group Filtering

Only Available in the Schema Replicator, Pro, Enterprise, and Portal Sync versions of the Portal Migration Suite.

 

This function allows for the filtering of properties within selected property groups. This allows you to define which properties you want to migrate/replicate via their inclusion in a specific property group. If you only want to migrate/replicate a select set of properties simply assign them to the same property group or groups that you want to migrate/replicate. Then the app will only migrate/replicate the properties in the selected groups.

 

If you wish to migrate/replicate everything for a given object, select no options during this step.

 

The following property definitions and the data for these properties are always migrated regardless of your selections below in order to ensure the migration can be completed.

 

Contacts

• Contact Name
• Contact Email
• Business Unit Assignment when applicable

Companies

• Company name
• Company Domain
• Business Unit Assignment when applicable

Deals

• Deal Name
• Deal Pipeline
• Deal Pipeline Stage
• Business Unit Assignment when applicable

Tickets

• Ticket Name
• Ticket Pipeline
• Ticket Pipeline Stage
• Business Unit Assignment when applicable

Products

• Product Name
• Billing Frequency
• Unit Price

 

Pipeline Filtering

Only Available in the Schema Replicator, Pro, Enterprise and Portal Toolkit versions of the Portal Migration Suite.

 

This function allows for the filtering of pipelines. This allows you to define which pipelines and records within those pipelines that you want to migrate/replicate. If you only want to migrate/replicate select pipelines then you should select which pipelines you want.

 

If you wish to migrate/replicate all pipelines and records for a given object, select no options during this step.

 

Pipelines and HubSpot Features limited by license tier

If you have the standard sales pipeline with the internal name of default in the source and destination portal the app will merge these two pipelines as part of the migration process. Please move the data in the source portal into a different pipeline if you do not want them 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.

 

Workflow Migration (Beta)

This feature is powered by a Beta API. HubSpot may change how this API works at any time with no advance warning. We highly recommend you review the Workflows after migrating them and before turning them on. Some Workflows may unexpectedly not migrate due to this Beta status and we cannot guarantee they will all migrate at this time. This is because there may be edge cases that prevent workflow migration that would have to be resolved by an API update on the HubSpot side.

 

Below are some key points about the Workflows Migration and how it works.

 

• Workflows are migrated in a deactivated state.
• Workflows are only created as new Workflows due to HubSpot API limitations.
• Existing Workflows cannot be updated by the app due to HubSpot API limitations.
  • If a duplicate or workflow with the same name already exists in the destination portal, the app will append a progressive number sequence starting with -1 after the workflow name in order to complete the migration.
• Existing enrollments, and enrollment history are unable to be migrated due to HubSpot API limitations. If necessary you should adjust your workflows to account for this before activating them.
• The app performs an automatic data mapping that attempts to accurately map assets referenced in Workflow filters and actions.
  • In order for this mapping to occur, you must migrate the items referenced in workflows. For example, if a workflow references a form, you must also use our application to replicate or migrate the form in order for the mapping to complete.

• Certain filters and actions may need to be updated post-migration in the target portal. If a workflow contains a reference to an item that we did not migrate, the app will be unable to map and reference the associated item. If you are unable to migrate associated items with the Workflow will still migrate, but cannot be enabled until you resolve the missing reference(s).
  • For example if a workflow references an email, the workflow will still migrate but will require an update before it can be activated.  See an example of this below.

Known Issues with Workflow Migration

• Re-enrollment criteria for workflows currently do not migrate. HubSpot is aware of this and is working on resolving this.
• Goal Lists are not supported
• Workflow folders are not supported
• Business unit assignment is not supported.

 

HubSpot to HubSpot Migrator

The HubSpot to HubSpot Migrator is a version of the Portal Migration Suite of apps that migrates both the Schema and Data of one HubSpot Portal into another one. An example of a Schema would be the all of the Contact properties. An example of "Data" would be all of your contact records.

 

Important Notes- HubSpot to HubSpot Migrator

 

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. 

 

The "Rollup" type of custom calculation properties cannot be created via the HubSpot APIS, and because of this our application cannot migrate them.

 

The "Property Sync" type of custom properties cannot be migrated or replicated via the HubSpot APIS due to deficiencies in how the HubSpot APIS return information about this property type.

 

Custom Call/Meeting types cannot be migrated due to API limitations. However if the Custom Call/Meeting types from the source portal are created in the destination portal prior to running the migrator the data will map correctly to those Custom Call/Meeting types.

 

If you are interested in migrating to a specific business unit you will need to use the Enterprise version of the app.

 

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.

 

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:
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. You can visit https://datawarehouse.io/account/my-app-information-item/ and select the HubSpot to HubSpot Migrator app to initiate and view the current status 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.
   
   

 

HubSpot Schema Replicator

The HubSpot Schema Replicator is a version of the Portal Migration Suite of apps that only replicates the Schema/Setup of a HubSpot portal from one portal into another. It does not migrate data, for example this version of the application will migrate all of your Contact properties but it will not migrate your Contact data.

 

Important Notes - HubSpot Schema Replicator

 

The "Rollup" type of calculation properties cannot be created via the HubSpot APIS, and because of this our application cannot replicate them. 

 

The "Property Sync" type of custom properties cannot be migrated or replicated via the HubSpot APIS due to deficiencies in how the HubSpot APIS return information about this property type.

 

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 replication. Otherwise certain properties may fail to migrate. For example if you have a calculation property that references the EUR currency in the source portal, and EUR is not enabled as a currency in the destination portal, if you attempt the replication that calculation property would fail to replicate.

 

Currently this version of the application cannot replicate, call/meeting types, reports, and dashboards but we are working on adding this functionality as soon as the authorized and secure public APIS for it are made available.

 

Setup and Activation - HubSpot Schema Replicator

1. After adding the HubSpot Schema Replicator to your cart on Datawarehouse.io, you will be taken to this page:
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 schemas are copied 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 schemas will copy too.
4. After these two connections are made, the “Continue” option will be clickable. Please click this button to continue onwards to the configuration screen.
5. On the configuration screen you can check which schemas you do and do not want to replicate. Once you are ready click the "Continue to Checkout" button.
6. You can visit https://datawarehouse.io/account/my-app-information-item/ and select the Schema Replicator to initiate app to view the current status of your replication.
7. The schema replication will complete in about 15 minutes or less, but may take longer depending on the amount of schemas you replicate. You will receive an email informing you of the completion of your schema replication once it is done.
8. During the process of replication, please refrain from making drastic structural 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.

 

HubSpot Portal Toolkit

 

The HubSpot Portal Toolkit is the flagship version of the Portal Migration Suite of apps. Designed to allow you to easily perform an unlimited amount of data migrations as often as you would like. Its perfect for merging portals, creating change sets, testing apps in dev accounts, or deploying templated sets of data to multiple portals.

 

Important Notes - HubSpot Portal Toolkit

 

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 large 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. 

 

The "Rollup" type of custom calculation properties cannot be created via the HubSpot APIS, and because of this our application cannot migrate them.

 

The "Property Sync" type of custom properties cannot be migrated or replicated via the HubSpot APIS due to deficiencies in how the HubSpot APIS return information about this property type.

 

Custom Call/Meeting types cannot be migrated due to API limitations. However if the Custom Call/Meeting types from the source portal are created in the destination portal prior to running the migrator the data will map correctly to those Custom Call/Meeting types.

 

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.

 

Setup and Activation

 

 

HubSpot Portal Sync

Important Notes - HubSpot Portal Sync

 

During the sync process, users in the Target HubSpot may have relevant data associated with them. In this process, unless otherwise configured in the HubSpot portal itself, the user can potentially receive 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 inform your users of the email notifications. You can see how to change your notifications here https://knowledge.hubspot.com/settings/how-to-set-up-user-notifications-in-hubspot.

 

Do not feel the need to re-create custom properties or pipelines before initiating the sync, the tool will do that for you and if you attempt to do it yourself first you may experience errors during the sync process. 

 

The "Rollup" type of custom calculation properties cannot be created via the HubSpot APIS, and because of this our application cannot sync them.

 

The "Property Sync" type of custom properties cannot be migrated or replicated via the HubSpot APIS due to deficiencies in how the HubSpot APIS return information about this property type.

 

Custom Call/Meeting types cannot be synced due to API limitations. However if the Custom Call/Meeting types from the source portal are created in the destination portal at any point during the sync the data will map correctly to those Custom Call/Meeting types.

 

If you are using a currency in the Source portal please make sure that same currency is enabled in the destination portal. Otherwise certain pieces of data may fail to sync. 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 sync those records will fail to sync.

Setup and Activation

 

 

HubSpot Beta APIs

This app utilizes the following beta APIs

 

• Workflows

 

The ability to replicate and migrate Workflows is powered by the beta API listed below. 

https://developers.hubspot.com/docs/api/automation/workflows 

 

To read more about Beta APIS and their inclusion in our service please visit this page.

 

How to Uninstall the App

*Do not perform these step until you are done using the Portal Migration Suite.

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.

 

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

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

 

 

App Functions

 

Object Type	Process	Errors, Duplicates, and Conditions
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. The application creates owners/users from the source portal as View Only users in the destination portal if they do not already exist in the destination. It does not create or consume HubSpot seats and will not cause a billing event to occur.	If the user already exists in the Target Portal, the Source user will not be created. Users that have failed to be created for any reason will be logged. 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.	If the exact same folder path already exists, then the folder will not be created. Folders that have failed to be created for any reasons will be logged. Product Folders, and Forms folders are not migrated due to API Limitations.
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.	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 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. Files names with special characters may fail to migrate due to API limitations. 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.	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. Internal name does not match then it will create a new value or fail to migrate that property/value The following property settings cannot be migrated due to API limitations. Set min character limit, Set max character limit, Restrict to numeric values, Don't allow special characters, Show in search results. Custom Properties that have failed to be migrated for any reason will be logged. 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. Properties flagged as "Sensitive Data" will not be migrated. If Business Units are enabled in the destination portal all properties created by the app will be assigned to the default business unit due to HubSpot API limitations. The "Property Sync" type of custom properties cannot be migrated or replicated via the HubSpot APIS due to deficiencies in how the HubSpot APIS return information about this property type.
Pipelines	Pipelines from Deals, and Tickets will be transferred from the Source HubSpot to the Target HubSpot.    With the Pro, Enterprise, Portal Toolkit, and Portal Sync versions of the app you can filter which pipelines you want to migrate from the source and the app will only migrate those pipelines and the deals within them.	Pipelines that have failed to be created for any reasons will be logged. If a pipeline has the same name it will be merged. If you use the standard deal pipeline with the internal name "default" when migrating it will merge with the pipeline with the "default" internal name in the destination even if the label of the pipeline is different.
Deals	Deals from the Source HubSpot portal will be transferred over to the Target HubSpot portal. All associations to other objects will be retained.	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. 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.	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. Any Product that fails to be created for any reason will be logged. Product Folders are not migrated due to HubSpot API Limitations.
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.	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. 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.	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. 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.	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. Companies that do not contain the same Domain Name, but have the same Company name will not be merged. This may result in duplicates. Any Company that fails to be created for any reason will be logged. Lifecycle stage will migrate, but custom stages that do not already exist in the target, will be appended to the end of the lifecycle stage display order. As a result the display order of lifecycle changes may change.
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 migrate, but will not merge into any existing contact in the destination. 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.	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. Any Contact that fails to be created for any reason will be logged. "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. Lifecycle stage will migrate, but custom stages that do not already exist in the target, will be appended to the end of the lifecycle stage display order. As a result the display order of lifecycle changes may change.
Lists	Active and Static Lists will migrate from the Source to the Target Portal. This includes Contact Lists, Deal Lists, Company Lists, and Custom Object Lists	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. Active lists that are built with a filter referencing marketing emails will not migrate. This is because we cannot migrate marketing emails. Active lists that reference objects/records that we cannot migrate will not be migrated. The migrator will create a list of all contacts migrated from the source portal. List Folders are not migrated currently. Custom list properties assignment's to lists are not migrated due to HubSpot API limitations.
Forms (Legacy Schemas Only)	All Legacy Form types will migrate from the source to the target portal. There is a new Beta form builder available in HubSpot as of 8/1/2024 and forms created by this beta are not supported at this time.   No form submissions are migrated. We only migrate the form setup.	Forms are matched on an exact name match. If a form already exists it will be updated. If it does not exist it will be created. Assigned campaign is not migrated. The Form Submission notification setting is only migrated if the owner/team was migrated or if it already exists in the destination If a form is assigned to the default BU part of a Enterprise migration or Schema Replication and you want to assign it to a different BU you will need to clone the form in the HubSpot UI and assign it to the BU you wish to associate the form with. Forms Folders are not migrated due to HubSpot API Limitations.
Engagements (Notes, Meetings, Tasks, Emails, Calls, SMS, Postal Mail)	All Engagements related to Contacts, Companies, Deals, and Tickets will migrate from the source to the Target Portal.	Campaign Emails do not migrate due to HubSpot API Limitations. Comments on engagements cannot currently be migrated due to HubSpot API limitations. Custom Call/Meeting types cannot be migrated due to API limitations. However if the Custom Call/Meeting types from the source portal are created in the destination portal prior to running the migrator the data will map correctly to those Custom Call/Meeting types. Call recordings are migrated if the call was made and recorded natively in HubSpot. Call recordings stored in third party apps are not migrated.
Custom Objects	All Custom Objects Schemas, Properties, Data, and Associations will migrate from the Source to the Target portal.	HubSpot as of 2/01/2024 has a maximum limit of 20 total custom objects schemas per HubSpot Portal. Our application cannot breach these limits. As an example if the source portal has 15 custom object schemas, and the destination portal has 7 custom object schemas, only 13 custom object schemas from the source will be migrated. The remainder will be ignored. 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. If the internal ids of custom objects do not match in the source and destination portal, but the labels match, that Custom Object will fail to migrate. The Object Labels and Internal IDS of custom objects must both match for custom objects to migrate and merge. Any Custom Object that fails to migrate for any reason will be logged.
Business Units	With the Enterprise, Portal Toolkit, and Portal Sync versions of the app you can filter which business units you wish to migrate from and too.   Business Units themselves are not migrated as it is not possible to create a new Business Unit via APIs.	You can only select one Business Unit to migrate to and/or from in a single migration run. Any Business Unit assignment that fails to migrate for any reason will be logged.
Currencies	Currency settings are replicated from the source into the destination portal.    If we are unable to migrate currencies this does not affect the integrity of your data.	Multi-currency must be enabled in HubSpot for currencies migration to work. If the currency we create does not have an exchange rate already applied to it we will set the default exchange rate for that currency to "1". Existing currencies with exchange rates will not be updated.
Associations	Associations between records will migrate as will association labels.	Association rules that limit the quantity of record associations in the target portal, may affect how many associations can be created. If you have limited associations between objects to a certain number of associations and the migration results in those limits being hit, excess associations will fail to migrate. Association rules that limit the quantity of record associations per association type will not migrate due to HubSpot API limitations and potential conflict with the destination portals settings. Any association assignment that fails to migrate for any reason will be logged.

 

 

Properties Migration Details

The internal ID of properties is used as the key to map properties. 

 

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 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/Internal Id Match	*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/Internal Id Match	Property will fail to migrate If the API name is the exact same in the Source and Destination portals but the Type is different.
True	True	Different Label, Same Type / Internal Id match	Label change will be migrated. The rest of the data will be migrated normally. *Example* If the Picklist property is named Industry in the source, and Vertical in the destination but the internal name matches, the Property Label will be renamed to Industry. The picklist options are merged to a single list covering all options in both Portals.
True	True	Same Label, Same Type / Internal Id Mismatch	Property will fail to migrate, because we cannot create a property with the same unique label twice.
True	True	Same Label, Same Type/ Internal Id Match/ Property in destination is archived	Property will fail to migrate, if the mapped property in the destination portal is in the archived properties section. To resolve and allow for this property to migrate, either delete the archived property or restore it.