Prerequisites #️⃣

  • A Strapi v5 instance with the Localazy plugin installed
  • A Localazy project containing your translated content from v4

Context #️⃣

Strapi v5 introduced several breaking changes that affect how content is accessed and structured:

  • Different document identifiers in Strapi v5
  • Modified composition of Localazy keys

Migration Steps #️⃣

Watch our video guide demonstrating the complete migration process step by step.

  1. Login to Localazy

    • Open your Strapi admin panel
    • Navigate to the Localazy plugin

  2. Create a New Project

    • Log in to your Localazy account
    • Create a new project in Localazy (do not use the same project as v4!)
    • This separation will make the migration process clearer and easier to manage

  3. Upload Source Content

    • Upload your source (default) language content from your Strapi v5 instance to the new project
    • This will establish the new content structure in Localazy

  4. Configure Languages

    • Navigate to Localazy and access your new project
    • Add the languages you want to translate your content into
    • These should match the languages you had in your v4 project

  5. Apply Translation Memory

    • Select all languages in your project
    • Choose the “Apply Translation Memory” bulk action
    • This will prepare the content for translation

  6. Link v4 Project

    • Click “Add projects” in the translation memory modal window settings
    • Select your existing Strapi v4 project that contains your translations
    • Confirm the selection to link your v4 project’s translation memory to the new project

  7. Complete Migration

    • Your translations will be migrated automatically
    • The process typically completes within moments
    • Your content will now be translated and properly aligned with your Strapi v5 instance