> For the complete documentation index, see [llms.txt](https://docs.guardianservice.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardianservice.app/technical-information/users/standard-registry-users-schemas-and-policies/policies/live-project-data-migration/live-project-data-migration-ui.md).

# Live Project Data Migration UI

## 1. Exporting Policy Data <a href="#id-1.-exporting-policy-data" id="id-1.-exporting-policy-data"></a>

We have added button "**Export policy data**" for published policies and dry-run policies.

By clicking you will get all policy data in the **.data** file.

Then you can use this file for migrating data to another policy.

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

## 2. Importing/Exporting Keys for Dry Run Policies <a href="#id-2.-importing-exporting-keys-for-dry-run-policies" id="id-2.-importing-exporting-keys-for-dry-run-policies"></a>

We have added buttons "**Export/Import virtual keys**" for dry-run policies.

By clicking you will get virtual user’s keys and DID Documents.

Then you can import it in another dry-run policy, where data was migrated from current policy.

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

## 3. Migrating Policy State to Destination Policy <a href="#id-3.-migrating-policy-state-to-destination-policy" id="id-3.-migrating-policy-state-to-destination-policy"></a>

We have added "**Migrate policy state**" flag to migrate data dialog.

When you enable it, you will migrate all policy state to destination policy (includes block states - steps, timers, multi-sign, split documents, aggregate documents, etc...)

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

<figure><img src="/files/2xpmTEb3VMZKnch4gJYZ" alt=""><figcaption></figcaption></figure>

## 4. Change VC Document during Migration <a href="#id-4.-change-vc-document-during-migration" id="id-4.-change-vc-document-during-migration"></a>

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

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

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


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.guardianservice.app/technical-information/users/standard-registry-users-schemas-and-policies/policies/live-project-data-migration/live-project-data-migration-ui.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.