How to do migration

How to use Crowdin? Tips&Tricks
1

I have an app that uses crowdin and lingui. We’re in the process of rewriting this app to a new repo.

Is it possible for both repos to share the same crowdin project? That means pushing and pulling strings.

GitHub Integration | Crowdin Docs

2

Hello @gglwebclient!

Yes - Crowdin project doesn’t care how many repos feed it. Two things to get right:

  • Separate crowdin.yml per repo, same project_id. Each repo keeps its own config and pushes/pulls independently - see Configuration File. The only hard rule: the two repos must not map to the same Crowdin file paths, or whichever pushes last wins and clobbers the other’s sources.

  • During the rewrite, give the new repo its own branch. Push it as a separate Crowdin branch so the live app’s strings stay untouched, then drop the old branch at cutover. Same-text strings get leveraged from TM/duplicates automatically, so you’re not re-translating the rewrite from zero.

If you’d rather let Crowdin do the syncing than run the CLI, the VCS integrations also support multiple repositories in one project - and one config file can serve both the integration and the CLI.