Whether you use Auth0, Stytch, Cognito, Firebase, or you built a custom solution, moving to something new can seem like an overwhelming task. However, with Rownd, it’s not hard or overwhelming. We’ve made it super easy for you to migrate.
A few things to consider when leaving your current auth provider:
- The easiest part is moving the data. User profiles, emails, phone numbers, even Google IDs can be imported into Rownd. In many cases, this can even happen automatically.
- Consider keeping users signed-in through the migration—your users will love you for it. This means you’ll temporarily run two auth providers in parallel.
Let’s dig in.
Set up Rownd
The first step is to confgiure Rownd in your dev enviornment. We have a plethora of SDKs and code snippets to make this straight-forward.
Considerations when setting up Rownd
No sign-in page: Rownd is different. You won’t need a sign-in page. Simply trigger the Rownd sign-in flow from existing buttons or trigger sign-in dynamically. It’s your choice.
No difficult coding: Rownd provides all of the authentication UI out of the box, so you won’t need to build anything yourself. Applying branding, authenticaton options, and more can be configured dynamically through the Rownd platform.
Move auth where you need it: Although some customers simply replace their existing sign-in flows with Rownd, we recommend moving authentication deeper into your offering. Letting your customers experience some of your product prior to requesting registration is a great way to boost your conversion rate.
Keeping users signed-in
Rownd provides a token validator integration that can take an existing authentication token and validate it against another provider’s API or JWK endpoint. This allows users that are already signed-in to stay signed-in while Rownd issues them a new token.
Considerations for token validaiton
- The API or JWK endpoint needs to be public so Rownd can validate the token.
- Each auth provider has their own methods for validating tokens. Reach out to firstname.lastname@example.org and we’ll help you configure the provider to validate tokens to keep your users signed-in.
Setting up Google and/or Apple sign-in
Considerations for setting up Google and/or Apple sign-in
- Use the same Google Client ID that you used to set up the authentication prior to migration. This ensures the Google ID remains the same. If that’s not possible for some reason, Rownd can still automatically users based on their Google account’s email address.
- Use the same Apple App ID for both.
Migrating existing user profiles is the easiest part. If you’re migrating from another auth provider, Rownd can automatically migrate your users for you. See our provider-specific migration guides for more information.
If you’re migrating from an auth provider that Rownd doesn’t support natively, or if you’re coming from your own auth solution, reach out to us a few days before deploying to production. We’ll provide hands-on assistance to ensure your migration is smooth.
Considerations for migrating data
- Consider what data you want to transfer to Rownd. Most sign-in methods should be migrated. Rownd can also manage other profile information (names, addresses, etc).
- You may choose to migrate data from two or more sources. For example, you may move profile data from Auth0 and personal information (PII) from your own database. Let us know!
Start a migration
Choose your migration path below to get started!