Lokalise Migration Deep Dive FAQs

Question 1

Do I need the Lokalise CLI to use this migration skill?

Accepted Answer

While the Lokalise CLI (lokalise2) is recommended for efficiency, the skill also provides alternative migration paths using the Node.js SDK and direct API calls via curl.

Question 2

How are key name conflicts handled during the migration?

Accepted Answer

It utilizes flattening logic to convert nested structures to dot-notation and allows you to tag updated versus inserted keys, making it easy to review and resolve conflicts post-import.

Question 3

How does the skill handle different variable syntaxes like ICU or i18next?

Accepted Answer

The skill includes a dedicated transformation layer that maps interpolation tokens (e.g., converting %{var} to {{var}}) during the migration to ensure compatibility with your target environment.

Question 4

Can I perform a dry run before actually importing data?

Accepted Answer

Yes, the skill includes examples for using cleanup-mode and validation scripts to assess the migration scope and potential changes without committing data to your production project.

Question 5

Which platforms can I migrate from using this skill?

Accepted Answer

This skill provides specific export and transformation scripts for Crowdin, Phrase (formerly PhraseApp), and POEditor, but it can be adapted for any platform that supports JSON or XLIFF exports.

Lokalise Migration Deep Dive

Lokalise Migration Deep Dive

主な機能

ユースケース

主な機能

ユースケース