Skip to main content

Migrate from Google Translation Hub

Google Translation Hub shuts down on September 20, 2026. It has been deprecated since June 30, 2025. Google's deprecation notice is the source of truth for the date.

This guide covers migrating off Translation Hub before the deadline. If you only use the Google Translate v2 text API (not Translation Hub), see Migrate from Google Translate v2 instead; that migration is much smaller.

Scope

Langbly's text API is compatible with the Google Translate v2 format, so a text-API integration can migrate with an endpoint and key change. Translation Hub's portal, document review workflows and adaptive MT have no 1:1 equivalent: plan those as a real migration, not a one-line change.

Suggested timeline​

Working back from the shutdown date, starting the week of July 27, 2026:

DateMilestone
By Aug 7, 2026Inventory complete (users, formats, volumes, language pairs, glossaries, integrations)
By Aug 14, 2026Providers shortlisted; parallel test runs started
Mid–late Aug 2026Fluent review of parallel output; cost and security sign-off
By Sep 4, 2026Cutover done; glossaries migrated; users trained
Sep 5–19, 2026Buffer; verify nothing still calls Translation Hub
Sep 20, 2026Hard deadline: Translation Hub shuts down

A printable version of this plan is available as a downloadable migration checklist.

Step 1: Inventory​

  • Active users, roles, and review responsibilities
  • Document formats, monthly volumes, and language pairs
  • Portals, templates, and automated workflows
  • Glossaries, terminology rules, and approved translations
  • Historical documents and review history that must stay accessible; export them now
  • Security, retention, and data-residency requirements

Step 2: Migrate documents and portal workflows​

Translation Hub's managed portal and review experience has no direct equivalent in any provider. Replace it with another product's workflow or your own tooling, and train users on it.

Langbly offers a document Translation Hub: upload files in 15+ formats, pick target languages, and download translated documents with layout preserved. Run your representative files through it before deciding.

Step 3: Migrate glossaries and terminology​

  1. Export every glossary from Google Cloud, per project and language pair.
  2. Recreate the glossaries in your new provider. Langbly supports glossaries for API and document translation.
  3. Verify glossary application with real documents. Adaptive MT features have no 1:1 equivalent; glossaries and custom instruction sets cover part of the same ground but behave differently.

Step 4: Map users, roles, and permissions​

List who has access today and what they do (upload, review, administer). Map those roles to the replacement's permission model and re-document the review workflow. Do not assume a 1:1 match with Translation Hub's role structure.

Step 5: Migrate API and workflow integrations​

Catalog every system that calls Translation Hub and classify each one:

  • Text API calls: smallest change. Langbly's endpoint is Google Translate v2-compatible:
import requests

response = requests.post(
    "https://api.langbly.com/language/translate/v2",
    headers={"Authorization": "Bearer YOUR_LANGBLY_KEY"},
    json={"q": "Hello world", "target": "nl"}
)

print(response.json())

Only the base URL and authentication change; the request and response format stay the same. Use https://eu.langbly.com for the EU Data Residency endpoint (processing in Google Cloud regions in EU member states, cache in Frankfurt).

  • Document, portal, and review workflows: plan a rebuild in the replacement product. The endpoint swap above does not cover them.

Step 6: Run quality checks in parallel​

Build a representative test set (difficult formatting, glossary-heavy text, top language pairs). Run old and new workflows in parallel and have fluent reviewers compare terminology, tone, and layout preservation. Cut over only after the parallel runs pass review. Keep a rollback plan ready, usable only until September 20, 2026.

Step 7: Calculate costs​

Verified July 27, 2026 against the Google Cloud Translation pricing page (re-check before budgeting):

  • Google Cloud Translation Basic: first 500K characters/month covered by a $10 credit, then $20 per 1M characters. Document translation and Advanced features are priced separately.
  • Langbly: first 500,000 input characters/month included, then $5 per 1M input characters with no base fee, a 75% lower usage rate. Payment details are required to activate API access.