lokalise-migration-deep-dive

# 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) - `LOKALISE_API_TOKEN` 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:** ```bash set -euo pipefail # Export all translations as JSON (flat key-value structure) # Use Crowdin CLI or API to download curl -X POST "https://api.crowdin.com/api/v2/projects/${CROWDIN_PROJECT_ID}/translations/builds" \ -H "Authorization: Bearer ${CROWDIN_TOKEN}" \ -H "Content-Type: application/json" \ -d '{"targetLanguageIds": [], "exportApprovedOnly": false}' # ...