Skip to main content
Migration

Migration steps

Move your Rownd users, sessions, and compatible authentication flows to SuperTokens without any breaking changes

Overview

Before going into the migration flow, you need to understand how the Rownd and SuperTokens architectures differ. Unlike with other providers, the SuperTokens Client SDKs never talk to the Authentication Service directly. All the requests target your existing backend where you integrate our server SDKs. Those in turn expose the authentication routes and communicate with the SuperTokens Core service which provides user and session storage.

Compared to Rownd, in SuperTokens you have to:

  • Integrate a separate backend SDK into your application
  • Configure authentication methods and customizations through code configuration passed to the SDKs
  • Setup a separate backend plugin that ensures compatibility between the legacy Rownd APIs and the SuperTokens functionality

Migration steps

Each step of the migration process requires an existing SuperTokens backend integration in your application. The following steps give you an overview over the process. For detailed instructions on how to integrate SDKs you can read the full guide.

The migration flow is not designed to be self service. Please get in touch with the SuperTokens team for assistance during the whole process.

1. Lazy migration

Update your existing Rownd client libraries to the latest version. With this you will enable the following behavior: after a successful sign-up, the SDK will call the migration endpoint exposed by the compatibility plugin. This phase ensures that no users are missed during the bulk migration flow. This is necessary since there is a time gap between when you export all your data for bulk import and when you go live with SuperTokens.

2. Bulk migration

This step is performed by the SuperTokens team. Once you have deployed the updated Rownd client libraries and confirmed that the migration works, you can start the next step. The migration will copy all your existing users from the Rownd account to the newly created SuperTokens core instance.

3. Cutover

Replace the Rownd client SDKs with the SuperTokens Rownd-compatible clients. The SDK integration guide goes into detail on how to do this. After cutover, authentication traffic goes through SuperTokens while your application uses Rownd-compatible APIs.

Compatibility model

The migration is designed to preserve the Rownd-facing integration surface where possible. Frontend APIs such as requestSignIn(), signOut(), getAccessToken(), profile management, and signed-in state continue to be exposed by the SuperTokens Rownd SDKs. Authentication UIs are preserved as well as the Rownd specific session claims.

Next steps

Continue with the SDK Integration Guide. The backend plugin must be deployed before clients can migrate sessions or use SuperTokens-backed Rownd flows.

After the backend is working, use the same guide to configure your frontend or mobile client platform.