---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/servicenow-platform

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Migrate MID Servers to IPKI

# Migrate MID Servers to IPKI {#ariaid-title1}

Release version: Australia  
Updated October 21, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Move an existing MID Server that uses basic authentication to ServiceNow certificate-based IPKI authentication. Migrating a MID Server to IPKI preserves the user previously set on that MID Server.

## Before you begin

Role required: admin or agent_admin

## About this task

You can migrate more than one MID Server at a time, but only after at least one MID Server is already running on IPKI. Until then, you can select and migrate only one MID Server. After one MID Server is confirmed on IPKI, bulk migration becomes available for the rest.{#mid-migrate-basic-to-ipki__mid-migrate-basic-to-ipki-context-1}

## Procedure

1. On your instance, navigate to WorkspacesITOM Infra Services Workspace.
2. Select the MID Servers icon in the left navigation panel.
3. Select the Auth-type migration tab.
4. From the Eligible MID Server list, select the MID Server you want to migrate, and then select Migrate.  
   To migrate all MID Servers at once, select Migrate All. To migrate only specific MID Servers, select the check boxes next to them, and then select Migrate.  
   Note:  
   The Eligible MID Server list shows MID Servers that are on basic authorization. A MID Serverthat isn't validated remains in the list, but the Migrate button stays disabled for it until it's validated.
5. In the Migrate MID Server dialog, select Migrate Server.
6. Monitor the migration record until it shows a result of succeeded or failed.  
   If the migration record shows failed, read the failure detail on the record, address the cause, and start the migration again. For the messages that the MID Server logs, see [MID Server IPKI reference](https://www.servicenow.com/docs/y8r6r9IRIIegUwn6P7DeHA "Learn about configuration parameters, keystore aliases, instance-side tables, and log messages for MID Server IPKI authentication.").

   If the migration record remains in an intermediate state for more than an hour, an investigation is needed.
{#mid-migrate-basic-to-ipki__steps_pj3_x4b_zkc}

## Result

On a successful migration, the status of the MID Server changes to Certificate issued. The username and password of the MID Server are removed from config.xml, and the MID Server authenticates using IPKI.

To move a MID Server back to basic authentication, see [Revert MID Servers from IPKI to basic authentication](https://www.servicenow.com/docs/oTzrYjRMoOg3gvlYbC5t6w "Move a MID Server that uses IPKI authentication back to basic authentication by changing its configuration and restarting the service.").

*[\>]: and then