A Problem That Gets Discovered Late
Video content localization is rarely on the initial due diligence checklist for a merger or acquisition, and it is rarely one of the first integration workstreams stood up in the months immediately following close. It is, with reasonable consistency, discovered as a problem several months into integration, when someone notices that the acquired company's product training videos use different terminology than the acquiring company's, that both organisations have active but different translation vendor contracts, and that customers in a shared market are receiving noticeably inconsistent multilingual content depending on which entity's content they happen to encounter.
This delay is understandable given everything else competing for attention during an integration, and it is also costly, because the problems that accumulate during the delay — vendor contracts renewing on autopilot, terminology diverging further as each side's content continues to be produced independently, customer-facing inconsistency compounding month over month — are considerably cheaper to address early and deliberately than to unwind later once they have had time to compound.
What Actually Needs Reconciling
Two separate sets of translation vendor contracts, frequently with different vendors, different pricing structures, different contract terms, and different remaining durations, none of which naturally resolve themselves and all of which need an explicit decision about consolidation, coexistence, or termination, made with actual visibility into contract terms on both sides rather than by default inertia toward whichever vendor happens to have the more actively engaged relationship manager at the moment integration planning begins.
Two separate terminology glossaries and style guides, per language, that will have diverged in ways both large and small over however many years each organisation operated independently, covering everything from product and feature names to formality register conventions to house style on units, dates, and currency formatting — this divergence is not a minor cosmetic issue once combined content actually reaches the same customer base, since a customer encountering the same underlying concept named two different ways across content from what is now supposedly one company reads as institutional confusion rather than as an understandable artefact of a recent merger they have no visibility into.
Two separate translation memory assets, per language, representing genuinely valuable prior investment on both sides that should not simply be discarded in favour of one side's assets by default, and merging them requires genuine editorial judgement about which side's prior translations should take precedence where the two conflict, rather than a purely mechanical technical merge that preserves both sets without resolving the actual conflicts between them.
Two separate sets of already-localized video content in market, using each organisation's own prior terminology and branding decisions, that will continue to exist and continue to be watched by customers for some time even after decisions about going-forward content have been made, which raises a genuinely separate question from going-forward production: whether and how much of the existing back catalogue is worth updating to the new unified standard, versus being left as-is and allowed to age out of relevance naturally over time.
Sequencing the Reconciliation
Terminology reconciliation for core, customer-visible product and brand terms should generally be prioritised early, ahead of full vendor and tooling consolidation, because customer-facing terminology inconsistency is the most immediately visible symptom of an unreconciled merger to an actual customer, while vendor contract consolidation and tooling unification are largely internal efficiency questions that customers never directly observe and that can reasonably proceed on a somewhat longer timeline without external visibility of the delay.
Establish a single combined terminology decision-making process before attempting to actually resolve individual specific terminology conflicts, since the harder problem is rarely the mechanical act of choosing between two existing terms for a given concept — that decision is usually reasonably quick and low-stakes once someone has clear authority to make it — the harder problem is establishing who actually has that authority and what process they follow, especially where the conflict touches a legacy product name that one side's organisation, sales force, or existing customer base has real emotional or commercial attachment to.
Prioritise which languages and which content categories to reconcile first based on actual customer and market overlap between the two organisations, not by defaulting to whichever organisation's home market happens to be, since the businesses most likely to notice and be affected by terminology or quality inconsistency are customers in markets where both merging organisations had a pre-existing meaningful presence, and those overlapping markets deserve reconciliation priority over markets where only one side had any presence to begin with and where there is consequently no actual inconsistency for a customer to encounter.
Defer full back-catalogue re-localization decisions until the going-forward terminology and process questions are actually settled, since attempting to update historical content to a standard that is itself still being actively negotiated and revised produces wasted rework as that standard continues to shift under the update effort, whereas waiting until the standard has actually stabilised means catalogue updates happen once, against a settled target, rather than multiple times against a moving one.
Vendor Consolidation Decisions
Evaluate both existing vendor relationships against the same criteria you would apply to any new vendor selection, rather than defaulting to whichever vendor belongs to the acquiring organisation simply because the acquiring organisation's existing processes and relationships are more likely to be the ones setting the agenda during integration by default — the acquired organisation's vendor relationship may genuinely be the stronger one for some or all languages and content types, and integration momentum should not be allowed to override an honest comparison purely because one side happens to be structurally in the position of decision-maker during the transition.
Check contract terms on both sides for change-of-control provisions, remaining contract duration, and any exit or transition costs before making a consolidation decision, since these terms directly affect the actual near-term cost and feasibility of any specific consolidation path and can make an otherwise clearly preferable vendor choice impractical in the near term if the alternative carries a substantial and unavoidable near-term termination cost that has to be weighed against the benefit.
Where full consolidation onto one vendor is not immediately practical due to contract constraints, plan an explicit interim multi-vendor coexistence period with the same shared terminology governance discipline described elsewhere for any multi-vendor arrangement, treating the interim period as a deliberately managed and time-bounded state with a defined end point, rather than as an indefinite default that never actually gets consolidated because the pressure to address it fades once the most acute post-merger attention has moved on to other priorities.
Brand Voice and Tone Reconciliation
Beyond specific terminology, the two organisations' overall brand voice, formality register, and general content style in each shared language will typically differ in ways that are harder to specify precisely than a glossary entry but are just as noticeable to an audience encountering both, and this reconciliation is a genuinely more subjective and slower process than terminology reconciliation specifically, since it involves an actual editorial and brand decision about which organisation's voice the combined entity should adopt going forward, or whether a genuinely new combined voice should be deliberately developed rather than simply picking one side's existing voice by default.
Involve brand and marketing stakeholders directly in this specific reconciliation, not only the localization or content operations team, since voice and tone reconciliation is fundamentally a brand decision with localization execution implications, rather than a localization decision that happens to also have some brand-adjacent implications, and treating it as purely a localization team's call risks a technically consistent but strategically unconsidered outcome that brand stakeholders later push back on.
Recognise that some markets may have a legitimate reason to retain distinct positioning even post-merger, particularly where the two original organisations served genuinely different market segments or price points that the merger was not actually intended to fully collapse into one undifferentiated offering, and voice reconciliation should follow the actual go-to-market and product strategy decisions being made elsewhere in the integration, rather than localization or content teams independently deciding on a single unified voice ahead of and disconnected from those broader strategic decisions.
Practical First Steps
Conduct an actual content and vendor audit early in integration, even if full reconciliation work is sequenced later, since simply establishing what exists on both sides — which vendors, which contracts, which glossaries, which languages, how much back-catalogue content, what the actual customer market overlap looks like — is foundational information needed to make every subsequent sequencing and consolidation decision well, and this audit itself is a relatively fast and low-cost activity that should not be delayed even where the actual reconciliation work is deliberately sequenced for later.
Freeze new terminology decisions on both sides for genuinely contested core terms while reconciliation is actively underway, rather than allowing both organisations to continue independently producing new content that further entrenches their existing, soon-to-be-reconciled terminology choices during the reconciliation period itself, which only makes the eventual reconciliation harder and creates more back-catalogue content that will eventually need updating.
Assign clear, named ownership for the localization integration workstream specifically, distinct from broader content or brand integration ownership, given how easily this specific area falls through the gaps between the many competing integration priorities and how consistently it seems to only get addressed once it becomes visible as a customer-facing problem rather than being addressed proactively as a foreseeable and known integration task.
A Working Checklist
- Conduct an early audit of both organisations' vendors, contracts, glossaries, languages, and content volume before sequencing full reconciliation.
- Prioritise customer-facing terminology reconciliation ahead of internal vendor and tooling consolidation.
- Establish clear decision-making authority and process for resolving terminology conflicts before attempting to resolve individual conflicts.
- Prioritise reconciliation for languages and markets where both organisations had genuine pre-existing customer overlap.
- Evaluate both existing vendor relationships against equal criteria rather than defaulting to the acquiring organisation's vendor.
- Check contract change-of-control and exit terms on both sides before committing to a consolidation path.
- Plan an explicit, time-bounded interim multi-vendor coexistence period if immediate consolidation is impractical.
- Defer back-catalogue re-localization decisions until going-forward terminology and process standards have stabilised.
- Involve brand and marketing stakeholders directly in voice and tone reconciliation, not only localization teams.
- Confirm brand voice reconciliation aligns with the actual go-to-market and product positioning strategy being decided elsewhere.
- Freeze new contested terminology decisions on both sides during active reconciliation to avoid further entrenchment.
- Assign clear, named ownership for the localization integration workstream specifically.
Frequently Asked Questions
When during an integration should video localization reconciliation start?
Earlier than it typically does in practice. An initial audit of both organisations' vendors, contracts, glossaries, and content volume is fast, low-cost, and should happen early even if full reconciliation work is deliberately sequenced for later. The common pattern of only addressing this once it surfaces as a visible customer-facing inconsistency, months into integration, is more costly than starting the audit and sequencing plan proactively from early in the process.
Should we automatically consolidate onto the acquiring company's existing vendor?
Not automatically, though it is the common default given that the acquiring organisation's processes typically set the integration agenda. Both existing vendor relationships deserve evaluation against the same criteria, since the acquired organisation's vendor may genuinely be the stronger choice for some or all languages, and contract terms — change-of-control provisions, remaining duration, exit costs — on both sides directly affect what consolidation path is actually feasible near-term regardless of which vendor is preferable in principle.
What should happen to already-localized content that used the old terminology?
Defer that decision until the going-forward terminology standard has actually stabilised, rather than updating the back catalogue against a standard that is itself still being negotiated. Updating early against a moving target produces wasted rework as the standard continues to shift. Once settled, the back-catalogue update decision is a separate cost-benefit question from going-forward production, based on how much continued viewership that older content still receives.
Whose brand voice should the combined organisation's localized content use?
This is a brand and go-to-market decision, not a localization team decision, and should be made with direct involvement from brand and marketing stakeholders rather than defaulting to whichever organisation's existing voice the localization team happens to find more familiar. It should also follow, not precede, the broader product and market positioning decisions being made elsewhere in the integration — some markets may genuinely warrant retaining distinct positioning if the merger was not intended to fully collapse two market segments into one.
How do we merge two organisations' translation memories without losing value from either side?
Preserve both sets of assets rather than discarding one in favour of the other by default, since both represent genuine prior investment, but recognise that a purely mechanical merge does not resolve the actual conflicts where the two disagree on how the same concept should be rendered. That resolution requires genuine editorial judgement, made through the same established terminology decision-making authority handling other reconciliation conflicts, rather than an automated or arbitrary tie-break.
What is the biggest risk of not actively managing this during an integration?
Terminology and quality inconsistency compounding the longer it goes unaddressed, since both organisations typically continue producing new content independently during any delay, further entrenching their respective existing choices and creating more back-catalogue content that will eventually need reconciling. What starts as a modest, manageable inconsistency becomes a larger and more expensive one purely as a function of time elapsed without a decision, independent of anything else changing.
Related reading: Video Localization Vendor Management | Video Translation Glossary Building | Localization Metrics That Matter
