Wiki Release: 2026.09.5 · UltimateClans: 9.1.4 · Documentation branch: 9 · ClanDataExchange

ClanDataExchange#

ClanDataExchange adds administrative migration/data exchange from supported clan ecosystems such as ClansLite/SimpleClans-style sources into the UltimateClans data model. The pages in this section explain what players see in-game, what administrators need to configure, the normal setup flow, and the most common problems you may need to diagnose.

Compatibility#

Component version: 2.0.0
Documentation release: 2026.09.5
Minimum UltimateClans version: 9.0.0

What you can do with it#

Take a full backup of both source plugin data and UltimateClans storage
Run the exchange only on a staging copy first
Select the supported source/migration task and review console output for skipped/converted records
Validate clan count, leaders, members and critical metadata before allowing players online

How it works#

Migration workflow#

ClanDataExchange is an administrative migration tool, not a daily player feature. Treat each exchange as a controlled data migration: stop writes to the source, back up both systems, run the supported conversion once on staging, compare clan/member/leader counts and only then repeat on production.

Do not repeatedly import the same source into an already populated target unless that specific migration path explicitly documents duplicate handling. The safe rollback is restoring the pre-migration backup.

First setup#

Before enabling the feature for players, review these installed files:

language/Lang_EN.yml
polymart.yml

Recommended in-game workflow#

Take a full backup of both source plugin data and UltimateClans storage.
Run the exchange only on a staging copy first.
Select the supported source/migration task and review console output for skipped/converted records.
Validate clan count, leaders, members and critical metadata before allowing players online.

This feature is mainly automatic or accessed through the parent plugin/GUI, so it does not need a large standalone command tree.

What administrators should configure#

Never treat migration as a reversible live command; backup is the rollback.
Do not run repeated imports into a populated target unless the migration path explicitly supports idempotency.
Keep source plugin files unchanged until validation is complete.

Before going live#

Back up the component data/configuration.
Start the server and confirm the component is detected without startup errors.
Test with a non-OP player and the lowest clan role that should have access.
Exercise the complete flow once, including the failure/deny path, not only the happy path.
Restart the server and verify that persistent state survives.
If the network is multiserver, repeat the test from a second node and verify storage/synchronization.

Troubleshooting quick reference#

Symptom	Likely cause	What to check
Import creates fewer clans than expected	Unsupported/corrupt source rows or duplicate/conflicting identifiers were skipped	Review migration output and compare source records individually.
Members are missing	Source identity/UUID resolution failed or membership data is unsupported	Check UUID/player mapping and source plugin storage version.
Running import twice duplicates data	Migration is not designed as a repeatable merge	Restore the clean backup and rerun once after fixing the cause.

For a longer diagnostic flow, open the Troubleshooting page for this component.