Last updated: December 16, 2025
Available with any of the following subscriptions, except where noted:
If you have a HubSpot account, you can migrate your data to one of HubSpot’s other data centers. HubSpot supports two types of data migrations: opt-in migrations that you initiate yourself, and automatic migrations that HubSpot schedules on your behalf.
- Opt-in migrations: after reviewing the requirements, logistics, and impact of the data migration tool, you can initiate and schedule the migration directly from your HubSpot account. There may be some required post-migration actions to take depending on the tools and features you're using.
- Automatic migrations: in some situations, HubSpot may determine that your account is a better fit for a different data hosting location to improve performance. In these cases, HubSpot will automatically schedule a migration for your account. All Super Admins will receive a notification about the migration 30 days in advance. You may cancel the migration or reschedule it.
If anything unexpected occurs during or after the migration, contact support.
Review the answers to some Frequently Asked Questions about migration.
Super Admin permissions are required to initiate, reschedule, or cancel a migration.
Before you get started
Please note the following limitations & considerations, which may apply to all types of data migrations, whether scheduled by you or automatically scheduled by HubSpot:
Data center locations
See the HubSpot Cloud Infrastructure and Data Hosting | Frequently Asked Questions article to understand where Customer Data will be hosted by HubSpot.
Understand limitations & considerations
- Data migrations usually take about 24 hours but can take up to 36 hours. Your HubSpot account will be unavailable to all users during that time.
- Data migrations must be scheduled on an available date at least one week in advance.
- A migration can be canceled up to 36 hours before it's due to begin.
- You can only migrate data from HubSpot’s U.S. East Coast data center (United States (East)) to another data center, not vice versa. E.g., you aren't able to migrate from HubSpot's EU data center to another data center.
- If you use single-sign on (SSO) (Enterprise only), you'll be automatically redirected to the new data center location after migration and no further action is required.
Understand cancellations
HubSpot will cancel an account’s migration if your account doesn’t meet the technical or product requirements needed to complete the move. Super Admins will receive an email notification if the migration is canceled.
Depending on whether you opted in to the migration or your account was selected for automatic migration, different conditions can prevent the process from continuing. Review the sections below to learn why your migration may be canceled and what steps you can take to move forward.
Opt-in or automatic migrations cancellation reasons
- HubSpot payments: you can only migrate to a non-U.S. data center if you have no transactions or test transactions. A Super Admin must contact support to turn off the payments feature if you want to schedule a data migration to a non-U.S. data center. Any active subscriptions will be canceled, and links you've set up will be turned off. Payments that are in progress (i.e., ACH) will be processed, but won’t update to your HubSpot account. To collect payments after migrating, you'll need to set up a payment option again. However, you won't be able to read past payment data.
- Stripe: if you have set up Stripe as a payment processing option in your account, you can only migrate if you have no transactions or test transactions. You must disconnect the Stripe migration. After you migrate, your historical payment data will be available as read-only.
- Sensitive Data: if you have Sensitive Data turned on and haven't stated the storage of HIPAA data, you can migrate your account.
- HIPPA data: if you’re storing HIPPA data, you can't migrate to another data center. To schedule the migration, you must edit your Sensitive Data settings to indicate that you aren’t storing HIPPA data.
- Microsoft Teams and Zoom integrations: if you’re using the Microsoft Teams or Zoom integrations, they need to be connected to one account. This needs to be done before you can schedule the migration.
- Billing changes: if your billing date changes after your migration is scheduled, the dates may conflict. If your migration is canceled for this reason, you must reschedule your migration for a different date.
Automatic migrations cancellation reasons
If HubSpot determines that your account is a better fit for another data hosting location, but any of the conditions below apply, your migration will be canceled to prevent business disruption. Super Admins can opt the account back in after reviewing the cancellation reason.
- Sandboxes: sandboxes can’t be migrated, and you'll lose any work done in the sandbox after migrating. You’ll need to create a new sandbox after migration is complete.
- Snowflake integration: the Snowflake integration can’t be migrated. It must be uninstalled and reinstalled after migration.
- Dedicated IP address: dedicated IP addresses can’t be migrated. You must reconnect them after migration.
Impact to HubSpot tools
All information in your HubSpot account including historical data will be migrated over to the new data center. Take note of the impact to the following tools, especially impact during downtime that'll require further action after the date migration:
| Tool |
Impact to tool |
| Account and object IDs |
Your HubSpot account and object record IDs will remain the same after the migration is complete. |
| Ads |
Any ad scheduled to go live during the data migration will go live at the scheduled time. Any data coming into HubSpot from a connected ad account (Facebook, LinkedIn, Google) during the migration will be processed when the data migration is complete. |
| API calls |
Any API calls made to your HubSpot account from integrations will fail during the migration. If a call is made during migration, HubSpot will return a 477 status code. After the data migration, API calls may or may not be retried depending on the app or integration that the API call originates from. HubSpot doesn't have visibility into whether an API call will be retried. |
| Authentication & secrets |
API authentication primarily works via OAuth. After the migration the OAuth flow will automatically take care of refreshing access credentials. |
| Calling |
Outbound calling: outbound calls initiated directly from a HubSpot account will be dropped once the migration starts. Outbound calls initiated from HubSpot but done through a phone won't be dropped. Inbound calling: inbound calls won't connect during the migration. HubSpot will play the standard message that would play whenever you can’t be reached. All existing call data and recordings will be migrated to the new HubSpot data hosting location. All future call data and activity will take place on the new data hosting location. Please note: Twilio keeps a record of HubSpot customers' phone numbers on their U.S. servers. |
| Chatbots |
Chatbots will be unavailable and hidden from website visitors beginning one hour before a data migration. Chatbots will be available for new messages when the migration is complete. If a customer has started a conversation with a chatbot before the migration starts, they’ll be able to finish it, but if the chat writes information to HubSpot, that will fail. |
| Customer portal |
Your customers will be able to create new tickets and view existing tickets. They will not be able to respond to or send new messages. If they try to respond to an existing message, they will see the following error: Unable to send message while system is undergoing scheduled maintenance. Check back later. |
| Custom and third-party integrations |
During migration, custom and third-party integrations will not sync with your HubSpot account. After the data migration, API calls may or may not be retried depending on the app or integration that the API call originates from. HubSpot does not have visibility into whether an API call will be retried. |
| CRM imports |
Imports will be unavailable 24 hours before your scheduled migration date. |
| CTAs |
CTAs will be available during the migration and will track activity. CTA analytics won't be accessible during the migration. |
| Data sync |
All syncing activity will be paused during the migration. After the migration, all syncing activity will resume normally. |
| Documents |
During the migration, documents will not be visible to any users. Users will see the error: This document is temporarily unavailable because of scheduled system updates. It’ll be available again on [date migration ends]. |
| Domains |
|
| Marketing Emails |
Once a data migration is scheduled, bulk marketing email sends can't be scheduled that day. Marketing emails scheduled to go out during a data migration won’t be sent and will need to be rescheduled when the migration is complete. Incoming emails will be received, but workflow triggers, RSS emails, forms, follow-up emails, and other email-based automation will be paused until the migration is complete. |
| Facebook Messenger integration |
Service reps will still be able to respond to incoming messages sent via Facebook Messenger or non-HubSpot email accounts. |
| Feedback surveys |
Feedback surveys will still be able to collect submissions, but they won’t be available until after the migration. Reminder emails scheduled for the day of the migration won't be sent, and will need rescheduling. All submission-based automation will also be paused until the migration is complete. |
| Forms |
Forms will still be able to collect submissions, but they won’t be available until after the migration. All submission-based automation will also be paused until the migration is complete. Anyone who submits a form during this time will see the following message: Your response was submitted. Due to system maintenance work, it might take up to a day to finish processing. |
| HubSpot-built integrations |
For most HubSpot-built integrations, data won't sync during the data migration. Data will sync after the integration is complete. Please review exceptions for the Microsoft Teams, Zoom, and Snowflake integrations below: Microsoft Teams: If your Microsoft Teams account is currently connected to multiple HubSpot accounts, all of those HubSpot accounts must be in the same data hosting location. If you want to keep your Microsoft Teams account connected to multiple HubSpot accounts, you must either migrate all or none of the accounts to the new data hosting location. If you only migrate one connected HubSpot account, Microsoft Teams will be disconnected from all accounts until:
Zoom: If your Zoom account is currently connected to multiple HubSpot accounts, all of those HubSpot accounts must be in the same data hosting location. If you want to keep your Zoom account connected to multiple HubSpot accounts, you must either migrate all or none of the accounts to the new data hosting location. If you only migrate one connected HubSpot account, Zoom will be disconnected from all accounts until:
Snowflake: After the migration is done, you'll need to uninstall and immediately reinstall and set up your Snowflake integration. Data captured before, during, and after migration will be available in the integration once it's reinstalled. Please note: depending on where your Snowflake account is located, you may experience a different syncing rate after migration. If your Snowflake account is in the same data center as your HubSpot account, the integration will sync data every 15 minutes. If they’re not in the same location, the integration will sync data daily. |
| Knowledge base |
Your knowledge base will be available to all visitors during the data migration. |
| Landing and website pages |
Website and landing pages will be available to all visitors during the migration, but users will be unable to make changes until the migration is complete. Page views and analytics will still be recorded, but they won’t be available until the migration is complete. The existing pages will continue to be hosted on the previous system for a limited amount of time, so if you modify the pages, you'll need to select a new domain. When you change a page to a new system domain, there won't be an automatic redirect. When a website or landing page is created in HubSpot but lives on a third-party website (e.g. Squarespace, Hostinger), you have to update the page's web address in the third-party site after moving it. The data migration changes the web address, which will cause links to that page to break due to there being no automatic redirect. See the Domains section in the table. |
| Live chat |
All live chat widgets will be unavailable and hidden from website visitors beginning one hour before a data migration. Live chat widgets will be available for new messages when the migration is complete. |
| Meeting links |
During migration, meeting links will go into offline mode. Meetings can still be requested via your link, but they won't be automatically added to your calendar. After the migration, you'll receive an email for any requested meetings. Please note: the meeting link owner will need to manually send meeting invites for the requested meetings. |
| Notifications |
Sidebar notifications won't be migrated. These notifications typically expire after 30 days. |
| Private apps |
Your private app will stay the same after the migration is complete. |
| Public apps |
Public app authorization isn't impacted by migration. Authorization URLs should still be shared at the app.hubspot.com URL. |
| Quotes |
If a quote requires multiple signatures, and isn't complete, the count of signatures will reset to zero after the migration. All signers will need to resign the quote after the migration. |
| Sales Emails |
1:1 emails will be sent after the migration is complete. |
| Sandboxes |
Sandboxes won't be migrated. You can create a new sandbox when migration is complete, however, you won't be able to access anything in the previous sandbox. |
| Sequences |
Sequences will be paused during a data migration, but contacts can still unenroll by responding to an email. Emails scheduled to be sent during the migration will go out as soon as it’s complete. All other emails in the sequences will send as scheduled. |
| Social tools |
Any social posts scheduled to be published during the migration will be published after the migration is complete. You'll still be able to schedule social posts during the weekend of your migration. If you need to have a post published during the migration weekend, you can publish it using the individual social tool rather than through HubSpot. If you publish directly, make sure to delete the HubSpot-scheduled post so you don’t have duplicate posts. |
| Tickets |
Tickets created through the chatbot won't be available during the migration. Tickets created through email will be created after the migration is over. Tickets created through the ticket form will be processed after the migration. |
| Videos |
If a video is embedded from the file manager, you won't be able to play it until you select a new domain if the existing page was initially hosted on a system domain. |
| Webhooks from HubSpot |
Webhooks from HubSpot to another system wouldn't be sent during the time of migration. Post-migration, they should continue to send, but it's recommended to review your webhook configuration. |
| Workflows |
Workflows will be paused, but any delayed actions will be triggered as soon as the migration is complete. All other workflow actions will resume as scheduled. |
Opt-in and schedule a data migration
- In your HubSpot account, click the settings icon in the top navigation bar.
- Click Account Defaults.
- Click the Data hosting tab.
- The HubSpot data center where your account’s data is currently hosted is shown under Your Data hosting location.
- Click Change to start the migration process.
- Click the New data hosting location dropdown menu and select a location.
- Click the Migration date dropdown menu and select a migration date.
Please note: the following may influence what dates you're able to select:
- The date must be at least one week in advance.
- You can't schedule a migration three days before, or after your bill date.
- There is a limit to the number of migrations that can be carried out for all HubSpot customers. If no dates are available, the maximum number of migrations may have been reached.
- Select the Confirm migration checkbox.
- Click Schedule data migration.
The migration date and new location will be displayed on the Data Hosting tab.
Your account will be unavailable for up to 36 hours during the migration. If a user tries to access their account during this time, they will see the following message:
Data Migration in Progress
Your HubSpot account data is moving to the [data center location]. Your account will be unavailable until [date] at [time and time zone]. If you have any questions, contact [super admin name].
All Super Admins in the account will receive four email notifications about the scheduled migration:
- After the migration has been scheduled.
- The Monday of the week that the migration is scheduled for.
- The day before the migration is scheduled for.
- After the data migration is complete.
They'll also receive an email notification if the data migration fails.
Cancel and reschedule a data migration
- In your HubSpot account, click the settings icon in the top navigation bar.
- Click Account Defaults.
- Click the Data Hosting tab.
- Under Your HubSpot account is scheduled to move to a new data hosting location, click Actions, then select:
- Reschedule to reschedule a data migration. In the dialog box, select a date for the data migration and click Reschedule. Migrations must be scheduled at least one week in advance.
- Cancel to cancel a data migration. In the dialog box, click Yes, cancel data migration.
Post-migration checklist
When a data migration is scheduled by you, the following post-migration actions are required to fully configure your account in the new data center. For migrations initiated by HubSpot, these actions are optional, but reviewing them is recommended if you want to confirm everything is working as expected.
Items that require immediate attention post migration
| Action needed | Description |
| Reinstall HubSpot-built integration |
Snowflake If you use the Snowflake data share functionality, you'll need to uninstall and immediately reinstall and set up your Snowflake integration. Data captured before, during, and after migration will be available in the integration once it's reinstalled. Please note: depending on where your Snowflake account is located, you may experience a different syncing rate after migration. If your Snowflake account is in the same data center as your HubSpot account, the integration will sync data every 15 minutes. If they’re not in the same location, the integration will sync data daily. |
Other items that need attention post migration
| Action needed | Description |
| Connect dedicated IP address |
Connect a dedicated IP address for sending transactional and or marketing emails in your domain settings. Without taking this step, your emails will send with a shared IP address. |
| Update SMTP hostname and SMTP port |
If you use the SMTP API for transactional emails, update the SMTP hostname and SMTP port. Without this step, emails will pass through the original data hosting location before being processed in the new data hosting location. |
| Review changes to user accounts after data migration |
Notification sounds reset to default Notification sound preferences for each user have defaulted to playing a sound for notification pop-ups. Users can change preferences in their notification settings. Browser notifications turned off Browser notifications for each user have defaulted to being off. Users can change preferences in their notification settings. Meeting links may have been updated If a user’s meeting link wasn’t available in the new data hosting location, they are automatically assigned a new one. Users can change their scheduling page URL in their scheduling settings. |
| Update BCC and forwarding email address |
Your BCC and forwarding email addresses for manually logging emails in HubSpot will be different after the migration. Follow the steps here to copy and set up your new BCC and forwarding email addresses. |
| Update the form embed code |
If you use forms on your non-HubSpot website, you'll have to update the form embed code. Without taking this step, forms are still functional and data will be stored in the new data hosting location but will continue to pass through the old data hosting location. Either update the embed code, or work with your web developers to ensure they're updated. Learn more about HubSpot forms on external sites. |
| Update the call-to-action embed code |
If you embed CTAs on your non-HubSpot website, you'll have to update the CTA embed code. Learn more about CTAs on external sites. |
| Update the HS-scripts embed code |
If your non-HubSpot website has any HS-scripts, follow the links under Update the HS-scripts embed code section to obtain new embed codes. If you don't update the embed codes, data will continue to pass through the old data location and you may experience delays with your landing page, website, and forms. The embed codes that need upating are:
|
| Update the HS-scripts embed code on WordPress |
Log into your WordPress site and follow the prompts to update the HS-scripts embed code. Without using new embed codes, data will continue to pass through the old data location, and you may experience delays with your landing page, website, and/or forms. |
