An overseas marketing team sends a new type specification to its production partner in China. The archive contains approved product films, regional edits and a reusable promotional project. A request to “update everything” sounds decisive, but it leaves the most important question unanswered: which file will create the next piece of content?
A brand video font migration is not simply an archive clean-up. It is a change to the way future material gets made, followed by a selective decision about existing outputs. A rarely used finished film and a template reused for every campaign should not automatically receive the same treatment.
A transition policy is more useful than a replacement announcement
Bracco’s brand guidelines contain a notice dated April 28, 2026: new material uses Montserrat, while existing material can retain Centra No.2 during a gradual transition. The company links the change partly to licensing-related difficulty using the previous typeface across teams and regions. Its examples include print; this is not evidence of a blanket policy for all its videos.
That is a useful, bounded observation from Bracco’s published guidelines, not a claim that the industry has adopted one migration model. The practical lesson is to specify both the future rule and the treatment of earlier work. This article develops that distinction into an ONCE production method; it does not report Bracco’s internal workflow or savings.
Permission to retain an old visual style is also different from permission to edit with a font. Adobe Fonts’ licensing FAQ, updated March 27, 2026, distinguishes finished graphics from files requiring direct font access: a client who needs that access to edit needs its own appropriate licence. Apply the terms of the actual font and service, not an assumption that an approved brand design makes every handoff permissible.
Scope the next operation, not the age of the file
ONCE proposes a migration trigger note for each content series that still has a job to do. Record its next use, the exact file or project being used, whether editing is planned, the template it depends on and the brand owner’s decision. The note is a production planning tool, not a new licensing standard.
Three next operations deserve different conversations:
- Play the existing export unchanged. Ask whether the brand permits continued use during the transition and whether the existing usage conditions still apply. Preserve the approved output rather than assuming it needs a new render.
- Reopen and change the material. Identify whether this work falls under the brand’s definition of new material. Updating a price, adding a language and changing an aspect ratio need not be treated identically, but the policy owner must make that distinction.
- Generate another output from an old template. Resolve this production entry point early. Otherwise, the next export can add to the very backlog the migration is meant to address.
A policy date alone does not answer every edge case. The brand lead should define which changes trigger migration and approve any exception. The editor should explain what those decisions require in the project, not invent the brand’s policy on its behalf.
Retire a production route without destroying its history
Consider a fictional home-accessory brand supplied from China. A distributor has a finished demonstration film; the central team uses an editable project to generate new retail promotions. The distributor’s file might remain in use if specifically approved. The promotional template needs a separate decision because it continues to produce material.
Do not overwrite the historical project to make the archive appear consistent. Keep the approved old export and its relevant records, identify the replacement template clearly and remove the retired template from the route people use for new work. An archived project and an actively distributed template are different things even if their contents are identical.
For an international team, the key handoff is practical: the person creating the next version must know which project to open. A polished example file sitting in a different department does not accomplish that. Nor should an exception for one existing film silently become permission to create unlimited new versions in the old style.
Price the dependencies a font replacement exposes
A font change can affect line endings, title width, the space around a product and the timing of word-by-word animation. These are checks to perform, not guaranteed problems. Test actual campaign copy before estimating the migration from the number of text layers.
Separate three work packages: the reusable template change, the specific finished films selected for revision, and checks on the required language and format outputs. Shared template work should not be counted as a new design for every export. Equally, a successful template update should not excuse skipping the review of its different outputs.
Text burned into footage needs a different intervention from an editable caption. Locate a legitimately usable project or clean source first. If that source is missing, explain the affected shot and the options for reconstruction or redesign; do not jump directly to reshooting the entire film. Physical text on a historical product or package also raises a factual question, not merely a layout problem.
No universal price or savings percentage follows from this approach. Its value is that a procurement team can compare the same scope across proposals and see which dependency drives the work.
Validate the next job, then choose the next batch
Before accepting the migration, run a real upcoming brief through the new template with the team that will use it. Check their ability to access the required fonts appropriately, reopen the project, handle real copy and produce the intended outputs. Review the rendered result as well as the project.
For brands coordinating with a Chinese production partner, bring the new specification, the active template and one concrete upcoming revision into the ONCE production planning conversation. That is more actionable than a folder link and an instruction to “make it all consistent.”
For ONCE, the strategic opportunity is a clearly scoped maintenance relationship: keep production templates usable, manage approved transitions and revise the selected outputs. This is a proposed service direction, not a claim about current revenue or valuation. For the customer, the decision is immediate: stop creating tomorrow’s legacy files before commissioning a wholesale rebuild of yesterday’s archive.
Source scope: checked October 19, 2026. This is an evergreen production analysis, not an October launch report or legal advice. The hypothetical brand and original AI-generated cover do not depict Bracco work or an ONCE client project.
