This article describes how to move a Lokalise project from one team to another, step by step. The goal is to keep everything intact and avoid losing any data during the transfer.
To prevent inconsistencies, we recommend completing the migration in one session. Avoid making new changes to the original project once you start the transfer.
Step 1: Create a new team
If the new team doesn’t exist yet, you’ll need to create it.
Click your avatar in the bottom-left corner.
Select Create new team.
Enter the team name.
Click Create.
Your new team is now ready to receive the project.
Step 2: Choose a subscription plan for the new team
Your new team needs its own subscription plan.
Click your avatar in the bottom-left corner and switch to the new team.
Click the avatar again and navigate to Billing.
Select Change plan and choose the plan that fits your needs.
View image
View image
Make sure the plan:
Has enough seats for all contributors you plan to move.
Includes enough AI words if you use Lokalise AI.
Step 3: Download cross-project shared glossary
Glossaries cannot be shared between teams, so they must be migrated manually.
Open the Project settings of the project you’re moving.
Check the Glossary section.
If it shows Use a shared glossary, the project depends on a glossary from another project.
If a shared glossary is used:
Download/export the glossary first (see the Glossary article for steps).
After the migration, upload/import the glossary into the new team’s project.
If another project in the old team also depends on this glossary, upload it there as well to keep consistency.
Step 4: Download Translation memory
If your project uses translation memory (TM), you’ll need to export it from the old team and then upload it to the new one. Unlike glossaries, translation memories are stored at the team level, not the project level.
Follow the instructions in the Translation memory article to:
Export the TM in TMX format from the old team.
Upload that TMX file to the new team (Team settings > Translation memory).
Check which translation memories your project uses
A project can use multiple TM storages, and you’ll want to transfer the correct ones. To verify this, open Project settings and look at:
Translation memory priority
Shows which TM storages the project reads entries from.Translation memory target
Shows where new TM entries are saved.
Make note of the TM storages referenced here, then download those specific TM files from the old team before continuing.
Important notes on uploading Translation Memory
When you upload a TMX file, the storage name will match the file name.
Example: uploadingproduction.tmxcreates a TM storage called production.If a storage with the same name already exists in the new team, entries from the uploaded file will be merged into the existing storage.
Every Lokalise team has one default storage called Lokalise Translation Memory. This storage cannot be renamed or deleted.
If you upload a TMX file named Lokalise Translation Memory.tmx (or anything matching an existing name), its entries will merge into the default storage.
To avoid merging when you don’t want it:
Rename the TMX file before uploading (for example:
project_TM.tmx).
After importing, open your project settings in the new team and confirm the correct TM storage is set under:
Translation memory priority
Translation memory target
Step 5: Move the project to a new team
After preparing the new team, subscription plan, glossary, and translation memory, you’re ready to move the project.
Open Project settings in the project you want to move.
Find the Belongs to team option.
Select the new team from the dropdown.
Save your changes.
You’ll see a notification stating that all current project users will be added to the new team. Make sure the new team has enough seats to include them.
If everything looks correct, click Proceed and wait for the migration to complete.
Step 6: Perform post-migration check
Once the project has finished moving to the new team, review the setup to make sure everything works as expected. Depending on which features your project uses, verify the following:
Confirm that all users have the correct roles and permissions on both the team and project levels. Adjust if necessary.
If contributors were using API tokens for custom integrations (for example, automated import/export workflows), these tokens may need to be regenerated in the new team.
If your project uses OTA, check the OTA configuration and tokens to ensure everything is still working.
Review Translation memory priority and Translation memory target in project settings to ensure the correct TM storages are selected.
Verify glossary settings. If the project used a shared glossary before migration, import the exported glossary file into the new project if you haven’t already.
Verify that QA checks, snapshot settings, automations, and workflows configurations are properly set up.
Confirm that repositories, CMS connectors, notifications, and other apps continue to function correctly.
Check that webhook events still trigger and reach the correct endpoints.
The project will keep:
The same project ID
All keys, translations, languages
The same user IDs for recreated users
However, the team ID changes, so any scripts, pipelines, or external tools referencing the old team ID must be updated to use the new one.
Optional: Move a copy of the project
If you’d rather keep the original project where it is, you can move a copy instead.
Open the project.
Go to Project settings.
Scroll to the bottom and click Create project copy.
The copying process may take a few minutes. The new project will appear in the same team and will have the same name as the original, with "Copy" added to it.
Once the copy is ready:
Open its Project settings
Use the Belongs to team option to move it to the new team (following the same migration steps as above)
Important notes:
The copied project will have a new project ID, and all of its keys will receive new key IDs.
Any scripts, apps, or automated workflows that reference project IDs or key IDs will need to be updated to use the new ones.