Skip to main content

​
Essentials → Vault Migration

If your server was previously using Essentials Economy, you can transfer all balances to Vault with a single operation. EssentialsImportService reads the Essentials/userdata/<uuid>.yml files directly.

​
Configuration

With enabled: true, the import fires in the plugin’s onEnable(). You can also launch it afterward with /vault import essentials if Essentials exists in the plugins folder.

​
Import modes

Internally mode 0 = merge / mode 1 = replace: Essentials balance resolution (parseMoney):
  1. If money is a Number → .doubleValue() directly
  2. If it is text → strips spaces and commas and Double.parseDouble
  3. Not finite → null and stats.failed increments

​
Player resolution by UUID or name

resolvePlayer() tries, in order, for each file Name.yml:
  1. File name as UUID (UUID.fromString(fileBase))
  2. YAML field uuid
  3. Field last-account-uuid (old formats)
  4. Fallback by name: last-account-name → player-name → name → file name
  5. If everything fails → PlayerResolver.resolveByNameWithOfflineFallback generates offline-mode UUID

​
Import statistics

On completion it writes a line to the log:

​
Import marker (anti-re-execution)

So it doesn’t repeat on every restart, upon finishing with failed == 0 it writes:
  • .internal/essentials_import.done (hidden .internal/ folder with dos:hidden on Windows)
  • Visible fallback: legacy essentials_import.done
If failed > 0 it is not marked, so the next startup retries the failed ones.

​
Persistence destination

  • target: file or MySQL inactive → economy.saveToFile() (balances.yml)
  • target: auto (default) and MySQL active → economy.save() via HikariCP