.svg)
Yes, you can test a migration to a HubSpot Sandbox account before executing the full migration to your production environment. This is a helpful step for testing and validating your setup. However, there are a few important limitations to keep in mind:
1. Migration Setup Is Fixed per Environment
Once you configure a migration, you cannot switch the source or target portal within that same setup. This means that after completing your Sandbox testing, you’ll need to create a new migration for your production portal.
2. Connect Your Production Portal First
There is no backward sync from HubSpot Sandbox to the production portal—so changes made in Sandbox won’t reflect in production. Therefore, we recommend setting up a migration to your production portal first in order to create any custom fields through the mapping UI. After that, you can mirror your Production portal into a Sandbox environment and set up a new migration to Sandbox.
3. Mapping Cannot Be Shared Between Migrations
The migration wizard does not allow direct transfer of mapping configurations between different migrations. You have two options:
-
Recreate the mapping manually in your migration to Sandbox;
-
Get help from our support team to transfer the mappings for you. This process typically takes about one technical hour and may involve an additional cost.
4. Multibrand Setup Not Supported in Sandbox
If your production environment uses a multibrand setup, please note that HubSpot Sandbox does not support this configuration. As a result, you'll only be able to test the migration to a specific brand in the production migration. To learn how to assign records to a specific brand during migration to production HubSpot, check out this article.