Migrate to Para
Already have some users in another auth or wallet system? Para makes it easy to migrate!
Overview
Para makes it easy to migrate users and/or wallets from another system. As with any migration, there are many nuances to consider, and a variety of options for how to approach a migration. First, you’ll need to determine what type of integration you want to complete.
Migration Scope
Users Only
Users Only
New pregenerated wallets will be created for your existing users, which they can claim when they log in. Please see our GitHub repository for a sample code snippet and instructions on how to leverage pregenerated wallets.
Users & Assets
Users & Assets
In addition to creating new wallets, assets can be transferred either in a batch (if migrating from a custodial system) or just-in-time as users claim their wallet and log in. In this method, assets can be ported over, but users will receive a new wallet address with Para.
If you are following this path, please get in touch with Para as the specifics of a migration path and options vary based on your current provider.
[Experimental] Users & Wallets
[Experimental] Users & Wallets
Para can also support importing a private key if your provider offers an export private key option. Using this path, users can keep the same wallet address they currently have.
This feature is experimental and availability varies based on the provider currently being used. If you would like to follow this path, please get in touch with Para for more information and to get access.
Migration Timing
For each of these options, there are two paths to migrating:
Batch Migration
Move users over proactively. This option works best if: - You don’t have assets to migrate - You’re migrating with a smart contract account setup - You’re migrating from a custodian that has a batch export feature
Live/Just-in-time
As users onboard, migrate over their account and/or assets. This option works best if you need users to: - Sign a transaction to onboard - Take an action such as exporting a private key and importing it into Para’s system
Migrations can be tricky business! We’re here to help, please get in touch and consider us your thought partners in this process.
Migrate to Para
Already have some users in another auth or wallet system? Para makes it easy to migrate!
Overview
Para makes it easy to migrate users and/or wallets from another system. As with any migration, there are many nuances to consider, and a variety of options for how to approach a migration. First, you’ll need to determine what type of integration you want to complete.
Migration Scope
Users Only
Users Only
New pregenerated wallets will be created for your existing users, which they can claim when they log in. Please see our GitHub repository for a sample code snippet and instructions on how to leverage pregenerated wallets.
Users & Assets
Users & Assets
In addition to creating new wallets, assets can be transferred either in a batch (if migrating from a custodial system) or just-in-time as users claim their wallet and log in. In this method, assets can be ported over, but users will receive a new wallet address with Para.
If you are following this path, please get in touch with Para as the specifics of a migration path and options vary based on your current provider.
[Experimental] Users & Wallets
[Experimental] Users & Wallets
Para can also support importing a private key if your provider offers an export private key option. Using this path, users can keep the same wallet address they currently have.
This feature is experimental and availability varies based on the provider currently being used. If you would like to follow this path, please get in touch with Para for more information and to get access.
Migration Timing
For each of these options, there are two paths to migrating:
Batch Migration
Move users over proactively. This option works best if: - You don’t have assets to migrate - You’re migrating with a smart contract account setup - You’re migrating from a custodian that has a batch export feature
Live/Just-in-time
As users onboard, migrate over their account and/or assets. This option works best if you need users to: - Sign a transaction to onboard - Take an action such as exporting a private key and importing it into Para’s system
Migrations can be tricky business! We’re here to help, please get in touch and consider us your thought partners in this process.