# Replace a Translation Agency: 30-Day Plan | Vitra.ai > Moving off an agency is an asset-recovery problem before it is a technology one. A week-by-week plan, and the two things to secure before giving notice. **Canonical URL**: https://www.vitra.ai/general/replace-a-translation-agency-with-ai **Source**: This is the Markdown rendering of https://www.vitra.ai/general/replace-a-translation-agency-with-ai, generated at build time from that page. --- 4 min read # Replace a Translation Agency: 30-Day Plan Moving off an agency is an asset-recovery problem before it is a technology one. A week-by-week plan, and the two things to secure before giving notice. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Senior Product Manager , Vitra.ai Updated Aug 17, 2026 ![Replace a Translation Agency: 30-Day Plan](https://www.vitra.ai/static/images/blog/replace-a-translation-agency-with-ai.jpg) Table of contents [Secure the assets before the conversation](#secure-the-assets-before-the-conversation) [Why the current setup feels chaotic](#why-the-current-setup-feels-chaotic) [Four weeks](#four-weeks) [Scale changes the sequencing, not the plan](#scale-changes-the-sequencing-not-the-plan) [What actually changes afterwards](#what-actually-changes-afterwards) [FAQ](#faq) Contributors [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Senior Product Manager Subscribe to our newsletter Subscribe > **Quick answer —** Before giving notice, recover your translation memory and glossaries and inventory where every asset lives. Then run four weeks: extract, pilot in parallel, migrate by content type, and cut over with the agency still on call.[Vitra.ai Universe](https://www.vitra.ai/platform) creates, translates, adapts and publishes from one place. ## Secure the assets before the conversation The power in an agency relationship sits with whoever holds the accumulated language, and it is usually not you. Two things to get first, in writing and in a usable format: the [translation memory](https://www.vitra.ai/features/translation-memory) as TMX, and every glossary and style guide. That is years of approved wording and it is yours; recovering it after notice is given is markedly harder than before. Then inventory. In a typical vendor arrangement assets are in a portal, a shared drive, an email thread, a TMS you do not administer, and a designer's machine. Nobody has a list, and the list is the project. ## Why the current setup feels chaotic Where things sit Consequence Agency portal You cannot search it Their TMS Memory accrues to them Shared drives No version authority Email threads Approvals with no record Designer machines Layered source files unrecoverable A tracking spreadsheet Out of date within a week None of that is anyone's fault. It is what six tools and two organisations sharing a process with no system of record produces — the [failure pattern](https://www.vitra.ai/general/why-localization-projects-fail) that makes deadlines slip. ## Four weeks **Week 1 — Extract and inventory.** TMX and glossaries out. List every content type, every language, every live asset and where it lives. Import the memory and confirm match rates against real recent content. **Week 2 — Pilot in parallel.** Take one live content type in two languages. Run it both ways — agency and platform — and compare output, turnaround and cost on identical input. Set the [review band](https://www.vitra.ai/features/quality-control) and name your in-market reviewers. Do not cancel anything yet. **Week 3 — Migrate by content type.** Move the highest-volume, lowest-risk type first, usually marketing or product copy. Point the workflows at your own [asset manager](https://www.vitra.ai/features/asset-manager) so output stops landing in someone else's portal. Add the second and third content types as each proves out. **Week 4 — Cut over.** Move the remaining types, including the regulated ones, with reviewers gating them. Keep the agency on a reduced retainer for one month as a fallback you almost certainly will not use — the cost of that month is trivial against the cost of having no fallback. ## Scale changes the sequencing, not the plan A small team compresses this into two weeks because there is one content type and one approver. An enterprise runs the same four weeks per business unit rather than for the whole company, in parallel, with a shared memory underneath — so unit three starts with the vocabulary units one and two already approved. ## What actually changes afterwards One place for every content type, one memory that keeps improving instead of accruing to a vendor, and an [orchestrated run](https://www.vitra.ai/features/agentic-workflows) rather than a chain of handoffs. The measurable version: cost per language falls with each one added, and the elapsed time between requesting and publishing stops being dominated by waiting for someone else. ## FAQ **What should be secured before leaving a translation agency?** The translation memory as TMX and every glossary and style guide, in writing and in a usable format. That is years of approved wording, and recovering it after giving notice is much harder. **How long does migrating off an agency take?** Four weeks for most organisations: extract and inventory, pilot in parallel, migrate by content type, then cut over. A small team can compress it to two; an enterprise runs it per business unit in parallel. **Should the agency be cancelled immediately?** No. Keep them on a reduced retainer for a month after cutover as a fallback. The cost is trivial compared with discovering a gap in regulated content with no alternative available. **Why do assets end up scattered with a vendor arrangement?** Because six tools and two organisations share a process with no single system of record. Files sit in a portal, a shared drive, email threads and designers' machines, and no inventory exists. Our blog ## Lastest blog posts Tool and strategies modern teams need to help their companies grow. Automotive [Automotive Brochure Localization by Market](https://www.vitra.ai/automotive/automotive-brochure-localization) A car brochure is a spec grid, a legal footer and a photo library, all market-specific. What actually has to change, and why the layout decides the schedule. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 Automotive [Automotive Campaign Localization Across Markets](https://www.vitra.ai/automotive/automotive-campaign-localization) Campaigns run through national companies and dealer networks, so one master becomes hundreds of files. Where the offer text and the disclaimers actually break. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 Automotive [Car Service Manual Translation for Technicians](https://www.vitra.ai/automotive/automotive-service-manual-translation) A workshop manual is read mid-repair by someone with the car on a lift. What that demands of procedures, torque figures and fault codes, in every language. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 [View all posts](https://www.vitra.ai/blog/page/1) --- ## Structured data ```json { "@context": "https://schema.org", "@type": "Article", "mainEntityOfPage": { "@type": "WebPage", "@id": "https://www.vitra.ai/general/replace-a-translation-agency-with-ai" }, "headline": "Replace a Translation Agency: 30-Day Plan", "image": [ { "@type": "ImageObject", "url": "https://www.vitra.ai/static/images/blog/replace-a-translation-agency-with-ai.jpg" } ], "datePublished": "2026-08-17T00:00:00.000Z", "dateModified": "2026-08-17T00:00:00.000Z", "author": [ { "@type": "Person", "name": "Samhitha J Bhatt" } ], "publisher": { "@type": "Organization", "name": "Vitra.ai", "logo": { "@type": "ImageObject", "url": "https://www.vitra.ai/static/images/vitra-v-logo.png" } }, "description": "Moving off an agency is an asset-recovery problem before it is a technology one. A week-by-week plan, and the two things to secure before giving notice." } ``` ```json { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.vitra.ai" }, { "@type": "ListItem", "position": 2, "name": "General", "item": "https://www.vitra.ai/general" }, { "@type": "ListItem", "position": 3, "name": "Replace a Translation Agency: 30-Day Plan", "item": "https://www.vitra.ai/general/replace-a-translation-agency-with-ai" } ] } ``` ```json { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What should be secured before leaving a translation agency?", "acceptedAnswer": { "@type": "Answer", "text": "The translation memory as TMX and every glossary and style guide, in writing and in a usable format. That is years of approved wording, and recovering it after giving notice is much harder." } }, { "@type": "Question", "name": "How long does migrating off an agency take?", "acceptedAnswer": { "@type": "Answer", "text": "Four weeks for most organisations: extract and inventory, pilot in parallel, migrate by content type, then cut over. A small team can compress it to two; an enterprise runs it per business unit in parallel." } }, { "@type": "Question", "name": "Should the agency be cancelled immediately?", "acceptedAnswer": { "@type": "Answer", "text": "No. Keep them on a reduced retainer for a month after cutover as a fallback. The cost is trivial compared with discovering a gap in regulated content with no alternative available." } }, { "@type": "Question", "name": "Why do assets end up scattered with a vendor arrangement?", "acceptedAnswer": { "@type": "Answer", "text": "Because six tools and two organisations share a process with no single system of record. Files sit in a portal, a shared drive, email threads and designers' machines, and no inventory exists." } } ] } ```