Legacy Connector Deprecation

Content is machine translated from English by Phrase Language AI.

Important

Google Drive (Legacy), Braze (Legacy), Contentful (Entry-Level) and Contentful (Field-Level) connectors will be deprecated on November 30, 2026. Each connector has been replaced by a Platform-level connector version.

Legacy connectors can be created until August 17, 2026.

Migration Guide

Google Drive (Legacy) to Google Drive

Authentication

Re-authenticate with a Google account.

Go to Settings, scroll down to the Integrations section, and click Connectors.
Click New connector.
Change the Type to Google Drive and provide a name for the connector.
Complete the OAuth flow.

Existing Google account credentials are valid for the new connector. No new permissions are required.

Feature parity

Full parity. No behavioral differences.

Braze (Legacy) to Braze

Authentication

The API key generated for the legacy connector is not compatible with the new connector. A new key is required.

To create a new API key:

In Braze, go to Settings > Developer Console > APIs and Identifiers.
Create a new REST API Key with permissions for Templates, Canvases, and Campaigns.
Copy the REST Endpoint URL.

To configure the new connector in Phrase TMS:

Go to Settings, scroll down to the Integrations section, and click Connectors.
Click New connector.
Change the Type to Braze and provide a name for the connector.
Enter the new API key and REST Endpoint URL.

Note

Braze locale codes must use underscores (for example, en_US), not hyphens. Hyphens cause job creation errors. Verify locale codes under Workspace Settings > Multi-Language Locale Settings in Braze before completing the migration.

Feature Differences

The new Braze connector adds the following:

Campaigns and Canvases are available for localization directly, not only HTML email templates.
Drag-and-drop templates are supported when accessed via Campaigns or Canvases.
Locale code variations (de-DE vs de-de, underscores vs hyphens) are resolved automatically through unified language mapping.
Custom locale mappings are configurable per connector.

Contentful (Entry-Level) Legacy and Contentful (Field-Level) Legacy to Contentful 2.0

Authentication

Re-enter Contentful credentials in the Contentful 2.0 connector setup: Space ID, Content Delivery API token, and Content Management API token.

EU-hosted Contentful customers must select the EU auth endpoint during setup. The legacy connector was hardcoded to the US endpoint only.

Feature Differences

Contentful 2.0 adds the following:

Embedded inline entries (pricing tokens, reusable strings, and inline links in rich text) appear as visible, movable placeholders. They were dropped from the translation payload entirely in Contentful (Legacy).
URLs in Markdown links are visible and editable where configured.
JSON Object fields are available for localization.
EU Data Center auth is supported.

Migrating Automated Project Creation

The Automated Project Creation (APC) migration flow is the same for all three connectors. APCs must be migrated one by one.

To migrate an APC:

Go to Settings, scroll down to the Automation section, and click Automated project creation.
Select an APC to migrate and click Clone to duplicate it.
In the duplicate, select the new connector folder.
On save, select Only new and updated files.
Trigger the original (old) APC one final time to ensure all intended jobs are created.
Deactivate the old APC.

Note

If step 5 created a project, complete translation of that project as usual, then delete the old APC.