This feature is available from the Pro plan and above.
Contentstack is a headless content management system (CMS) that helps teams manage and deliver digital content across multiple platforms. Known for its flexibility and ease of use, it’s a powerful tool for content creators and developers.
With the Contentstack app, you can sync your Contentstack data in just a few clicks, making localization effortless.
Getting started
Adding Contentstack languages
Decide which languages you want to translate. In Contentstack, open your stack and go to Settings > Languages.
Click New language, and a dialog box will appear where you can either select a predefined language or create a custom one.
Once selected, click Add.
Generate Contentstack API token
To generate a new API key and management token, go to Settings > Tokens in Contentstack. Switch to the Management tokens tab and click +Management Token. Enter a name for the token and select read and write permissions.
Enter a name for the token and select read and write permissions.
Click Generate token, and you’ll receive your API key and token.
Keep this information secure, as you’ll need it to connect Lokalise with Contentstack.
Create Lokalise project
If you haven’t already, create a Marketing and support project in Lokalise.
Enter a project name, select the base and target languages, and choose Contentstack from the Content integration dropdown.
Click Create project to finalize the setup.
Installing the app
Open your Lokalise project and go to the Content management tab. Click Install, and a dialog will appear.
Enter the Contentstack API keys generated in the previous step, select your region, and click Authorize. The content import process should start automatically.
To retrieve newly created content from Contentstack at any time, click Refresh.
Importing data from Contentstack to Lokalise
Once the app is set up, you can select which content to import under the Content management tab. Check the boxes next to the items you want to import and click Import selected.
You can refine your selection using the search box or by creating a custom filter.
After selecting your content, a dialog box will appear with the following options:
Import languages – choose which languages to import from Contentstack. If a language is not yet in your Lokalise project, it will be created automatically.
Overwrite updated translations – enable this to update previously imported translations in Lokalise with the latest content from Contentstack.
Skip key creation for empty translations – if enabled, Lokalise won’t create translation keys for items without content.
Assign tags – select any tags to apply to the imported items.
Click OK to begin the import. The process will run in the background, and a notification will appear once it’s complete. You can then proceed to the project editor and start translating.
Exporting data from Lokalise to Contentstack
Once your translations are complete, export them back to Contentstack.
Open the Content management tab.
Select the items you want to export by checking the boxes.
Click Export selected.
A dialog box will appear with the following options:
Export languages – Select the languages to export. Only languages that exist in Contentstack can be chosen (as described in the Adding Contentstack languages section).
Don't export empty translations – Enable this to skip exporting untranslated content.
Click OK to start the export. The process will run in the background, and you’ll receive a notification once it’s finished.
Known issues
Unique IDs
In Contentstack, each field within a content type has a unique ID based on its display name. If this ID is modified, the Lokalise app will generate a new key name, as the integration relies on consistent key names. However, changing the display name alone will not affect the existing Lokalise key linkage.
If you change a field’s unique ID in Contentstack, here’s what will happen:
In Contentstack: The content in that field will be removed for all entries using this content type.
In Lokalise:
After clicking Refresh, the old entries will be replaced with new ones.
During the next import, Lokalise will create new keys with different names.
When exporting, Lokalise will use the new keys, and the original keys will no longer be linked.