> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/knowledge-base/how-to-articles/migrate-users-to-another-authentication-provider.md).

# Migrate users to another authentication provider

These instructions explain how to migrate the user accounts and user groups from one authentication provider to another. Here are the providers available for migration:

* ***Domain***
* ***Microsoft***
* ***Okta***
* ***PingOne***
* ***Devolutions Server*** (can only be migrated **from**)
* ***SQL server*** (can only be migrated **from**)

All the providers listed above can be migrated to—and from—one another, with the exception of SQL server and Devolutions Server, which cannot be migrated to.

The tool can be found in three locations on the web interface of your Devolutions Server instance:

* ***Administration*** – ***Server settings*** – ***Authentication***
* ***Administration*** – ***Users***
* ***Administration*** – ***User groups***

{% hint style="info" %}
To migrate users and user groups to the same Identity provider (for example: Active Directory to another Active Directory), the information under ***Administration*** – ***Server settings*** – ***Authentication*** must be changed to the new domain before using the authentication migration tool.
{% endhint %}

### Migration steps

1. As mentioned in the ***Introduction***, important operations are required before going through this process. Click ***Next***.

   ![](https://cdnweb.devolutions.net/docs/docs_en_kb_KB8124.png)
2. In the ***Options***, select the source and the destination of the migration.

   ![](https://cdnweb.devolutions.net/docs/docs_en_kb_KB8125.png)
3. In the ***Users mapping***, the wizard should automatically match the accounts that are similar. The other accounts will need to be selected manually.

   ![](https://cdnweb.devolutions.net/docs/docs_en_kb_KB8126.png)
4. In the ***User groups mapping*** some groups will also be matched automatically by the wizard, the rest will have to be done manually.

   ![](https://cdnweb.devolutions.net/docs/docs_en_kb_KB8127.png)
5. The ***Confirmation*** shows the number of selected users, user groups and the ones that are not selected for the migration process.

   ![](https://cdnweb.devolutions.net/docs/docs_en_kb_KB8128.png)
6. Click on the ***Start migration*** button to start the process and get the migration confirmation report.

   ![](https://cdnweb.devolutions.net/docs/docs_en_kb_KB8129.png)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/server/knowledge-base/how-to-articles/migrate-users-to-another-authentication-provider.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
