Migrating to Crowdin

Crowdin provides team cooperation features (e.g., inviting project members, defining permission levels, tasks, messages, etc.), workflow automation, integrations and plugins, and many more features you would need for efficient project localization.

To start your migration, you can use the following step-by-step migration instructions.

In Your Previous Translation Tool

To start your migration, you can use the following step-by-step migration instructions.

1. Download source files.
   In most cases, you’ll have them on your machine/server, so this step is optional.

2. Download translations.
   Download all the latest translations you have at the moment of transition.

3. Download TM, Glossary, and Style Guide.
   Download the translation memory, glossary, and style guide so your translators can reuse them in your Crowdin projects.

In Crowdin

Sign up and create your localization project

Sign up or log in if you already have your Crowdin account and create a project to which you’ll migrate your data.

Upload source files

There are a couple of ways you can upload your source files to the Crowdin project. Use one of the following options:

• via UI.
• via direct integration with external services (e.g., GitHub, GitLab, etc.) Explore available integrations on the Crowdin Store.
• via Console Client (CLI).
• via API.

Note

If you work with a source file format not listed in the Supported Formats article, we can develop custom pre-/post-processors for you.

Read more about Uploading Source Files.

Upload Existing Translations

Upload your existing translations to ensure that your previous work won’t be lost and that you continue from where you performed the transition. If you plan to use integrations with GitHub, GitLab, or other services, your existing translations could be uploaded in an automated way.

Read more about Uploading Existing Translations.

Upload TM, Glossary, and Style Guide

If you have a Translation Memory (TM), Glossary, or Style Guide from your previous translation tool, feel free to upload them to your Crowdin project. These localization resources might greatly help your translators during the translation process and ensure high-quality translations.

Migrating a Project to Another Crowdin Account

Crowdin projects are tied to the account that owns them, and project ownership can’t be transferred between Crowdin accounts. To move a project to a different account, recreate it under the new account and re-import your data.

1. In the original account, download your source files, translations, TM, glossary, and style guides.

2. In the new account, create a project and upload the source files, translations, TM, glossary, and style guides as described in the sections above.

Some data is stored at the account level or can’t be exported, so you’ll need to set it up again in the new account:

• Machine Translation engines and AI configurations (these are account-level resources).
• Integrations and webhooks.
• Project members and managers.
• Project settings, such as QA check configuration and target languages.
• String comments, screenshots, and activity history aren’t carried over with this method.

Note

If you need a centralized workspace where projects belong to an organization and ownership can be reassigned between members, consider Crowdin Enterprise.

Assistance from our team

If you require any assistance during the migration process, our team is ready to help you with any step. For any guidance, feel free to contact us.

See Also

For ManagersRead our quick guide for a seamless localization setup.

Migrating to Crowdin EnterpriseLearn how to migrate your projects from Crowdin to Crowdin Enterprise.