# Overview

Get a high-level overview of the migration process.

The **Migration** section covers instructions on how you can move your authentication data from your current authentication solution to **SuperTokens**.

* * *

## [Before You Start](/content/docs/migration/overview#before-you-start/index.html)

The migration steps are intended to be executed after you have configured your [initial **SuperTokens** integration](/content/docs/quickstart/index.html). Hence, to complete any of the next instructions you will need the following:

- An existing application that has a working **SuperTokens** integration. You can follow the [quickstart guide](/content/docs/quickstart/index.html) for instructions on how to achieve this.
- A **SuperTokens** managed service account or a self-hosted **SuperTokens Core** instance. More specifically, you will have to make HTTP requests to your `CORE_API_ENDPOINT` using an `API_KEY`.

## [Migration Steps](/content/docs/migration/overview#migration-steps/index.html)

The entire migration process can be broken down into two steps. Both are required to achieve a seamless transition.

1. [**Account Migration**](/content/docs/migration/account-migration/index.html)

This is the main part of the migration flow. You will be importing your users, together with their account credentials, from the legacy authentication provider into **SuperTokens**.

2. [**Session Migration**](/content/docs/migration/session-migration/index.html)

This step prevents any users with active sessions from experiencing authentication issues. You will extend the **SuperTokens** functionality to create new sessions for users that have authenticated using your legacy provider.

With that in mind, you can now move to the first step, the [**Account Migration**](/content/docs/migration/account-migration/index.html) process.
