Migration from i18n-excel-manager

If you currently use i18n-excel-manager, this guide helps you move to LangSync while keeping your existing translation workflow intact where possible.

What changes with LangSync

• A typed langsync.config.ts instead of ad-hoc scripts.
• Consistent validation and sync commands for local use and CI.
• Built-in Excel round-trip plus optional AI translation.
• One workflow for engineers and translators.

Migration checklist

1. Install LangSync:

   pnpm add -D @mariokreitz/langsync

2. Create your config with:

   pnpm langsync init

3. Point input, locales, and defaultLocale at your current locale setup.

4. Run langsync validate to identify missing, extra, and empty keys.

5. Run langsync sync to scaffold missing keys without overwriting existing translations.

6. Continue translator handoff with langsync export excel and langsync import excel.

Locale layout migration notes

If your existing files already match one of LangSync's supported layouts, you can keep them as-is.

• Single file per locale: <input>/<locale>.json
• locale-dir namespaces: <input>/<locale>/<namespace>.json
• locale-prefix namespaces: <input>/<locale>.<namespace>.json

Namespaces are opt-in. LangSync does not auto-migrate file layouts or delete target-only namespace files automatically.

AI provider availability

langsync translate supports these providers:

• openai and deepl: released
• anthropic and gemini: experimental (LANGSYNC_AI_EXPERIMENTAL=1)

Related docs

• Introduction
• Getting Started
• Configuration
• CLI export excel
• CLI import excel