If you’re a customer located in the European Union (EU) or Asia Pacific region (APAC) with data stored in the United States data center, ActiveCampaign is going to migrate your data to be hosted in the appropriate regional data center, primarily based on your account billing address, immediately prior to the migration.
The maintenance window is between 12:00 a.m. and 4:00 a.m. in the account's local time zone and should take less than one hour to complete, with minimal disruption to your platform experience.
Please refer to our FAQs if you have questions about your upcoming migration. We also strongly encourage you to read our Multi-Regional Data Hosting Policy for details about what ActiveCampaign can and cannot host within a specific region.
Impact on ActiveCampaign Features and Integrations
Data in your ActiveCampaign account will undergo migration to the new regional data center based on your IP address at sign-up. Your account will be in a "maintenance" state throughout the migration process. Please be aware of the impact on the following features and integrations:
| Feature or Integration | Impact |
| Account CNAME/Domain Alias | Your domain alias will continue to work after the maintenance window, but it may take up to 30 minutes after the maintenance window for the CNAME to be updated and moved to the backend to the new region. |
|
Advertising Integrations:
|
Any data ActiveCampaign receives from connected advertising accounts (Facebook, LinkedIn, Google) during maintenance will be processed once maintenance is complete. |
| API URL | API URLs will continue to be "api-us1.com." |
| Automations | Automation activity will temporarily pause during the maintenance window and resume once the account is back online. |
|
Automation Triggers:
|
During the migration window, these automation events will be placed in a queue and processed after the maintenance is complete. |
|
Automation Triggers:
|
During account maintenance windows, automations will not trigger, active historical syncs will be stopped, and real-time data synced in will be entered into a queue. Once maintenance is complete, data syncing will AUTOMATICALLY resume - meaning any active historical syncs that were paused will be restarted, and real-time data in the queue will resume syncing, which will trigger any active automations as they would normally be expected to. |
| Campaign Sending |
Campaigns will not be sent during the migration window. You are advised to pause all Campaigns (including split campaigns) before the scheduled migration begins and refrain from sending any campaigns within 12 hours before the migration window. If a campaign is scheduled to send during the migration, your migration will be skipped and rescheduled for another day. |
| Calendly Integration | During the migration window, Calendly messages will be placed in a queue and processed after the maintenance is complete. |
| Conversations | Accounts with Conversations capability can be migrated to other data centers, with Conversations data continuing to reside in the US-East Data Center. |
|
CRM Integrations:
|
If you have with Salesforce and Microsoft Dynamics integrations will be migrated at a later date and will receive advanced notification of migration requirements. |
|
Custom Objects Triggers:
|
API requests made directly to COs (outside of CX Apps and other native integrations) will be dropped unless handled appropriately by the service making the requests. This generally means that any service using an API should account for error handling. Normally, this entails some sort of retry mechanism with exponential back-off. For this case, AC will serve 503s that the service can recognize to retry the failed requests later, ideally an hour later when it's likely the maintenance has finished and the APIs become available again. |
| Custom and Third-Party Integrations |
Custom and third-party integrations will not sync with your ActiveCampaign account during the migration window. Following the migration's completion, API calls may or may not be retried depending on the app or integration from which they originate. We suggest reviewing your API calls individually to determine if a retry is necessary. |
|
CX Apps Triggers:
|
During the migration window, Google and Calendly integration event triggers will be placed in a queue and processed after maintenance is complete. Salesforce will verify the account status before sending events. If the account is undergoing migration, the events will be queued on the Salesforce side until the account becomes active. |
| Data syncs |
Ensure all data syncs are completed at least 12 hours before the migration time. If a data sync is taking place during your maintenance window, your migration will be skipped and rescheduled for another day. |
| Data Imports, Bulk Edits, and List Clean Ups |
You are advised to avoid imports, bulk edits, and list cleanups within 12 hours before migrations to minimize potential issues. If data imports, bulk edits, or list clean-ups occur during your maintenance window, your migration will be skipped and rescheduled for another day. |
|
Deals Triggers:
Contacts Triggers:
|
The majority of Deal and Contact Triggers will not be spawned during maintenance. Triggers in these domains would not fire if inbound API calls from third parties attempted to modify them. This is because the API will respond with 5XXs, and it is on the 3P to properly handle these retries if they want to queue them for post-maintenance processing. |
| Data object and record IDs (contacts, accounts, lists, fields, etc.) | All data object and record IDs will be maintained across the migration. |
|
E-commerce integrations:
|
During account maintenance windows, automations will not trigger, active historical syncs will be stopped, and real-time data synced in will be entered into a queue. Once maintenance is complete, data syncing will automatically resume - meaning any active historical syncs that were paused will be restarted, and real-time data in the queue will resume syncing, which will trigger any active automations as they would normally be expected to. |
| Email Open and Click Reporting | During the migration window, email open and click-through reporting will be placed in a queue and processed after maintenance is complete. |
| Event Tracking | Custom event tracking will be placed in a queue during the migration window and processed after the maintenance is complete. |
| Forms | For now, we will not migrate accounts with active Forms, including any Forms that handle unsubscribes. We will implement an update that will prevent Form submissions during maintenance. |
|
Forms Triggers:
|
Forms will be offline during maintenance, and APIs for submitting embedded forms and List APIs will not be processed. This means any automations triggered by these events will never run. |
| Landing Pages | Published Landing Pages will remain available during maintenance, and landing page analytics will be tracked. |
| SSO | Account URLs won’t change after maintenance, SSO will continue working. |
| Reporting and Segmentation |
After the migration is complete, reports and segments may not immediately reflect the latest data until all queued events have been processed. Please allow up to 4 hours for the reporting and segmentation data to fully normalize after the migration is complete. |
| Sales Engagement Automation (Automated 1:1 Email) |
All automation activity will pause during the migration period and resume once the account is back online. Automated 1:1 emails will be sent upon resumption of automation as soon as the contact reaches the action block. |
| Site Tracking | During the migration window, site tracking will be placed in a queue and processed after the maintenance is complete. |
| Unsubscribes from Campaigns | During maintenance, when a contact clicks on “unsubscribe” in a Campaign, they will see a page that says to try back later, and the unsubscribe will not be recorded. |
| WordPress Plugin | Plugin setup, form embedding, and form submissions will be non-functional during migration. |
| Zapier Integration | Zap actions will cease processing during maintenance; they can be retried post-migration. |