Lokalise Migration — Deep Dive

What it does

This skill provides a practical, end-to-end migration workflow for moving translation data from other TMS platforms (Crowdin, Phrase, POEditor) into Lokalise. It covers export strategies, key/variable transforms, bulk uploads (CLI/API), conflict handling, and post-import validation.

When to use it

Use during a replatforming or migration to Lokalise where you need reliable, repeatable steps to export source translations, normalize key naming and interpolation, and import with coverage validation and conflict reporting. Suitable for migrations of small to large key counts.

What's included

• Scripts: transform-keys.mjs, CI snippets and many example bash commands for export/upload/validation. The SKILL.md includes example Node/TypeScript validation code and CLI command sequences.
• References: repository includes references folder and specific API docs linked in the skill text.
• Instructions: Detailed prescriptive steps (export, transform, create project, upload, validate, handle conflicts) with example commands for Crowdin/Phrase/POEditor and Lokalise.

Compatible agents

Designed for agent runtimes that can run shell/Node.js workflows and call external CLIs (lokalise2, curl, jq, node). Explicitly lists compatibility with claude-code and codex in frontmatter.