micsapp 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
- Migration Types
- Instructions
- 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
#!/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."