# Google Translation Hub Migration Checklist

**Hard deadline: Google Translation Hub shuts down on September 20, 2026** (deprecated since June 30, 2025).
Source of truth: <https://docs.cloud.google.com/translation-hub/docs/deprecations>

Companion guide: <https://langbly.com/blog/google-translation-hub-alternative>
Last updated: July 27, 2026.

> **Scope note: read first.** Migrating a Google Translate v2-style *text API*
> integration can be as small as changing the endpoint and API key. Migrating
> Translation Hub *portal, document, glossary, user and review workflows* is a
> real project. This checklist covers both; do not treat the whole migration as
> a one-line change.

---

## 1. Inventory (target: done by August 7, 2026)

- [ ] List all active Translation Hub users and their roles (upload, review, admin)
- [ ] Record review responsibilities per project/language pair
- [ ] List all document formats in use (PDF, DOCX, PPTX, XLSX, HTML, subtitles, XLIFF, ...)
- [ ] Measure monthly volumes: documents and characters per language pair
- [ ] List all language pairs and regional variants
- [ ] Identify historical documents and review history that must remain accessible; export them now
- [ ] Record which projects/departments own which workflows

## 2. Glossaries and terminology

- [ ] Export every glossary from Google Cloud (per project and language pair)
- [ ] Record which workflows each glossary is attached to
- [ ] Note custom/adaptive MT usage: adaptive MT has no 1:1 equivalent elsewhere; plan how glossaries or custom instructions will cover it
- [ ] Recreate glossaries in the target provider
- [ ] Verify glossary application with real documents (see section 6)

## 3. Permissions and review workflow mapping

- [ ] Map each Translation Hub role to the replacement product's permission model
- [ ] Re-document the review workflow (who reviews what, in which order); do not assume settings copy over 1:1
- [ ] Identify training needs for portal users

## 4. API and workflow integrations

- [ ] Catalog every system that calls Translation Hub: scripts, CI pipelines, TMS connectors, internal tools
- [ ] Classify each: text API call (simple) vs. document/portal/review workflow (project)
- [ ] For text API calls, test the endpoint swap (see example below)
- [ ] For document/portal workflows, plan a rebuild in the replacement product

### Text API endpoint swap (scope: text API only)

```python
import requests

response = requests.post(
    "https://api.langbly.com/language/translate/v2",  # was translation.googleapis.com
    headers={"Authorization": "Bearer YOUR_LANGBLY_KEY"},  # was ?key= in the URL
    json={"q": "Hello world", "target": "nl"}
)

print(response.json())
```

Request and response format stay the same (Google Translate v2 compatible).
Use `https://eu.langbly.com` instead if you need EU data residency.

## 5. Security and data residency requirements

- [ ] Document your data-residency requirements (EU-only processing? retention limits?)
- [ ] Verify the replacement's regional processing: Langbly's `eu.langbly.com` endpoint processes in Google Cloud regions in EU member states, with the temporary cache in Frankfurt
- [ ] Check cache/retention behavior against your policy: eligible translation responses may be cached up to 1 hour; idempotent responses and document results up to 24 hours (Langbly)
- [ ] Complete vendor security review / DPA where required

## 6. Parallel-run quality checks (target: mid-August 2026)

- [ ] Build a representative test set: difficult formatting, glossary-heavy text, top language pairs
- [ ] Run old and new workflows in parallel on the test set
- [ ] Have fluent reviewers compare terminology, tone and layout preservation
- [ ] Record pass/fail per workflow; fix gaps before cutover

## 7. Cost calculation

- [ ] Calculate monthly cost on real volumes for each candidate
- [ ] Basis (verified July 27, 2026; re-check before budgeting): Google Cloud Translation Basic lists $20 per 1M characters after the first 500K monthly characters ($10 credit); Langbly includes the first 500,000 input characters/month, then $5 per 1M input characters, no base fee, a 75% lower usage rate. Source: <https://cloud.google.com/translate/pricing>
- [ ] Include document translation and any per-seat/portal costs, not just character rates
- [ ] Note activation requirements: payment details are required to activate Langbly API access

## 8. Cutover plan (target: by September 4, 2026)

- [ ] Set cutover date per workflow (API integrations first, portal users after training)
- [ ] Migrate glossaries and recreate user roles in the replacement
- [ ] Train portal users on the replacement workflow
- [ ] Verify no remaining system calls Translation Hub (logs, config scan)
- [ ] Keep September 5–19 as buffer for issues

## 9. Rollback plan

- [ ] Keep the old configuration/credentials documented and restorable until shutdown
- [ ] Define the trigger for rolling back a workflow (e.g. failed review gate)
- [ ] Remember: rollback is only possible until September 20, 2026; after that date Translation Hub is gone

## 10. Deadline

- [ ] **September 20, 2026: Google Translation Hub shuts down.** All workflows migrated, users trained, old access decommissioned.

---

*Langbly links: [Translation Hub](https://langbly.com/translation-hub) · [Pricing](https://langbly.com/pricing) · [Switch from Google Translate](https://langbly.com/switch-from-google-translate) · [Migration docs](https://langbly.com/docs/migrate-google)*