Multi Account Migration
How to migrate resources from one account to another, on the same system or a different system
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.
Export resources from an individual BindPlane OP account and import them into another account on the same system or a different BindPlane OP system.
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.
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
- 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.
1bindplane profile set "export" \ 2 --server-url "http://192.168.1.9:3001" \ 3 --api-key "xxxx-xxxx-xxxx-xxxx-xxxxxx"
1bindplane profile set "import" \ 2 --server-url "http://192.168.1.10:3001" \ 3 --api-key "xxxx-xxxx-xxxx-xxxx-xxxxxx"
Replace the values for the remote URL and API key with your BindPlane OP server remote URL(s) and API keys.
Switch to the
1bindplane profile use "export"
Export destinations, sources, processors, and configurations from the account:
1touch migration-resources.yaml 2bindplane get destination -o yaml --export > "migration-resources.yaml" 3bindplane get source -o yaml --export >> "migration-resources.yaml" 4bindplane get processor -o yaml --export >> "migration-resources.yaml" 5bindplane get configuration -o yaml --export >> "migration-resources.yaml"
Switch to the
1bindplane profile use "import"
Import destinations, sources, processors, and configurations using the apply command:
1bindplane apply -f "migration-resources.yaml"
Log into the BindPlane OP account and ensure the configurations and destinations are present. If everything looks right, the migration is finished.
Previously connected agents will need to be updated with the new account's secret key. Follow the Migrate Agents documentation.