> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abbyy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate from Vantage 2.7

> Plan a migration from Vantage 2.7 self-hosted to 3.0: a fresh 3.0 install plus a data migration, not an in-place upgrade.

<Warning>
  **Vantage 3.0 uses a different deployment model than 2.7.** The ABBYY-provided Ansible playbooks and Azure CLI scripts used in 2.7 are not supported in 3.0, and the install pattern changes to a Kubernetes operator + ArgoCD. Treat a 2.7 → 3.0 transition as a fresh install of 3.0 alongside a data migration, not an in-place upgrade.
</Warning>

<Note>
  **Vantage 3.0 uses a different deployment model than 2.7 and earlier.** Previous releases required ABBYY's exact specified infrastructure, created and configured by ABBYY-provided Ansible and Azure CLI scripts. That model is not supported in 3.0:

  * You provision your own infrastructure: the Kubernetes cluster, databases, storage accounts, and key vault. ABBYY does not provide provisioning scripts, templates, or other infrastructure automation for 3.0.
  * The installer deploys Vantage Core only. Third-party software that Vantage relies on, such as ArgoCD, your service mesh and ingress controller, your secrets integration, and your monitoring stack, is installed and maintained by you, usually via Helm.
  * The documented configurations are scenarios ABBYY has tested. You can adapt your installation based on the documented examples; validating an adaptation is your responsibility.
</Note>

## Before you start

Read these first:

* [Introduction](/vantage/self-hosted/v3.0/introduction): the architecture differences between 2.7 and 3.0, including the move from ABBYY-provided Ansible and Azure CLI scripts to the operator + custom resource pattern.
* [Known Limitations](/vantage/self-hosted/v3.0/known-limitations): current constraints in 3.0, such as the SMTP path supporting only basic auth (or no auth). Confirm none of your 2.7 dependencies are affected before migrating.
* [Prerequisites](/vantage/self-hosted/v3.0/prerequisites): 3.0 introduces new infrastructure requirements, including ArgoCD, a supported service mesh and ingress controller, a secrets integration, and one database per connection-string alias listed in [Secrets and Key Vault](/vantage/self-hosted/v3.0/secrets-and-keyvault).

## Vantage 3.0 Migrator

ABBYY provides the Vantage 3.0 Migrator for customers transitioning from Vantage 2.7.x to 3.0. The 3.0 release notes track Migrator updates and are the authoritative reference for the migration path between 2.7 and 3.0.

<Card title="Vantage 3.0 release notes and Migrator" href="https://docs.abbyy.com/vantage/release-notes/3.0/release-notes" icon="arrow-up-right-from-square">
  View the full release notes for 3.0, 3.0.1, 3.0.2, 3.0.3, and 3.0.4 on docs.abbyy.com, including Vantage 3.0 Migrator updates.
</Card>

## Recommended approach

A dedicated step-by-step migration guide is planned for this page. The recommended pattern today is:

<Steps>
  <Step title="Stand up a parallel 3.0 environment">
    Provision a separate environment following [Azure](/vantage/self-hosted/v3.0/providers/azure) or [Self-Managed Kubernetes](/vantage/self-hosted/v3.0/providers/self-managed). Note that the `vantage-operator` Helm chart supports only one instance per cluster; see [Known Limitations](/vantage/self-hosted/v3.0/known-limitations#one-operator-instance-per-cluster).
  </Step>

  <Step title="Migrate data with the Vantage 3.0 Migrator">
    Use the Vantage 3.0 Migrator to move data from your 2.7 install into the 3.0 environment. Confirm the 3.0 install is healthy first: wait for the `Vantage` resource's `Ready` condition, and wait for the skill installer job to complete. See [Lifecycle](/vantage/self-hosted/v3.0/lifecycle#skill-installation-runs-separately) for the monitoring commands.
  </Step>

  <Step title="Cut traffic over">
    Once data is migrated and verified, point your DNS / clients at the 3.0 cluster. Keep the 2.7 environment available as a rollback target until you've validated production traffic on 3.0.
  </Step>

  <Step title="Decommission 2.7">
    Once 3.0 has run cleanly through your verification window, decommission the 2.7 environment per your normal change management process.
  </Step>
</Steps>

## What to bring to your account team

If you're planning a migration window, your ABBYY account team will need:

* Your current 2.7 version and any out-of-band patches.
* Whether your mail setup depends on an SMTP auth scheme other than basic auth: the 3.0 SMTP path currently supports only basic auth or no auth, and SendGrid is the default mail provider. See [Known Limitations](/vantage/self-hosted/v3.0/known-limitations#smtp-supports-basic-auth-only).
* Expected document throughput and tenant counts, used to validate sizing for the 3.0 environment.

## What's next

<CardGroup cols={2}>
  <Card title="Architecture overview" icon="book-open" href="/vantage/self-hosted/v3.0/introduction">
    What changes structurally between 2.7 and 3.0.
  </Card>

  <Card title="Vantage 2.7 docs" icon="clock-rotate-left" href="/vantage/self-hosted/v2.7/introduction">
    Reference for your existing 2.7 deployment until migration completes.
  </Card>
</CardGroup>