Migrating from Localazy to Locize

If you want to move your translations from Localazy to Locize, this guide walks you through exporting your files, mapping your project structure to Locize namespaces, and importing everything cleanly.

Evaluating Locize?
See our comparison with Localazy to understand how our i18next-native approach differs.

Prerequisites

• A Localazy account with an existing project
• A Locize account (create one here if needed)
• (Optional) The Localazy CLI installed if you prefer command-line exports

1) Export your localization files from Localazy

1. Log in to your Localazy account.
2. Open the project you want to migrate.
3. Go to the Download section.
4. Select the format you need (recommended: JSON for i18next projects, but XLIFF, CSV, and others are also supported).
5. Download each language file.
6. If you exported a ZIP, extract it to a local directory.

Localazy also supports exporting via:

• CLI (localazy download)
• API

2) Map Localazy project structure to Locize namespaces

Localazy organizes translations as flat key sets within a project. Locize uses namespaces to split translations into logical groups (e.g. common, dashboard, emails).

Before importing, decide how to map your keys:

• Single namespace — if your Localazy project has a manageable number of keys, import everything into a single namespace (e.g. translation or common).
• Multiple namespaces — if you already prefix keys by domain (e.g. dashboard.title, emails.welcome), split them into separate files per namespace before importing. This keeps your Locize project organized and leverages i18next namespace loading.

3) Import your files into Locize

You can import using any of these options:

• UI import
• CLI
• API

If you split your translations into multiple namespaces in step 2, import each namespace file separately.

4) Update your app config to point to Locize CDN

If you are using i18next, replace your current backend configuration with the Locize backend plugin:

npm install i18next-locize-backend

Then update your i18next config:

import i18next from 'i18next'
import LocizeBackend from 'i18next-locize-backend'

i18next
  .use(LocizeBackend)
  .init({
    backend: {
      projectId: '[YOUR_PROJECT_ID]',
      apiKey: '[YOUR_API_KEY]', // only needed if using saveMissing
    },
    // ...other options
  })

Your app will now load translations directly from the Locize CDN at runtime — no file sync or redeploy needed.

5) Verify & go live

• Spot-check a few keys in each language (especially plural forms and interpolation placeholders).
• Confirm your reference language matches what your app expects.
• If you use i18next, consider enabling saveMissing: true so new keys are sent to Locize automatically during development.
• Test that your app loads translations correctly from the Locize CDN.