# Live Project Data Migration UI

1. [Step By Step Process](#id-1.-step-by-step-process)
2. [Demo Video](#id-2.-demo-video)

## 1. Step By Step Process

## 1. Exporting Policy Data

Data migration feature allows transfer of some or all policy artefacts and/or state into another policy (on the same of different Guardian instance) by exporting into and then importing the .data file.

To perform export press ‘**Export policy data**’ option in the Policy menu.

The operation is available for dry-run and published policies.

<figure><img src="/files/l5tVwFDNe93HmVxk6A17" alt=""><figcaption></figcaption></figure>

## 2. Importing/Exporting Keys for Dry Run Policies

To export/import virtual users’ keys and DID documents for dry-run policies press the corresponding ‘**Export virtual keys**’ or ‘**Import virtual keys**’ menu options.

They can be imported into another dry-run policy, where data was migrated from the current policy.

<figure><img src="/files/l5tVwFDNe93HmVxk6A17" alt=""><figcaption></figcaption></figure>

## 3. Migrating Policy State to Destination Policy

If Policy state flag is set in the ‘**Migrate Data**’ dialog, the entire policy state gets migrated into the destination policy.

This includes block states - steps, timers, multi-signs, split documents, aggregate documents, etc...

To get information about different steps in the below migration process screen, please refer to [Migration Process](/guardian-dev/guardian/standard-registry/discontinuing-policy-workflow/apis-related-to-discontinuing-policy-workflow/migratepolicy-data.md)

<figure><img src="/files/0AaDrAI2utwqLKcje1rE" alt=""><figcaption></figcaption></figure>

## 4. Migrate Retire Pools

When ‘Migrate retire pools’ flag is selected, the migration process will re-create all selected existing retirement pools, from all contracts created by the ‘current’ instance, in the new retirement contract. The UI allows the user to map policy tokens and select the new retire contract.

<figure><img src="/files/bkNQfYGcGIPHj4LGrqDW" alt=""><figcaption></figcaption></figure>

## 5. Change VC Document during Migration

We have added ability to change VC which will be migrated by clicking on "**Edit document**" button under operations column:

<figure><img src="/files/qKVMe7lbxmj967zMCT7P" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/xmUzTP9nCgqX0R8Zzu6x" alt=""><figcaption></figcaption></figure>

When state migration is selected block mapping could be used to optimize the migrations.

<figure><img src="/files/vfwDTTci070mDEhulAuQ" alt=""><figcaption></figcaption></figure>

For Policies with dynamic tokens mapping of token templates might be required.

<figure><img src="/files/iyoHSZhmOZLwTTFxVwqL" alt=""><figcaption></figcaption></figure>

## 2. Demo Video

[Youtube](https://youtu.be/stSudc82pZU?si=Nsv6RyM6I_NpRvwE\&t=110)


---

# Agent Instructions: 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://guardian.hedera.com/guardian-dev/guardian/standard-registry/live-project-data-migration/live-project-data-migration-ui.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.