How to Migrate from Lokalise to IntlPull (Step-by-Step Guide)

Overview

Migrating from Lokalise to IntlPull takes about 10 minutes and preserves:

• All projects and their structure
• All translation keys and values
• All languages
• Translation memory entries
• Glossary/terminology
• Comments and context

Prerequisites

Before starting:

1. Lokalise API key with read access to projects
2. IntlPull account (sign up free)
3. Node.js 18+ (for CLI migration)

Method 1: CLI Migration (Recommended)

The fastest way to migrate everything at once.

Step 1: Install IntlPull CLI

TerminalCopy
npm install -g @intlpullhq/cli

Step 2: Get Your Lokalise API Key

1. Log into Lokalise
2. Go to Profile Settings → API Tokens
3. Create a new token with Read-only access
4. Copy the token

Step 3: Run Migration

TerminalCopy
npx @intlpullhq/cli migrate --from lokalise

You'll be prompted for:

• Lokalise API key
• IntlPull API key (get from IntlPull dashboard)
• Projects to migrate (all or select specific ones)

Step 4: Verify

Once complete, check your IntlPull dashboard to verify:

• All projects appear
• All languages are present
• Translation counts match

Method 2: Web Migration

If you prefer a visual interface:

Step 1: Go to Migration Page

Visit intlpull.com/migrate and select "Lokalise" as your source.

Step 2: Connect Lokalise

Enter your Lokalise API key. IntlPull will fetch your project list.

Step 3: Select Projects

Choose which projects to migrate:

• Select all for complete migration
• Or pick specific projects

Step 4: Configure Options

• Import TM: Yes (recommended)
• Import Glossary: Yes (recommended)
• Import Comments: Yes (recommended)

Step 5: Start Migration

Click "Start Migration" and wait for completion. You'll see progress for each project.

Method 3: Manual Export/Import

For more control, export from Lokalise and import to IntlPull.

Export from Lokalise

1. Open your Lokalise project
2. Go to Download
3. Select format: JSON (Structured)
4. Select all languages
5. Click Build and Download

Export Translation Memory

1. Go to Translation Memory
2. Click Export
3. Download as TMX or CSV

Export Glossary

1. Go to Glossary
2. Click Export
3. Download as TBX or CSV

Import to IntlPull

1. Create a new project in IntlPull
2. Go to Import
3. Upload your JSON files
4. Go to Translation Memory → Import
5. Upload your TM file
6. Go to Glossary → Import
7. Upload your glossary file

Post-Migration Steps

1. Update CI/CD Pipelines

Replace Lokalise CLI commands with IntlPull:

TerminalCopy
1# Before (Lokalise)
2lokalise2 file download --project-id xxx
3
4# After (IntlPull)
5npx @intlpullhq/cli download

2. Update Environment Variables

TerminalCopy
1# Remove
2LOKALISE_API_TOKEN=xxx
3LOKALISE_PROJECT_ID=xxx
4
5# Add
6INTLPULL_API_KEY=xxx
7INTLPULL_PROJECT_ID=xxx

3. Set Up OTA (Optional)

If you want instant translation updates for mobile apps:

iOS:

SwiftCopy
1import IntlPull
2
3IntlPull.configure(
4    projectId: "your-project-id",
5    apiKey: "your-api-key"
6)

Android:

KotlinCopy
1IntlPull.configure(
2    projectId = "your-project-id",
3    apiKey = "your-api-key"
4)

4. Invite Team Members

1. Go to Project Settings → Team
2. Invite translators and developers
3. Set appropriate roles

5. Cancel Lokalise Subscription

Once verified:

1. Export a final backup from Lokalise (just in case)
2. Cancel your Lokalise subscription
3. Enjoy your savings!

Troubleshooting

"Invalid API Key" Error

• Ensure your Lokalise token has read access
• Check for extra spaces when copying
• Generate a new token if needed

Missing Translations

• Verify all languages were selected during export
• Check if translations were in "draft" status in Lokalise
• Re-run migration for specific languages if needed

TM Not Importing

• TM import requires Pro plan or higher
• Check file format (TMX or CSV)
• Contact support if issues persist

Rate Limiting

For large projects, the migration might take longer due to API rate limits. The CLI handles this automatically with retries.

Data Mapping

FAQ

Q: Will I lose any data? A: No. All translations, TM entries, and glossary terms are preserved.

Q: Can I migrate multiple projects? A: Yes. The CLI can migrate all projects at once.

Q: How long does migration take? A: Usually 5-10 minutes for most teams. Large projects (100k+ strings) may take longer.

Q: Can I keep using Lokalise during migration? A: Yes. Migration is read-only on the Lokalise side.

Q: What if something goes wrong? A: Contact our support team. We'll help ensure complete migration.

Cost Comparison

After migration, you'll likely see significant savings:

Summary

1. Get API keys from both platforms
2. Run migration via CLI or web interface
3. Verify data in IntlPull dashboard
4. Update integrations (CI/CD, mobile SDKs)
5. Cancel Lokalise and save money

Need help? Our migration support team is available at support@intlpull.com.

Start your migration now →