Migrating User Vaults Between Regions

Process to move a vault between data center regions

Overview

Occasionally a user may have a pre-existing Keeper vault tied to their organization's email address that resides in a region outside of where the subscription has been setup in. Due to GDPR compliance, Keeper can not relocate a user's vault from one region to another. For example, if a user created a vault in the US datacenter and an organization creates a subscription in which their encrypted data resides in the EU datacenter (or vice versa), Keeper can not move a vault into the other region as regions are completely isolated from one another. Instead, the user who owns the data will have to migrate their data themselves. This section is designed to help them with that migration.

Step 1: Request that the user change their vault email address.

If it's simply a matter that the vault was created with a work email address, but the data inside the vault is personal, the quickest solution is to change the email address associated with the user's vault to something other than their work email address. (For guidance on changing the email address, see the Settings section of the user vault guide). Once that's complete, the Admin can re-invite the user and they will receive the invitation to create their work vault. If the vault was created with the intention to be the work vault, but it was created in the wrong region, continue with the email change, but continue to step 2. If the data in the vault is meant to be for personal reasons no further steps required. Proceed to step 3.

Step 2: Export the Vault Data

Now that the vault has been re-associated with a new email address, the next step to migrate the data is to export the records to a .json file. For more information on this step see the Vault Export guide.

Step 3: Invite to the Enterprise

If not done already, the organization's Keeper Administrator will need to onboard the account (under the work email address) and an invitation will be sent. Create the new vault under the work email address.

Step 4: Import the Vault Data

The .json file created in step 2 will now be imported into the new vault. Follow the .json import steps from the Password Import section.