Skip to content

FEAT-084 - Migration Wizard For Legacy Profile Import

Decision

Record this eMuleAI feature as WONT_DO for eMuleBB.

The first eMuleBB release line should not add a wizard that copies or mutates legacy profiles automatically. eMuleBB has strict .met/.dat compatibility and backup policy, and profile import is a data-loss-sensitive workflow. A wizard could be useful later, but it should not be part of the accepted future backlog now.

eMuleAI References

Review source: eMuleAI commit 8e34bdec2b7e4fe9e4307df9d80f691804be99ed.

Rationale

  • Profile migration touches high-value data: downloads, known files, credits, server lists, Kad state, categories, and preferences.
  • A wizard can obscure which files were copied, skipped, rewritten, or backed up.
  • eMuleBB already documents .met/.dat file roles and backup behavior. Any future import tool should be a separate, heavily-tested operator workflow, not a startup wizard.

Replacement Direction

Keep profile movement manual for now. If reopened, implement it as an external dry-run-capable migration tool with explicit source/target paths, full backups, and no automatic startup mutation.