Skip to content
Back to skills

Lokalise Migration Deep Dive

ASecurity

Execute major migration to Lokalise from other TMS platforms with data migration strategies. Use when migrating to Lokalise from competitors, performing data imports, or re-platforming existing translation management to Lokalise. Trigger with phrases like "migrate to lokalise", "lokalise migration", "switch to lokalise", "lokalise import", "lokalise replatform".

  • 4 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 10, 2026
businessbashapi

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 10, 2026

npx -y skills add micsapp/micstec-skills --skill lokalise-migration-deep-dive --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lokalise Migration Deep Dive?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Lokalise Migration Deep Dive
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/micsapp-lokalise-migration-deep-dive/badge)](https://www.skillsdirectory.com/skills/micsapp-lokalise-migration-deep-dive)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: lokalise-migration-deep-dive
description: |
  Execute major migration to Lokalise from other TMS platforms with data migration strategies.
  Use when migrating to Lokalise from competitors, performing data imports,
  or re-platforming existing translation management to Lokalise.
  Trigger with phrases like "migrate to lokalise", "lokalise migration",
  "switch to lokalise", "lokalise import", "lokalise replatform".
allowed-tools: Read, Write, Edit, Bash(npm:*), Bash(lokalise2:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Lokalise Migration Deep Dive

## Overview
Comprehensive guide for migrating to Lokalise from other TMS platforms or legacy systems.

## Prerequisites
- Access to source system for export
- Lokalise account with appropriate plan
- Understanding of current translation workflow
- Rollback strategy defined

## Instructions
1. **Migration Types**
2. **Instructions**
3. **Flagship+ Skills**

For full implementation details, load: `Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)`

## Output
- Migration assessment complete
- Data exported and transformed
- Lokalise project created
- Keys and translations imported
- Migration validated

## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Key name conflicts | Different naming conventions | Normalize keys before import |
| Missing translations | Export incomplete | Re-export from source |
| Encoding issues | Non-UTF8 files | Convert to UTF-8 |
| Rate limit during import | Too fast | Increase delays between batches |
| Variable syntax mismatch | Different interpolation syntax between platforms | Transform variable tokens to match Lokalise format |

## Examples
### Migration Rollback
```bash
#!/bin/bash
# rollback-migration.sh

# If migration fails, delete the new project
lokalise2 --token "$LOKALISE_API_TOKEN" \
  project delete --project-id "$NEW_PROJECT_ID"

# Keep using old system
echo "Migration rolled back. Continue using source system."
```

## Resources
- [Lokalise Import Guide](https://docs.lokalise.com/en/articles/1400492-uploading-translation-files)
- [Supported File Formats](https://docs.lokalise.com/en/articles/1400452-file-formats)
- [Migration Case Studies](https://lokalise.com/case-studies)

Files in this skill

  • SKILL.md2.3 KB
  • references/implementation-guide.md10.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.