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

Overview

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

Prerequisites

Before starting:

Method 1: CLI Migration (Recommended)

The fastest way to migrate everything at once.

Step 1: Install IntlPull CLI

npm install -g @intlpull/cli

Step 2: Get Your Lokalise API Key

Step 3: Run Migration

npx intlpull migrate --from lokalise

You'll be prompted for:

Step 4: Verify

Once complete, check your IntlPull dashboard to verify:

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:

Step 4: Configure Options

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

Export Translation Memory

Export Glossary

Import to IntlPull

Post-Migration Steps

1. Update CI/CD Pipelines

Replace Lokalise CLI commands with IntlPull:

# Before (Lokalise)
lokalise2 file download --project-id xxx

# After (IntlPull)
npx intlpull pull

2. Update Environment Variables

# Remove
LOKALISE_API_TOKEN=xxx
LOKALISE_PROJECT_ID=xxx

# Add
INTLPULL_API_KEY=xxx
INTLPULL_PROJECT_ID=xxx

3. Set Up OTA (Optional)

If you want instant translation updates for mobile apps:

iOS:

import IntlPull

IntlPull.configure(
    projectId: "your-project-id",
    apiKey: "your-api-key"
)

Android:

IntlPull.configure(
    projectId = "your-project-id",
    apiKey = "your-api-key"
)

4. Invite Team Members

5. Cancel Lokalise Subscription

Once verified:

Troubleshooting

"Invalid API Key" Error

Missing Translations

TM Not Importing

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

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

Start your migration now →