# 🚢 Migration

The plugin can import from these crate plugins:

* **Excellent Crates**
* **Crazy Crates**
* **Custom Crate**
* **Specialized Crate**
* **AdvancedCrates**
* **AquaticCrates**

<figure><img src=".gitbook/assets/Screenshot%202025-10-05%20123938.png" alt=""><figcaption><p>Editor > Migrations</p></figcaption></figure>

## Limits

* That we can only support the latest version of the plugins above. Migration cannot be done from an outdated versions.
* We cannot guarantee that all the data from other crate plugins will migrate to ours, but reward items will certainly be migrated.
* For AquaticCrates, only reward items are migrated due to the plugin’s very different structure.
* A crate block that can't be used as a crate block, such as a block added in a newer Minecraft version, is skipped with a warning. That crate keeps the default block.

## Excellent Crates

Imports keys, crates, rewards, placed crates and player data from Excellent Crates 6.0.1 or newer: virtual keys, openings, crate cooldowns and reward win counts. Only the Excellent Crates folder in your plugins folder is needed, the plugin itself does not have to be installed. Items saved in its encoded format are only copied exactly while nightcore is installed.

<figure><img src=".gitbook/assets/editor/migrations/excellent-crates.png" alt="" width="563"><figcaption><p>Migrations (Migrate from Excellent Crates (6.0.1+))</p></figcaption></figure>

Reward rarities have no equivalent here, so each reward's chance is folded into its own weight. Anything that could not be mapped, such as milestones or a key amount above 1 per opening, is listed in the report.

## Crazy Crates

Imports keys, crates, rewards, placed crates and player data from Crazy Crates 4.0 or newer. As with Excellent Crates, only its plugin folder is needed. Menu crates are skipped, and crate types with no matching animation open with the default one.

<figure><img src=".gitbook/assets/editor/migrations/crazy-crates.png" alt="" width="563"><figcaption><p>Migrations (Migrate from Crazy Crates (4.0+))</p></figcaption></figure>

## Advanced Crates

Imports crates, rewards and keys from Advanced Crates 4.4.0 or newer. Unlike the two importers above, it reads the crates from the running plugin, so Advanced Crates has to be installed and enabled. Start it from **Editor > Migrations**, there is no command for it.

Each crate keeps its name as the id and gets a key named `<id>_key` made from its key item. Rewards keep their id, chance, commands and display item, and give the configured item when the reward has one. Every crate is imported as a chest with the default idle effects and opening animations. Placed crates and player data are not imported.

## Custom Crates

Imports crates, rewards and keys from Custom Crates. It reads the crates from the running plugin, so Custom Crates has to be installed and enabled. Start it from **Editor > Migrations**, there is no command for it.

Each crate gets a key with the same id, which keeps its glow. Prizes become rewards named `reward_0`, `reward_1` and so on, with their chance, item and commands. The `[bc]` and `[msg]` command prefixes are turned into a `say` and a `msg %player%` command. A crate block that can't be used is skipped with a warning and the crate keeps the default block. Every crate gets the default idle effects and opening animations. Placed crates and player data are not imported.

## Specialized Crates

Imports crates, rewards and keys from Specialized Crates 3.3.9 or newer. It reads every `.crate` file in the Specialized Crates `Crates` folder, so the plugin has to be installed and enabled. Start it from **Editor > Migrations**, there is no command for it.

Each crate keeps its file name as the id and imports its name, enabled state, block (including a head texture), open cost and cooldown. Its key keeps the item, the glow and whether a key is required. Rewards keep their display item, chance and commands, and give the display item unless the reward says otherwise. The chance line is removed from the reward lore, and the player placeholders in commands become `%player%`. A crate file that fails to import is skipped and logged, the rest continue. Every crate gets the default idle effects. Placed crates and player data are not imported.

## Preview and Apply

Excellent Crates and Crazy Crates are imported in two steps, from **Editor > Migrations** or with /crates migrate \<source> \[confirm].

1. **Preview** (left-click, or the command without `confirm`) reads everything and reports what would be imported, without changing anything.
2. **Apply** (right-click and confirm, or the command with `confirm`) backs up the whole PhoenixCrates folder and the player data first, then imports.

Both steps print a summary in chat and write a full report to the migrations folder, listing every item that was renamed, skipped or not mapped. Backups go to the backups folder.

* A crate or key whose id is already taken is imported as `<id>_imported`, and a reward as `<crate>_<reward>`.
* Virtual keys are added to what players already have.
* The Lite version imports up to 5 crates (6 on a [linked server](plugin-information/licensing.md#linking-a-lite-server)) and 5 keys in total, counting the ones you already have.
* Each source can be applied once. To run it again, delete its `.applied` file in the migrations folder.

> **Warning:**
Disable the old plugin after applying, so both plugins do not handle the same crate blocks.

## Phoenix Crates Migration

Moving from the Lite version to the Premium version is automatic. The first time the Premium jar starts, it looks for a plugins/PhoenixCratesLite folder next to it and copies everything across into plugins/PhoenixCrates — your crates, keys, translations, templates and the player database, with nothing converted or dropped.

<figure><img src=".gitbook/assets/image%20(67).png" alt=""><figcaption></figcaption></figure>

### Note

* The copy only runs while plugins/PhoenixCrates does not exist yet. If the Premium jar has already been started once, the folder is there and the migration is skipped. Stop the server, delete or rename that folder, and start again.
* Your old PhoenixCratesLite folder is left untouched. Remove the Lite jar afterwards so both versions are not running side by side.
* The Lite version has no license, so after migrating you may need to fill in `product-license` in config.yml. See [🪪 Licensing](plugin-information/licensing.md).

> **Warning:**
If a PhoenixCratesPro folder is also present, it takes priority and the Lite folder is ignored.

## From MCModels

<figure><img src=".gitbook/assets/Migrate Now (1).png" alt=""><figcaption></figcaption></figure>

> **Info:**
Only applies when purchasing the Premium version.

Moving to PhoenixCrates from another crates plugin through the MCModels deal gives a 30% discount. Contact support and ask for the migration deal. We may ask you to fill in a short form about your previous plugin and why you are switching.

* **Discord** - [Click Here](https://www.myphoenixstore.com/en/media/discord)
* **Email** - support@myphoenixstore.com

Source: https://www.phoenixplugins.com/docs/phoenix-crates/migration