Skip to content

Reference

LuckPerms migration

Import ranks, permissions and users from a LuckPerms 5.x export into sofyCore with a reviewed, resumable plan run from the console.

Bring your ranks, permissions and users over from LuckPerms 5.x in a few steps. While LuckPerms stays installed, sofyCore pauses its own permissions, grants and purchases to avoid conflicts (/access status shows SUSPENDED). Coming from PermissionsEx? See PermissionsEx migration.

  1. Find the owner's UUID

    Ask the owner to join the network, then run access uuid <name> in the console. Use this UUID: a premium UUID website may give a different identity on offline-mode networks.

  2. Analyze the export

    Run access migration luckperms analyze <file> <owner-uuid> <sofycore|import>. sofycore keeps rank definitions that already exist in sofyCore; import takes the definition from the file for those IDs.

  3. Review the plan

    access migration report [plan] shows the summary, conflicts and warnings. access migration status [plan] shows progress.

  4. Apply

    access migration apply <plan> confirm imports exactly the reviewed plan. If it is interrupted, access migration resume <plan> confirm continues or verifies it.

  5. Remove LuckPerms and restart

    sofyCore stays suspended while LuckPerms is installed. Remove it and restart the affected servers.

What is imported and how

  • Rules and personal assignments are merged by node/context or rank/context, using the chosen priority when they match.
  • Ranks and users that are not in the file are kept.
  • Imported groups are NORMAL ranks with no staff authority, whatever their name. The file's owner group becomes lp_owner; the internal owner is only the UUID chosen in the console.
  • With sofycore priority, names that match kept STAFF ranks get a normal lp_<name> alias, shown in the report.
  • Real dates from the export are converted to rank time using the current state of the rank clock.