Migrating to Web3Auth advice

Help - Plug n Play
1

Hello, we are currently planning a migration from our current auth + wallet creation / linking setup to Web3Auth and are looking for any advice or tips on this journey.

We use a custom built email/password authentication system and google login, as well as a wallet provider for creating or connect wallets for our users. We have a mixture of users, some are crypto natives who have connected their own external wallets and other are not crypto savvy and have had a wallet created for them.

Our current plan goes a little like this:

  • When we transition to Web3Auth, we will link existing users records with the new user/wallet created by Web3Auth, on our backend.
  • After that, we will create a tool/function to transfer assets and funds from the user’s old wallet to their new web3auth wallet.
  • Users using their own custodial wallet are not affected and simply connect their wallet again and login.

In general, does this sound right? Are we missing anything?

Thank you

2

Hi @benjamin.groves,

Thank you for selecting web3auth for your project. I have reviewed your migration plans and they appear to be in order. However, I wanted to inform you that if you plan to use custom-built email/passwordless authentication, you will need to include the JWT token steps outlined here. Aside from this minor adjustment, you should be all set to proceed with the web3auth migration.

I am eagerly anticipating updates on the progress.

3

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.