Agent skill · software engineering · jeremylongshore
lokalise-migration-deep-dive
Execute major migration to Lokalise from other TMS platforms with data
Why this skill is useful
Adds executable scripts for migrating translations from various TMS platforms to Lokalise, including specific API commands and transformation logic.
What it needs
Requires jq, lokalise2, node installed locally. Requires crowdin, lokalise, phrase, poeditor account access. About 6k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lokalise Migration Deep Dive Current State !lokalise2 --version 2>/dev/null echo 'CLI not installed' !npm list @lokalise/node-api 2>/dev/null grep lokalise echo 'SDK not installed' !node --version 2>/dev/null echo 'Node.js not available' Overview Migrate translations from another TMS (Crowdin, Phrase, POEditor) into Lokalise — export from the source platform, transform key names and variable syntax to match Lokalise conventions, bulk upload via API, validate translation coverage, and handle key conflicts with format-aware tooling. Prerequisites Admin or export access to the source TMS platform Lokalise account with a plan that supports the target key count (Free: 500 keys, Pro: unlimited) LOKALISEAPITOKEN environment variable set (read-write token) lokalise2 CLI or @lokalise/node-api SDK installed jq for JSON manipulation during transformation Instructions Step 1: Export from Source Platform Each TMS has its own export format. Export to a Lokalise-compatible format when possible (JSON, XLIFF, or the platform's native format). From Crowdin: From Phrase (formerly PhraseApp): From POEditor: Step 2: Transform Keys and Variable Syntax Different TMS platforms use different interpolation syntax. Lokalise supports multiple formats, but consistency matters. Step 3: Create Lokalise Project and Upload Step 4: Bulk Upload Translation Files Alternative: Upload via API (when CLI is unavailable): Step 5: Validate Coverage Step 6: Handle Key Conflicts When importing into an existing project, keys may already exist. Lokalise offers conflict resolution via upload parameters: Output Source TMS translations exported and archived locally Keys transformed to Lokalise naming convention (dot-notation, matching interpolation syntax) Lokalise project created with all target languages configured All translation files uploaded with per-language coverage validated Conflict report for any keys that were updated vs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lokalise-migration-deep-dive