In this article, you'll learn the step-by-step process to move your Lokalise project to a different team, ensuring a smooth transition without data loss or disruptions.

We recommend completing the migration process as quickly as possible. This ensures no new content is added to the old instance after you've downloaded and transferred the translation memory.

If you haven't already, you'll need to set up a new team in Lokalise. To achieve that, click on the avatar in the bottom left corner and then choose Create new team.

Enter a team name and click Create.

If you haven’t done this yet, select a subscription plan for the newly created team. To achieve that, click your avatar in the bottom-left corner and switch to the new team.

Then, click the avatar again, go to Billing, and click Change plan.

Choose the subscription plan that best fits your needs. Ensure the plan includes enough seats for all the users you plan to move to the new team. If you’re using Lokalise AI, make sure you have enough AI words to accommodate the usage.

Glossaries cannot be shared between Lokalise teams, so it’s important to handle them carefully during the migration. If your project uses shared glossaries, make sure to download them first. You can find detailed instructions in the Glossary article. To find out if you're using a shared glossary, navigate to the project settings and find the Glossary options:

If it's set to Use a shared glossary, it means the current project is indeed using glossary entries from another project.

After moving the project to the new team, upload the exported glossary into the new team's project as explained in the Glossary article. If another project relies on the glossary from the one you’re about to move, upload the exported glossary into that project to ensure continuity.

If your project relies on translation memory (TM), you’ll need to export it from the old team and upload it to the new one. Unlike glossaries, translation memory is configured at the team level. Refer to the Translation memory article for guidance on exporting and importing entries in TMX format. Once exported, navigate to the settings of the newly created team and upload the file there.

Your project might use multiple translation memories. To check which TM storages are in use, open the project settings and locate the relevant configuration options:

Make a note of the translation memories linked to these settings, then download the appropriate files from the team settings before proceeding with the migration.

When you import a translation memory storage, its name will default to the file name of the TMX file being uploaded. For instance, if the file is named production.tmx, the corresponding TM storage will be named "production." If a storage with the same name already exists in the team, the entries from the uploaded file will be merged into that existing storage.

By default, Lokalise teams have a single storage called "Lokalise Translation Memory", which cannot be renamed or removed. If the new team already has entries in this default storage and you import a TMX file with the same name, the entries will be added to this memory.

If you want to avoid merging entries into the default storage, rename the TMX file before uploading it. Once the project is moved to the new team, review the configuration and ensure the correct TM storage is selected for the project.

Once everything is prepared, it’s time to migrate the project to the new team. Go to your project settings and locate the Belongs to team option. From the dropdown menu, select the new team and save your changes.

You’ll receive a notification confirming that all current project users will be added to the target team. Ensure the new team has enough seats to accommodate them. If everything is in order, click Proceed and wait for the migration to complete.

The project will move to the new team along with its settings, private glossary (shared glossaries are not included), and users.

After the migration is complete, take some time to review and ensure everything is set up correctly. Here are the key areas to verify, depending on the features you're using:

If you prefer not to move the original project, you can migrate a copy instead. To create a copy, open the project, go to its settings, and scroll to the bottom. Look for the Create project copy button and click it. The copying process might take a few minutes.

The copy will be created in the same team and will have the same name as the original project, with a "Copy" postfix. Once the copy is ready, you can go to its settings and move it to a different team following the steps outlined above.