Multi Account Migration
How to migrate resources from one account to another, on the same system or a different system
Multi Account
Multi-Account BindPlane is an Enterprise feature that allows users to create multiple tenants (accounts). Each account can have its own users, configurations, and managed agents. Multi-Account supports user invitations in order to support collaboration between multiple users.
Objective
Export resources from an individual BindPlane OP account and import them into another account on the same system or a different BindPlane OP system.
Prerequisites
The following requirements must be met:
- You are running BindPlane OP Enterprise. See Upgrade to BindPlane OP Enterprise.
- BindPlane OP v1.25.0 or newer. If on an older version, upgrade before attempting a migration.
- BindPlane OP is configured with multi-account enabled.
Procedure
The migration procedure has the following steps:
- Create API Keys
- Configure BindPlane CLI profiles
- Export resources from an account
- Import resources to the new account
- Validate
- Migrate Agents
Create API Keys
Following the API Keys documentation, create an API key for your source and destination accounts. We are going to refer to them as "export" and "import".
Note the API keys, but do not create their profiles. Follow the next section for profile instructions.
Configure CLI Profiles
Configure your BindPlane CLI with two profiles. One for the source account and server, and another for the target account and server.
Create export
profile:
Create the import
profile:
Replace the values for the remote URL and API key with your BindPlane OP server remote URL(s) and API keys.
Export Resources
Switch to the export
profile:
Export destinations, sources, processors, and configurations from the account:
Import Resources
Switch to the import
profile:
Import destinations, sources, processors, and configurations using the apply command:
Validate
Log into the BindPlane OP account and ensure the configurations and destinations are present. If everything looks right, the migration is finished.
Migrate Agents
Previously connected agents will need to be updated with the new account's secret key. Follow the Migrate Agents documentation.