Migrating Web Users with Extended Rights from Evolution 2.0.4 to 3.x

User migration is easy only when the old project stayed close to the defaults. As soon as teams extend permissions, TV access, or role logic around web users, upgrades become much riskier. That is why this migration note mattered: it pointed to a practical script for moving web users from Evolution 2.0.4 into Evo 3 while keeping the access model in view.

The important lesson is not just “run a script.” It is that user migration should be treated as a permissions migration too. Teams need to verify group bindings, extra rights, and custom assumptions before calling the upgrade complete, especially if the old project used web users as part of a more advanced account area or commerce workflow.

What to validate during a migration like this

• web user groups and role mappings
• custom permission extensions added in the old build
• login, profile, and access-control behavior after the move
• whether old assumptions still make sense in Evo 3

Source: Telegram post and forum.evo.im migration discussion.