> For the complete documentation index, see [llms.txt](https://docs.fenixpyre.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fenixpyre.com/migration-guide/migrating-from-legacy-datanchor-to-the-fenixpyre-platform.md).

# Migrating from Legacy Datanchor to the FenixPyre Platform

## Migrating from Legacy Datanchor to the FenixPyre Platform

This guide walks organization **admins** through migrating from the legacy Datanchor platform (Windows agent versions **5.3.3 and lower**) to the current **FenixPyre** platform (Windows agent **6.5.3+**). It covers everything from accepting your new tenant invite to rolling the new agent out to all of your users.

{% hint style="info" %}
**No downtime.** Your existing users can keep working on version **5.3.3** throughout the migration. You only move users to the new agent once you've verified everything has migrated successfully.
{% endhint %}

### Who should follow this guide

This guide is intended for the **organization administrator** responsible for managing FenixPyre. Most of the steps are performed by you in the FenixPyre [admin dashboard](https://docs.fenixpyre.com/references/glossary), while a few are handled by the FenixPyre team on your behalf.

### Migration at a glance

| Phase                      | What happens                                                     | Who's responsible |
| -------------------------- | ---------------------------------------------------------------- | ----------------- |
| 1. Provision new tenant    | A new FenixPyre tenant is created and an admin invite is sent    | FenixPyre team    |
| 2. Accept invite           | Admin accepts the invite and signs in to the new dashboard       | Customer admin    |
| 3. Create Master Key       | Admin creates the Master Encryption Key                          | Customer admin    |
| 4. Migrate keys & policies | Encryption keys and user policies are migrated to the new tenant | FenixPyre team    |
| 5. Pilot verification      | 1–2 users install agent 6.5.3+ and verify the migration          | Customer admin    |
| 6. Full rollout            | Remaining users move to agent 6.5.3+                             | Customer admin    |

### Prerequisites

Before installing the new Windows agent, ensure each machine meets the [FenixPyre Windows Client prerequisites](https://docs.fenixpyre.com/fenixpyre-for-admins/fenixpyre-windows-agent/prerequisites-for-fenixpyre-windows-client-installation). For agent version **6.2.0 and above**, this includes:

* **Whitelist FenixPyre** in your firewall and antivirus software.
* **Microsoft Visual C++ Redistributable (x64) 2019 or higher** installed.
* **TLS 1.2 or above** enabled.
* **AppData folder on local storage** (not network storage).
* **WebView2** installed (you'll be prompted during installation if it's missing).

***

### Step 1 - Accept your new tenant invite

{% stepper %}
{% step %}
**Receive your invitation**

Once the FenixPyre team provisions your new tenant, the admin receives an email invitation to the FenixPyre admin dashboard. The email includes your **Organization ID** (e.g., `[ORG_ID]`) and your **Admin Dashboard URL**. See [Creating a tenant for your Organization](https://docs.fenixpyre.com/fenixpyre-for-admins/getting-started/creating-a-tenant-for-your-organization) for details.
{% endstep %}

{% step %}
**Accept the invite**

Click **Accept Invite** in the email to confirm your admin role. This link expires within a few days, so accept it promptly.
{% endstep %}

{% step %}
**Sign in to the new dashboard**

Log in to the new FenixPyre admin dashboard at `admin.anchormydata.com` using your Organization ID and credentials (or SSO, if configured).
{% endstep %}
{% endstepper %}

***

### Step 2 - Create your Master Encryption Key

A [Master Encryption Key (MEK)](https://docs.fenixpyre.com/fenixpyre-for-admins/getting-started/create-your-master-encryption-key) is used to encrypt File Encryption Keys before they're stored. It must exist before any encryption or decryption can take place on the new tenant.

{% hint style="warning" %}
FenixPyre does **not** store the decrypted version of your Master Key. Copy and securely store the key when prompted - it is essential for decrypting your data in the future.
{% endhint %}

FenixPyre offers [three methods to create your Master Key](https://docs.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/key-management/master-encryption-keys):

1. **Create your own Master Key with FenixPyre** (stored in the FenixPyre-managed HSM) - the most convenient option, recommended for most organizations.
2. **Bring your own Google HSM.**
3. **Bring your own Azure HSM.**

{% stepper %}
{% step %}
**Open Key Management**

In the dashboard, go to **Settings → Security → Key Management** and select the **Master Encryption Keys** tab. See [Create Master Encryption Key with FenixPyre](https://docs.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/key-management/master-encryption-keys/create-master-encryption-key-with-fenixpyre).
{% endstep %}

{% step %}
**Add a new key**

Click **Add new master encryption key**, provide a name, and click **Create Key**.
{% endstep %}

{% step %}
**Save and verify**

Copy and download the key for safekeeping, then enter it on the final step to complete verification.
{% endstep %}
{% endstepper %}

***

### Step 3 - Key and policy migration (FenixPyre team)

After your Master Key is created, the FenixPyre team migrates all **encryption keys** and **user policies** from your legacy tenant to the new tenant. We'll notify you once this is complete.

While you wait, it's a good time to review:

* [**User Policies**](https://docs.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/user-policies) - the rules and access controls applied to your users and groups. A default policy is generated automatically on onboarding.
* [**User Applications**](https://docs.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/user-applications) - the applications allowed to open encrypted files. Confirm that the applications your organization relies on are added to your policies.

***

### Step 4 - Pilot verification

Before rolling out to everyone, have **one or two users** install the new agent and confirm everything migrated correctly.

{% stepper %}
{% step %}
**Download the installer**

In the admin dashboard, go to the **Installers** section and download FenixPyre version **6.5.3+**. Extract the zip to get **FPInstaller.exe**. See [How to download and install the Windows agent](https://docs.fenixpyre.com/fenixpyre-for-admins/fenixpyre-windows-agent/how-to-download-and-install-windows-agent).
{% endstep %}

{% step %}
**Install the agent**

Double-click **FPInstaller.exe**, approve the UAC prompt, and enter your **Organization ID in lowercase** exactly as provided.
{% endstep %}

{% step %}
**Reboot and sign in**

Reboot the machine when prompted (this is mandatory), then launch the FenixPyre agent and sign in.
{% endstep %}

{% step %}
**Verify the migration**

Confirm that encrypted files open correctly and that keys and policies have migrated as expected.
{% endstep %}
{% endstepper %}

***

### Step 5 - Full user rollout

Once pilot verification succeeds, migrate your remaining users:

1. Confirm all users are present on the new tenant. To add or [invite team members](https://docs.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/user-management/invite-your-team-members), use email/password or SSO login as appropriate.
2. Roll out Windows agent **6.5.3+** to all users (following the same install steps as Step 4).
3. Users log in to the new agent and continue working seamlessly.

***

### After migration

{% hint style="success" %}
**You're done!** Once all users are on agent 6.5.3+ and signed in, your organization is fully migrated to the FenixPyre platform.
{% endhint %}

Post-migration checklist:

* [ ] Master Encryption Key created and securely stored
* [ ] Encryption keys and user policies verified on the new tenant
* [ ] Required user applications added to policies
* [ ] Pilot users verified successfully
* [ ] All users migrated to Windows agent 6.5.3+

If you run into any issues during the migration, contact the FenixPyre team through your support channel for assistance.


---

# 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:

```
GET https://docs.fenixpyre.com/migration-guide/migrating-from-legacy-datanchor-to-the-fenixpyre-platform.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.