---
title: Migrate legacy instances
description: Migrate from legacy PingAM deployments by creating a new deployment and redirecting client traffic to replace your unsupported installation
component: pingam
version: 8.1
page_id: pingam:upgrade:upgrade-legacy
canonical_url: https://docs.pingidentity.com/pingam/8.1/upgrade/upgrade-legacy.html
llms_txt: https://docs.pingidentity.com/pingam/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2026-06-01T14:11:17Z
keywords: ["Upgrade"]
page_aliases: ["upgrade-guide:upgrade-legacy.adoc"]
section_ids:
  proc-upgrade-legacy: Upgrade a legacy deployment
---

# Migrate legacy instances

Rather than upgrade legacy instances (running an [AM version that's no longer supported](https://support.pingidentity.com/s/article/Ping-Identity-EOL-Tracker#pam)), you must instead manually migrate from your existing deployment to a new deployment.

For complex legacy deployments, Ping Identity can help you with the migration process.

## Upgrade a legacy deployment

1. Prepare your customized AM `.war` file.

2. Prepare a new deployment, installing servers from the new, customized `.war` file, starting with the instructions in [Install AM](../installation/installing-instances.html).

3. After installation, configure the new servers in the same way as the old servers, adapting as necessary.

4. Validate that the new service is performing as expected.

5. Redirect client application traffic from the old deployment to the new deployment.