Forms & Surveys
Part of Translation management software: workflow fit
Evaluating export compatibility with a content system
Check field mapping, locales, formatting, review status and repeat delivery when translations return to a content system.
Evaluate export compatibility by moving one translated entry into a safe copy of the receiving content system and comparing its fields with the source. A connector name or supported file format does not establish that the intended locale, rich text, references and review state will reach the right entry.
Define the receiving record
Choose fictional content with a title, body, linked child entry and short call to action. Record the destination entry ID, field IDs, locale codes, formatting rules and character limits. Mark fields that are localised and those shared across languages. Decide whether delivery should update a draft, create a record or leave publication to an editor.
Reconciliation point / What to compare
- Identity
- Correct entry and field mapping, without an unexpected duplicate
- Language
- Target values under the intended locale code
- Structure
- Headings, lists, links and referenced entries retained
- Readiness
- The intended translation state selected for delivery
- Retry
- A repeated transfer does not silently overwrite newer content
- Exit
- A usable file or another supported extraction route
Keep expected values outside the translation system. Use harmless content in a staging environment where the connector supports one.
Read connector claims narrowly
Lokalise Expert and Contentful: Lokalise documents a standalone Contentful app for Marketing and support projects. It handles specified localised text and RichText fields.
Lokalise also documents a distinct Contentful Native route. The app runs within the Contentful Editor, supports limited RichText capabilities, and can be installed separately in spaces, environments and aliases. Confirm which route the supplier proposes and how it controls release.
Phrase TMS and Contentful: Phrase documents its Contentful 2.0 connector for Business and Enterprise plans, excluding LSP plans. It supports field-level localisation, multiple spaces and environment aliases. Phrase says the connector does not translate JSON objects and currently authenticates through the US data centre only.
Its older Entry-Level and Field-Level connectors are scheduled for deprecation on 30 November 2026. Confirm the connector version and show the actual content model in the proposed account.
For a file route, Lokalise Expert documents format, language, file-structure and branch choices. It generates a new file from extracted keys rather than retaining the uploaded file as a template. Open the resulting file in the receiving system; matching a filename extension is only an initial check.
Connector Claims vs. Actual Functionality: Lokalise and Phrase TMS with Contentful
- Connector Type
- Lokalise Expert App
- Supported Features
- Localised text, RichText fields (limited)
- Installation Scope
- Separate installation in spaces, environments, aliases
- Connector Type
- Lokalise Contentful Native
- Supported Features
- Limited RichText, runs within Contentful Editor
- Installation Scope
- Installed separately in spaces, environments, aliases
- Connector Type
- Phrase TMS Contentful 2.0
- Supported Features
- Field-level localisation, multiple spaces, environment aliases
- Limitations
- Does not translate JSON objects; US data centre only
- Deprecated Connectors
- Entry-Level and Field-Level connectors (deprecation 30 November 2026)
Accept the delivered content
Ask the supplier to transfer the fictional entry through the proposed route. Compare every target field with the expected values, inspect the rendered draft and repeat after changing one source sentence and one child entry. Record skipped fields, invalid markup, missing locales and overwritten content. Have a content editor identify which version may be published.
If an essential field or release condition needs a manual step, identify its owner and supported procedure before selecting the integration. Request the exact connector, plan and environment details in the proposed agreement.
