[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792XY201N5DYN14BVGQNKNN":3,"skill-same:01M792XY201N5DYN14BVGQNKNN":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M792XY201N5DYN14BVGQNKNN","lokalise-migration-deep-dive",null,"Execute major migration to Lokalise from other TMS platforms with data migration strategies.\nUse when migrating to Lokalise from competitors, performing data imports,\nor re-platforming existing translation management to Lokalise.\nTrigger with phrases like \"migrate to lokalise\", \"lokalise migration\",\n\"switch to lokalise\", \"lokalise import\", \"lokalise replatform\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--lokalise-pack--lokalise-migration-deep-dive\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: lokalise-migration-deep-dive\ndescription: |\n  Execute major migration to Lokalise from other TMS platforms with data migration strategies.\n  Use when migrating to Lokalise from competitors, performing data imports,\n  or re-platforming existing translation management to Lokalise.\n  Trigger with phrases like \"migrate to lokalise\", \"lokalise migration\",\n  \"switch to lokalise\", \"lokalise import\", \"lokalise replatform\".\nallowed-tools: Read, Write, Edit, Bash(npm:*), Bash(lokalise2:*), Bash(curl:*), Bash(jq:*), Bash(node:*), Bash(python3:*), Bash(mkdir:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, lokalise, migration]\n---\n# Lokalise Migration Deep Dive\n\n## Current State\n!`lokalise2 --version 2>\u002Fdev\u002Fnull || echo 'CLI not installed'`\n!`npm list @lokalise\u002Fnode-api 2>\u002Fdev\u002Fnull | grep lokalise || echo 'SDK not installed'`\n!`node --version 2>\u002Fdev\u002Fnull || echo 'Node.js not available'`\n\n## Overview\n\nMigrate 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.\n\n## Prerequisites\n\n- Admin or export access to the source TMS platform\n- Lokalise account with a plan that supports the target key count (Free: 500 keys, Pro: unlimited)\n- `LOKALISE_API_TOKEN` environment variable set (read-write token)\n- `lokalise2` CLI or `@lokalise\u002Fnode-api` SDK installed\n- `jq` for JSON manipulation during transformation\n\n## Instructions\n\n### Step 1: Export from Source Platform\n\nEach TMS has its own export format. Export to a Lokalise-compatible format when possible (JSON, XLIFF, or the platform's native format).\n\n**From Crowdin:**\n```bash\nset -euo pipefail\n# Export all translations as JSON (flat key-value structure)\n# Use Crowdin CLI or API to download\ncurl -X POST \"https:\u002F\u002Fapi.crowdin.com\u002Fapi\u002Fv2\u002Fprojects\u002F${CROWDIN_PROJECT_ID}\u002Ftranslations\u002Fbuilds\" \\\n  -H \"Authorization: Bearer ${CROWDIN_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"targetLanguageIds\": [], \"exportApprovedOnly\": false}'\n\n# Download the build when ready (poll build status first)\ncurl -X GET \"https:\u002F\u002Fapi.crowdin.com\u002Fapi\u002Fv2\u002Fprojects\u002F${CROWDIN_PROJECT_ID}\u002Ftranslations\u002Fbuilds\u002F${BUILD_ID}\u002Fdownload\" \\\n  -H \"Authorization: Bearer ${CROWDIN_TOKEN}\" -o crowdin-export.zip\n\nunzip crowdin-export.zip -d crowdin-export\u002F\necho \"Exported $(find crowdin-export\u002F -name '*.json' | wc -l) translation files\"\n```\n\n**From Phrase (formerly PhraseApp):**\n```bash\nset -euo pipefail\n# Export all locales as JSON\nfor LOCALE in en fr de es ja; do\n  curl -X GET \"https:\u002F\u002Fapi.phrase.com\u002Fv2\u002Fprojects\u002F${PHRASE_PROJECT_ID}\u002Flocales\u002F${LOCALE}\u002Fdownload?file_format=simple_json\" \\\n    -H \"Authorization: token ${PHRASE_TOKEN}\" \\\n    -o \"phrase-export\u002F${LOCALE}.json\"\n  sleep 0.5\ndone\necho \"Exported locales: $(ls phrase-export\u002F)\"\n```\n\n**From POEditor:**\n```bash\nset -euo pipefail\n# Export via POEditor API (returns a download URL)\nEXPORT_URL=$(curl -s -X POST \"https:\u002F\u002Fapi.poeditor.com\u002Fv2\u002Fprojects\u002Fexport\" \\\n  -d \"api_token=${POEDITOR_TOKEN}&id=${POEDITOR_PROJECT_ID}&language=en&type=json\" \\\n  | jq -r '.result.url')\n\ncurl -s \"$EXPORT_URL\" -o poeditor-export\u002Fen.json\necho \"Downloaded $(wc -c \u003C poeditor-export\u002Fen.json) bytes\"\n```\n\n### Step 2: Transform Keys and Variable Syntax\n\nDifferent TMS platforms use different interpolation syntax. Lokalise supports multiple formats, but consistency matters.\n\n```javascript\n\u002F\u002F transform-keys.mjs — Convert source format to Lokalise-compatible JSON\nimport { readFileSync, writeFileSync, readdirSync } from 'fs';\n\nconst VARIABLE_TRANSFORMS = {\n  \u002F\u002F Crowdin ICU: {count} -> %{count} (for Ruby) or keep as {count} (for JS)\n  crowdin: (value) => value, \u002F\u002F Crowdin uses ICU by default, Lokalise supports it\n  \u002F\u002F Phrase: %{variable} -> {{variable}} (if targeting i18next)\n  phrase: (value) => value.replace(\u002F%\\{(\\w+)\\}\u002Fg, '{{$1}}'),\n  \u002F\u002F POEditor: {{variable}} -> {variable} (if targeting ICU)\n  poeditor: (value) => value.replace(\u002F\\{\\{(\\w+)\\}\\}\u002Fg, '{$1}'),\n};\n\nconst SOURCE = process.argv[2] || 'crowdin'; \u002F\u002F crowdin | phrase | poeditor\nconst INPUT_DIR = process.argv[3] || 'source-export';\nconst OUTPUT_DIR = process.argv[4] || 'lokalise-import';\n\nconst transform = VARIABLE_TRANSFORMS[SOURCE] || ((v) => v);\n\nfor (const file of readdirSync(INPUT_DIR).filter(f => f.endsWith('.json'))) {\n  const data = JSON.parse(readFileSync(`${INPUT_DIR}\u002F${file}`, 'utf8'));\n  const transformed = {};\n\n  \u002F\u002F Flatten nested keys with dot notation (Lokalise convention)\n  function flatten(obj, prefix = '') {\n    for (const [key, value] of Object.entries(obj)) {\n      const fullKey = prefix ? `${prefix}.${key}` : key;\n      if (typeof value === 'object' && value !== null && !Array.isArray(value)) {\n        flatten(value, fullKey);\n      } else {\n        transformed[fullKey] = transform(String(value));\n      }\n    }\n  }\n  flatten(data);\n  writeFileSync(`${OUTPUT_DIR}\u002F${file}`, JSON.stringify(transformed, null, 2));\n  console.log(`Transformed ${file}: ${Object.keys(transformed).length} keys`);\n}\n```\n\n```bash\nset -euo pipefail\nmkdir -p lokalise-import\nnode transform-keys.mjs crowdin crowdin-export lokalise-import\n```\n\n### Step 3: Create Lokalise Project and Upload\n\n```bash\nset -euo pipefail\n# Create a new project for the migration\nPROJECT=$(curl -s -X POST \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"name\": \"Migration from Crowdin\",\n    \"description\": \"Migrated translations\",\n    \"base_lang_iso\": \"en\",\n    \"languages\": [\n      {\"lang_iso\": \"en\"}, {\"lang_iso\": \"fr\"}, {\"lang_iso\": \"de\"},\n      {\"lang_iso\": \"es\"}, {\"lang_iso\": \"ja\"}\n    ]\n  }')\n\nPROJECT_ID=$(echo \"$PROJECT\" | jq -r '.project_id')\necho \"Created project: ${PROJECT_ID}\"\n```\n\n### Step 4: Bulk Upload Translation Files\n\n```bash\nset -euo pipefail\n# Upload each language file — Lokalise processes uploads asynchronously\nfor FILE in lokalise-import\u002F*.json; do\n  LANG=$(basename \"$FILE\" .json)  # Filename must match lang_iso (e.g., en.json, fr.json)\n\n  # Upload via CLI (handles base64 encoding automatically)\n  lokalise2 --token \"${LOKALISE_API_TOKEN}\" \\\n    file upload \\\n    --project-id \"${PROJECT_ID}\" \\\n    --file \"$FILE\" \\\n    --lang-iso \"${LANG}\" \\\n    --replace-modified \\\n    --distinguish-by-file \\\n    --poll \\\n    --poll-timeout 120s\n\n  echo \"Uploaded ${LANG}: $(jq 'length' \"$FILE\") keys\"\n  sleep 0.5  # Rate limit buffer\ndone\n```\n\n**Alternative: Upload via API (when CLI is unavailable):**\n\n```bash\nset -euo pipefail\nFILE_CONTENT=$(base64 -w 0 lokalise-import\u002Fen.json)\n\ncurl -X POST \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${PROJECT_ID}\u002Ffiles\u002Fupload\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d \"{\n    \\\"data\\\": \\\"${FILE_CONTENT}\\\",\n    \\\"filename\\\": \\\"en.json\\\",\n    \\\"lang_iso\\\": \\\"en\\\",\n    \\\"replace_modified\\\": true,\n    \\\"distinguish_by_file\\\": false\n  }\"\n\n# Upload is async — poll the returned process ID\n```\n\n### Step 5: Validate Coverage\n\n```typescript\nimport { LokaliseApi } from '@lokalise\u002Fnode-api';\nconst lok = new LokaliseApi({ apiKey: process.env.LOKALISE_API_TOKEN! });\n\nasync function validateMigration(projectId: string, expectedKeys: number) {\n  \u002F\u002F Get project statistics\n  const project = await lok.projects().get(projectId);\n  const stats = project.statistics;\n\n  console.log('=== Migration Validation ===');\n  console.log(`Keys imported: ${stats.keys_total} (expected: ${expectedKeys})`);\n  console.log(`Languages: ${stats.languages?.length}`);\n  console.log(`Overall progress: ${stats.progress_total}%`);\n\n  \u002F\u002F Check per-language coverage\n  const languages = await lok.languages().list({ project_id: projectId, limit: 100 });\n  for (const lang of languages.items) {\n    const pct = lang.words_reviewed !== undefined\n      ? Math.round((lang.words_reviewed \u002F (lang.words || 1)) * 100)\n      : 'N\u002FA';\n    console.log(`  ${lang.lang_iso}: ${lang.words} words, ${pct}% reviewed`);\n  }\n\n  \u002F\u002F Flag gaps\n  if (stats.keys_total \u003C expectedKeys) {\n    console.warn(`WARNING: ${expectedKeys - stats.keys_total} keys missing after import`);\n  }\n}\n\nawait validateMigration(process.env.PROJECT_ID!, 5000);\n```\n\n### Step 6: Handle Key Conflicts\n\nWhen importing into an existing project, keys may already exist. Lokalise offers conflict resolution via upload parameters:\n\n```bash\nset -euo pipefail\n# Upload with explicit conflict handling\nlokalise2 --token \"${LOKALISE_API_TOKEN}\" \\\n  file upload \\\n  --project-id \"${PROJECT_ID}\" \\\n  --file lokalise-import\u002Fen.json \\\n  --lang-iso en \\\n  --replace-modified \\\n  --tag-inserted-keys \"migration-$(date +%Y%m%d)\" \\\n  --tag-updated-keys \"migration-updated-$(date +%Y%m%d)\" \\\n  --poll\n\n# After upload, review conflicts by tag\nTAG=\"migration-updated-$(date +%Y%m%d)\"  # Tag matches the upload batch date\ncurl -s -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" \\\n  \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${PROJECT_ID}\u002Fkeys?filter_tags=${TAG}&limit=500\" \\\n  | jq '.keys | length' | xargs -I{} echo \"Keys with conflicts (updated): {}\"\n```\n\n## Output\n\n- Source TMS translations exported and archived locally\n- Keys transformed to Lokalise naming convention (dot-notation, matching interpolation syntax)\n- Lokalise project created with all target languages configured\n- All translation files uploaded with per-language coverage validated\n- Conflict report for any keys that were updated vs. inserted\n- Tags applied for audit trail (date-stamped: `migration-YYYYMMDD`, `migration-updated-YYYYMMDD`)\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Key name conflicts | Different naming conventions across platforms | Flatten nested keys to dot notation in Step 2 before import |\n| Missing translations | Source export was incomplete or language-filtered | Re-export from source with all languages selected |\n| Encoding errors | Non-UTF-8 files from legacy systems | Convert with `iconv -f LATIN1 -t UTF-8 input.json > output.json` |\n| `429` during bulk upload | Uploading too fast (6 req\u002Fs limit) | Use `--poll` flag with CLI which handles waiting, or add `sleep 0.5` between API calls |\n| Variable syntax mismatch | Source uses `%{user_name}`, target expects `{{user_name}}` | Use the transform script in Step 2 to normalize interpolation tokens before upload |\n| Upload process stuck | Large file processing on Lokalise side | Poll process status; files over 50MB should be split by namespace |\n| Plural forms missing | Source platform uses different plural rules | Manually map CLDR plural categories after import |\n\n## Examples\n\n### Quick Migration Inventory\n\nBefore starting a migration, assess the scope:\n\n```bash\nset -euo pipefail\necho \"=== Source Platform Inventory ===\"\necho \"Translation files:\"\nfind source-export\u002F -name \"*.json\" -o -name \"*.xliff\" -o -name \"*.po\" | head -20\necho \"\"\necho \"Languages found:\"\nls source-export\u002F | head -20\necho \"\"\necho \"Sample key count (first file):\"\nFIRST_FILE=$(find source-export\u002F -name \"*.json\" -type f | head -1)\njq 'keys | length' \"$FIRST_FILE\" 2>\u002Fdev\u002Fnull || echo \"Not a flat JSON file\"\n```\n\n### Dry Run — Validate Without Importing\n\n```bash\nset -euo pipefail\n# Upload with --cleanup-mode to see what would happen without committing\nlokalise2 --token \"${LOKALISE_API_TOKEN}\" \\\n  file upload \\\n  --project-id \"${PROJECT_ID}\" \\\n  --file lokalise-import\u002Fen.json \\\n  --lang-iso en \\\n  --poll \\\n  --detect-icu-plurals\n# Review the process result before uploading remaining languages\n```\n\n## Resources\n\n- [Lokalise File Upload API](https:\u002F\u002Fdevelopers.lokalise.com\u002Freference\u002Fupload-a-file)\n- [Supported File Formats](https:\u002F\u002Fdocs.lokalise.com\u002Fen\u002Farticles\u002F1400452-file-formats)\n- [Crowdin Export API](https:\u002F\u002Fdeveloper.crowdin.com\u002Fapi\u002Fv2\u002F#operation\u002Fapi.projects.translations.builds.post)\n- [Phrase Export API](https:\u002F\u002Fdevelopers.phrase.com\u002Fapi\u002F#tag\u002FLocales\u002Foperation\u002Flocale\u002Fdownload)\n- [POEditor Export API](https:\u002F\u002Fpoeditor.com\u002Fdocs\u002Fapi#projects_export)\n- [CLDR Plural Rules](https:\u002F\u002Fcldr.unicode.org\u002Findex\u002Fcldr-spec\u002Fplural-rules)\n\n## Next Steps\n\n- After migration, configure webhooks and CI integration with `lokalise-ci-integration`.\n- Set up team permissions on the new project with `lokalise-enterprise-rbac`.\n- If key counts are large (10K+), optimize API access with `lokalise-performance-tuning`.\n","# Lokalise Migration Deep Dive\n\n## Current State\n!`lokalise2 --version 2>\u002Fdev\u002Fnull || echo 'CLI not installed'`\n!`npm list @lokalise\u002Fnode-api 2>\u002Fdev\u002Fnull | grep lokalise || echo 'SDK not installed'`\n!`node --version 2>\u002Fdev\u002Fnull || echo 'Node.js not available'`\n\n## Overview\n\nMigrate 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.\n\n## Prerequisites\n\n- Admin or export access to the source TMS platform\n- Lokalise account with a plan that supports the target key count (Free: 500 keys, Pro: unlimited)\n- `LOKALISE_API_TOKEN` environment variable set (read-write token)\n- `lokalise2` CLI or `@lokalise\u002Fnode-api` SDK installed\n- `jq` for JSON manipulation during transformation\n\n## Instructions\n\n### Step 1: Export from Source Platform\n\nEach TMS has its own export format. Export to a Lokalise-compatible format when possible (JSON, XLIFF, or the platform's native format).\n\n**From Crowdin:**\n```bash\nset -euo pipefail\n# Export all translations as JSON (flat key-value structure)\n# Use Crowdin CLI or API to download\ncurl -X POST \"https:\u002F\u002Fapi.crowdin.com\u002Fapi\u002Fv2\u002Fprojects\u002F${CROWDIN_PROJECT_ID}\u002Ftranslations\u002Fbuilds\" \\\n  -H \"Authorization: Bearer ${CROWDIN_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"targetLanguageIds\": [], \"exportApprovedOnly\": false}'\n\n# Download the build when ready (poll build status first)\ncurl -X GET \"https:\u002F\u002Fapi.crowdin.com\u002Fapi\u002Fv2\u002Fprojects\u002F${CROWDIN_PROJECT_ID}\u002Ftranslations\u002Fbuilds\u002F${BUILD_ID}\u002Fdownload\" \\\n  -H \"Authorization: Bearer ${CROWDIN_TOKEN}\" -o crowdin-export.zip\n\nunzip crowdin-export.zip -d crowdin-export\u002F\necho \"Exported $(find crowdin-export\u002F -name '*.json' | wc -l) translation files\"\n```\n\n**From Phrase (formerly PhraseApp):**\n```bash\nset -euo pipefail\n# Export all locales as JSON\nfor LOCALE in en fr de es ja; do\n  curl -X GET \"https:\u002F\u002Fapi.phrase.com\u002Fv2\u002Fprojects\u002F${PHRASE_PROJECT_ID}\u002Flocales\u002F${LOCALE}\u002Fdownload?file_format=simple_json\" \\\n    -H \"Authorization: token ${PHRASE_TOKEN}\" \\\n    -o \"phrase-export\u002F${LOCALE}.json\"\n  sleep 0.5\ndone\necho \"Exported locales: $(ls phrase-export\u002F)\"\n```\n\n**From POEditor:**\n```bash\nset -euo pipefail\n# Export via POEditor API (returns a download URL)\nEXPORT_URL=$(curl -s -X POST \"https:\u002F\u002Fapi.poeditor.com\u002Fv2\u002Fprojects\u002Fexport\" \\\n  -d \"api_token=${POEDITOR_TOKEN}&id=${POEDITOR_PROJECT_ID}&language=en&type=json\" \\\n  | jq -r '.result.url')\n\ncurl -s \"$EXPORT_URL\" -o poeditor-export\u002Fen.json\necho \"Downloaded $(wc -c \u003C poeditor-export\u002Fen.json) bytes\"\n```\n\n### Step 2: Transform Keys and Variable Syntax\n\nDifferent TMS platforms use different interpolation syntax. Lokalise supports multiple formats, but consistency matters.\n\n```javascript\n\u002F\u002F transform-keys.mjs — Convert source format to Lokalise-compatible JSON\nimport { readFileSync, writeFileSync, readdirSync } from 'fs';\n\nconst VARIABLE_TRANSFORMS = {\n  \u002F\u002F Crowdin ICU: {count} -> %{count} (for Ruby) or keep as {count} (for JS)\n  crowdin: (value) => value, \u002F\u002F Crowdin uses ICU by default, Lokalise supports it\n  \u002F\u002F Phrase: %{variable} -> {{variable}} (if targeting i18next)\n  phrase: (value) => value.replace(\u002F%\\{(\\w+)\\}\u002Fg, '{{$1}}'),\n  \u002F\u002F POEditor: {{variable}} -> {variable} (if targeting ICU)\n  poeditor: (value) => value.replace(\u002F\\{\\{(\\w+)\\}\\}\u002Fg, '{$1}'),\n};\n\nconst SOURCE = process.argv[2] || 'crowdin'; \u002F\u002F crowdin | phrase | poeditor\nconst INPUT_DIR = process.argv[3] || 'source-export';\nconst OUTPUT_DIR = process.argv[4] || 'lokalise-import';\n\nconst transform = VARIABLE_TRANSFORMS[SOURCE] || ((v) => v);\n\nfor (const file of readdirSync(INPUT_DIR).filter(f => f.endsWith('.json'))) {\n  const data = JSON.parse(readFileSync(`${INPUT_DIR}\u002F${file}`, 'utf8'));\n  const transformed = {};\n\n  \u002F\u002F Flatten nested keys with dot notation (Lokalise convention)\n  function flatten(obj, prefix = '') {\n    for (const [key, value] of Object.entries(obj)) {\n      const fullKey = prefix ? `${prefix}.${key}` : key;\n      if (typeof value === 'object' && value !== null && !Array.isArray(value)) {\n        flatten(value, fullKey);\n      } else {\n        transformed[fullKey] = transform(String(value));\n      }\n    }\n  }\n  flatten(data);\n  writeFileSync(`${OUTPUT_DIR}\u002F${file}`, JSON.stringify(transformed, null, 2));\n  console.log(`Transformed ${file}: ${Object.keys(transformed).length} keys`);\n}\n```\n\n```bash\nset -euo pipefail\nmkdir -p lokalise-import\nnode transform-keys.mjs crowdin crowdin-export lokalise-import\n```\n\n### Step 3: Create Lokalise Project and Upload\n\n```bash\nset -euo pipefail\n# Create a new project for the migration\nPROJECT=$(curl -s -X POST \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"name\": \"Migration from Crowdin\",\n    \"description\": \"Migrated translations\",\n    \"base_lang_iso\": \"en\",\n    \"languages\": [\n      {\"lang_iso\": \"en\"}, {\"lang_iso\": \"fr\"}, {\"lang_iso\": \"de\"},\n      {\"lang_iso\": \"es\"}, {\"lang_iso\": \"ja\"}\n    ]\n  }')\n\nPROJECT_ID=$(echo \"$PROJECT\" | jq -r '.project_id')\necho \"Created project: ${PROJECT_ID}\"\n```\n\n### Step 4: Bulk Upload Translation Files\n\n```bash\nset -euo pipefail\n# Upload each language file — Lokalise processes uploads asynchronously\nfor FILE in lokalise-import\u002F*.json; do\n  LANG=$(basename \"$FILE\" .json)  # Filename must match lang_iso (e.g., en.json, fr.json)\n\n  # Upload via CLI (handles base64 encoding automatically)\n  lokalise2 --token \"${LOKALISE_API_TOKEN}\" \\\n    file upload \\\n    --project-id \"${PROJECT_ID}\" \\\n    --file \"$FILE\" \\\n    --lang-iso \"${LANG}\" \\\n    --replace-modified \\\n    --distinguish-by-file \\\n    --poll \\\n    --poll-timeout 120s\n\n  echo \"Uploaded ${LANG}: $(jq 'length' \"$FILE\") keys\"\n  sleep 0.5  # Rate limit buffer\ndone\n```\n\n**Alternative: Upload via API (when CLI is unavailable):**\n\n```bash\nset -euo pipefail\nFILE_CONTENT=$(base64 -w 0 lokalise-import\u002Fen.json)\n\ncurl -X POST \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${PROJECT_ID}\u002Ffiles\u002Fupload\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d \"{\n    \\\"data\\\": \\\"${FILE_CONTENT}\\\",\n    \\\"filename\\\": \\\"en.json\\\",\n    \\\"lang_iso\\\": \\\"en\\\",\n    \\\"replace_modified\\\": true,\n    \\\"distinguish_by_file\\\": false\n  }\"\n\n# Upload is async — poll the returned process ID\n```\n\n### Step 5: Validate Coverage\n\n```typescript\nimport { LokaliseApi } from '@lokalise\u002Fnode-api';\nconst lok = new LokaliseApi({ apiKey: process.env.LOKALISE_API_TOKEN! });\n\nasync function validateMigration(projectId: string, expectedKeys: number) {\n  \u002F\u002F Get project statistics\n  const project = await lok.projects().get(projectId);\n  const stats = project.statistics;\n\n  console.log('=== Migration Validation ===');\n  console.log(`Keys imported: ${stats.keys_total} (expected: ${expectedKeys})`);\n  console.log(`Languages: ${stats.languages?.length}`);\n  console.log(`Overall progress: ${stats.progress_total}%`);\n\n  \u002F\u002F Check per-language coverage\n  const languages = await lok.languages().list({ project_id: projectId, limit: 100 });\n  for (const lang of languages.items) {\n    const pct = lang.words_reviewed !== undefined\n      ? Math.round((lang.words_reviewed \u002F (lang.words || 1)) * 100)\n      : 'N\u002FA';\n    console.log(`  ${lang.lang_iso}: ${lang.words} words, ${pct}% reviewed`);\n  }\n\n  \u002F\u002F Flag gaps\n  if (stats.keys_total \u003C expectedKeys) {\n    console.warn(`WARNING: ${expectedKeys - stats.keys_total} keys missing after import`);\n  }\n}\n\nawait validateMigration(process.env.PROJECT_ID!, 5000);\n```\n\n### Step 6: Handle Key Conflicts\n\nWhen importing into an existing project, keys may already exist. Lokalise offers conflict resolution via upload parameters:\n\n```bash\nset -euo pipefail\n# Upload with explicit conflict handling\nlokalise2 --token \"${LOKALISE_API_TOKEN}\" \\\n  file upload \\\n  --project-id \"${PROJECT_ID}\" \\\n  --file lokalise-import\u002Fen.json \\\n  --lang-iso en \\\n  --replace-modified \\\n  --tag-inserted-keys \"migration-$(date +%Y%m%d)\" \\\n  --tag-updated-keys \"migration-updated-$(date +%Y%m%d)\" \\\n  --poll\n\n# After upload, review conflicts by tag\nTAG=\"migration-updated-$(date +%Y%m%d)\"  # Tag matches the upload batch date\ncurl -s -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" \\\n  \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${PROJECT_ID}\u002Fkeys?filter_tags=${TAG}&limit=500\" \\\n  | jq '.keys | length' | xargs -I{} echo \"Keys with conflicts (updated): {}\"\n```\n\n## Output\n\n- Source TMS translations exported and archived locally\n- Keys transformed to Lokalise naming convention (dot-notation, matching interpolation syntax)\n- Lokalise project created with all target languages configured\n- All translation files uploaded with per-language coverage validated\n- Conflict report for any keys that were updated vs. inserted\n- Tags applied for audit trail (date-stamped: `migration-YYYYMMDD`, `migration-updated-YYYYMMDD`)\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Key name conflicts | Different naming conventions across platforms | Flatten nested keys to dot notation in Step 2 before import |\n| Missing translations | Source export was incomplete or language-filtered | Re-export from source with all languages selected |\n| Encoding errors | Non-UTF-8 files from legacy systems | Convert with `iconv -f LATIN1 -t UTF-8 input.json > output.json` |\n| `429` during bulk upload | Uploading too fast (6 req\u002Fs limit) | Use `--poll` flag with CLI which handles waiting, or add `sleep 0.5` between API calls |\n| Variable syntax mismatch | Source uses `%{user_name}`, target expects `{{user_name}}` | Use the transform script in Step 2 to normalize interpolation tokens before upload |\n| Upload process stuck | Large file processing on Lokalise side | Poll process status; files over 50MB should be split by namespace |\n| Plural forms missing | Source platform uses different plural rules | Manually map CLDR plural categories after import |\n\n## Examples\n\n### Quick Migration Inventory\n\nBefore starting a migration, assess the scope:\n\n```bash\nset -euo pipefail\necho \"=== Source Platform Inventory ===\"\necho \"Translation files:\"\nfind source-export\u002F -name \"*.json\" -o -name \"*.xliff\" -o -name \"*.po\" | head -20\necho \"\"\necho \"Languages found:\"\nls source-export\u002F | head -20\necho \"\"\necho \"Sample key count (first file):\"\nFIRST_FILE=$(find source-export\u002F -name \"*.json\" -type f | head -1)\njq 'keys | length' \"$FIRST_FILE\" 2>\u002Fdev\u002Fnull || echo \"Not a flat JSON file\"\n```\n\n### Dry Run — Validate Without Importing\n\n```bash\nset -euo pipefail\n# Upload with --cleanup-mode to see what would happen without committing\nlokalise2 --token \"${LOKALISE_API_TOKEN}\" \\\n  file upload \\\n  --project-id \"${PROJECT_ID}\" \\\n  --file lokalise-import\u002Fen.json \\\n  --lang-iso en \\\n  --poll \\\n  --detect-icu-plurals\n# Review the process result before uploading remaining languages\n```\n\n## Resources\n\n- [Lokalise File Upload API](https:\u002F\u002Fdevelopers.lokalise.com\u002Freference\u002Fupload-a-file)\n- [Supported File Formats](https:\u002F\u002Fdocs.lokalise.com\u002Fen\u002Farticles\u002F1400452-file-formats)\n- [Crowdin Export API](https:\u002F\u002Fdeveloper.crowdin.com\u002Fapi\u002Fv2\u002F#operation\u002Fapi.projects.translations.builds.post)\n- [Phrase Export API](https:\u002F\u002Fdevelopers.phrase.com\u002Fapi\u002F#tag\u002FLocales\u002Foperation\u002Flocale\u002Fdownload)\n- [POEditor Export API](https:\u002F\u002Fpoeditor.com\u002Fdocs\u002Fapi#projects_export)\n- [CLDR Plural Rules](https:\u002F\u002Fcldr.unicode.org\u002Findex\u002Fcldr-spec\u002Fplural-rules)\n\n## Next Steps\n\n- After migration, configure webhooks and CI integration with `lokalise-ci-integration`.\n- Set up team permissions on the new project with `lokalise-enterprise-rbac`.\n- If key counts are large (10K+), optimize API access with `lokalise-performance-tuning`.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","lokalise","migration","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute major migration to Lokalise from other TMS platforms with data migration strategies.\nUse when migrating to Lokalise from competitors, performing data imports,\nor re-platforming existing translation management to Lokalise.\nTrigger with phrases like \"migrate to lokalise\", \"lokalise migration\",\n\"switch to lokalise\", \"lokalise import\", \"lokalise replatform\".\n","Read, Write, Edit, Bash(npm:*), Bash(lokalise2:*), Bash(curl:*), Bash(jq:*), Bash(node:*), Bash(python3:*), Bash(mkdir:*), Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--lokalise-pack--lokalise-migration-deep-dive",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill lokalise-migration-deep-dive",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill lokalise-migration-deep-dive",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill lokalise-migration-deep-dive","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--lokalise-pack--lokalise-migration-deep-dive\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]