Skip to main content

How to setup a migration from HubSpot with Import2

This is a guide on what to expect when using Import2 to complete a sample and a full migration

Written by Jessica Maron

Getting Started with Sample Migration

1. Connect your Apps

Select the app you are migrating to

2. Create account

Confirm your account by verifying it with a code sent to your inbox.

3. Connect your source and destination apps.

Connect your source and destination accounts using the secure form.

To connect HubSpot

Choose the HubSpot account that you want to migrate data from

Check the box and click “Connect app” on the connecting app screen

Permissions requested by Import2

On the “Connect app” screen HubSpot lists every permission (scope) that Import2 requests. These permissions let Import2 read the records you select and write them into the destination account. Import2 does not use them for any other purpose.

4. Configure Sample

Start the free sample migration to import a subset of your database, to see how your data actually looks in your new app! Utilize the settings available under Configuration > Objects, Field Mappings or Filters to make adjustments as needed during the sample step.

5. Validate the results

In the "Results" tab you can access links to migrated records in your destination app.

Proceeding with Full Migration

To move forward with the full migration, you may purchase from the Purchase tab of your migration. After payment is received, you will have a button to "Start Full Migration" to kick off the full migration when you are ready.

Many of our migrations are provided at no cost through our partnerships with SaaS apps. If you are migrating to one of our partners, the "Start Full Migration" will be available to you immediately after the sample and you can proceed whenever ready.

If your migration has errors, check out our guide on how to manage those here.

If you need some additional help or configuration of your migration, please reach out and we are happy to discuss our available features with you!

Disconnecting and Uninstalling

Disconnect HubSpot from Import2

To disconnect HubSpot from Import2 click “Reset Connection”

This revokes the access token Import2 holds for that HubSpot account. You can reconnect at any time by repeating the steps in Connect your source and destination apps above.

Uninstall Import2 from your Hubspot Account

Resetting the connection removes access on the Import2 side. To also remove the app from HubSpot itself:

  1. Sign in to your HubSpot account as a Super Admin.

  2. Click the settings icon in the top navigation bar.

  3. In the left sidebar menu, go to Integrations > Connected Apps.

  4. Find Import2, click Actions, then Uninstall.

  5. Type uninstall in the confirmation field and click Uninstall.

For the full instructions, see HubSpot's Knowledge Base article: Uninstall an integration in HubSpot.

We don't recommend uninstalling and reinstalling the app as a troubleshooting step. If your migration isn't behaving as expected, contact Import2 support first.

How disconnecting or uninstalling affects your account and data

  • Records that were already migrated stay where they are. Disconnecting or uninstalling does not delete, modify or roll back any records Import2 has written into the destination account, and it does not change anything in the source account.

  • Nothing is removed from your HubSpot account. Import2 does not store your records on its servers, so there is nothing on our side to delete along with the app.

  • All permissions are revoked. After uninstalling, the scopes you granted on the Connect app screen no longer apply and Import2 can neither read nor write data in that account.

  • A migration that is still running will stop. Import2 loses access immediately, so start or finish your migration before disconnecting. Records already transferred are not affected.

  • Your Import2 migration record remains so you can review what was moved. To have it archived and the stored credentials deleted, contact support or submit a data subject access request.

  • Reconnecting requires granting the permissions again.

Did this answer your question?