Assess whether you are capable to migrate existing translations to the new system. It may be a lot of work to copy the old translation into the new one. If you aren't able to spend a lot of time or you are unable find the proposed translation units in the new system, ask for help. Do not proceed until you are sure that you and the people who promised to help are able to migrate everything within a few days, if it is a policy, even within a few hours. Whether you have the capabilities to migrate to the new system usually depends on

Move all existing translations to the corresponding subpages: An Example: If there is a French translation for Example which is located at Exemple, you have to move it to Example/fr to ensure the page history, which also servers for the attribution requirement of the Creative Commons License, all texts at Commons are licensed under, is merged. If you do not move it, the subpages created by the Extension (as soon as a translation to one language was started) must be deleted and the page where the translation was copied from must be moved there (both moving to and deleting a subpage require temporary unmarking a page from translation). After moving, the deleted revisions can be restored (History merge)

Prepare the page for translation. Some templates were designed to help keeping it easy for the translators. Further help is available in the manual.

Mark the page for translation (you must be translationadmin for doing so). FuzzyBot will now overwrite all existing translations with the source version (English). So hurry to complete the next step.

Paste all old translations into the new interface. This can take a considerable amount of time.