Migration overview

Move to StringPush from JSON-in-repo libraries or a translation management system (TMS).

Choose your path

flowchart TD
  Start[Existing setup?]
  Start --> Lib[i18next / react-intl / vue-i18n]
  Start --> TMS[Phrase / Lokalise / Crowdin]
  Lib --> Code[Replace SDK calls + publish bundles]
  TMS --> Data[Export JSON + map keys]
  Code --> Overlay[Optional: staging overlay]
  Data --> Overlay

Comparison

	StringPush	JSON in repo (i18next)	Enterprise TMS
Runtime delivery	CDN bundles	Bundled with app	CDN or API
In-context edit	Staging overlay	No	Often yes
Developer keys in repo	No (CDN fetch)	Yes	Varies
Git sync	Beta (export → PR) — guide	Native	Export/import

Effort guide

Source	Effort	Guide
i18next / react-i18next	S–M	From i18next
react-intl / FormatJS	M	Coming soon
vue-i18n	M	Coming soon
Phrase / Lokalise / Crowdin	M–L	Coming soon (JSON export path)

General steps

1. Export strings from the old system (JSON preferred).
2. Import keys into StringPush (admin UI or API; bulk import API on roadmap).
3. Swap runtime initialization in your app.
4. Run staging in parallel until copy is verified.
5. Cut over production environment and allowed domains.

Honest gaps

• Bi-directional Git sync with conflict policies — Enterprise; one-way export → PR is in beta (Git sync).
• Bulk XLIFF/PO import — on the roadmap.
• Rich <Trans> with nested components — use plain t() or values-only <Trans> in v1.

Need help?

Request beta access or contact support.