Hi everyone, We're ready to start implementing and testing the new ranking structure we designed for our community.  I'm trying to figure out what would be the best way to create the new ranks without disrupting the user experience. Does anyone have some tips or best practices? Here's what I'm considering: - Do it on Stage first, then, if everything goes well, do it on production. - Temporarily disable email notifications for rank changes - Create all new ranks at the bottom of the list, below our current initial rank (where all new users should land). This way, no one will get these newly created ranks because the community assigns the highest rank possible on the list. - Once we're done creating the ranks we will start deleting the old ranks.  - Enable email notifications again.   I also have some questions... Is there any way to easily backup the current rank structure in case we need to do a rollback? Is there a way to export the ranking structure from Stage and import it on Production? What do you usually test during your QA phase? In our case we're considering testing the styling (we're changing the icons and rank names), but I'm not sure you can test the actual rank structure aside from randomly check some user profiles. Our superusers have an icon next to their username. Is there a way to do that without duplicating each rank and adding a role as a condition for the 'superuser' rank? Any help will be appreciated! Thank you. Oscar ... View more