Help customers find you through a rebrand

State exactly what changes for the customer

Separate a visual refresh, a name change, a portfolio change and a change to the underlying service. They may happen together, but they are not interchangeable. Write what remains the same and what genuinely changes: ownership, formulation, account access, terms, support or product availability. Do not reassure people that nothing changes if a material part of the experience changes. Have responsible owners verify those statements before they enter campaign copy.

Identify whose orientation is at risk. Regular shoppers may recognize an old pack from a distance. A business customer may require supplier records to match an invoice. A returning user may search an old product name or follow a saved link. List these situations alongside the launch audience. The transition succeeds only when existing customers can continue doing what they came to do, not merely when new artwork reaches its intended channels.

Build a transition register, not a logo checklist

Record each customer-facing touchpoint, its owner, current version, replacement date and dependency. Include stock already in warehouses, retailer listings, receipts, email addresses, payment descriptions, warranty documents, support scripts and physical signs. Prioritize by the harm a mismatch could cause. A decorative social banner and a confusing payment descriptor do not deserve identical launch urgency. Mark third-party surfaces that require a request rather than direct editing access.

Decide where old and new identities must coexist for a period. A temporary explanatory line may help customers connect the names, but it needs an end condition and consistent wording. Avoid indefinite clutter where every asset carries both identities forever. Plan old-stock handling honestly, including situations where shoppers will encounter two packaging versions. Train frontline teams to explain the transition before asking them to answer surprised customers on launch day.

Keep existing routes working

If URLs change, give the technical team a page-level map from old destinations to relevant new ones. Google's migration guidance recommends appropriate permanent redirects, updated internal links and careful monitoring. Sending every old product page to a generic home page can leave people without the item they sought. The marketing owner should verify the intended destination and meaning, while technical owners implement and test the migration safely.

Do not combine every optional technology change with the rebrand simply because the calendar offers a launch date. New identity, domain, checkout and content structure can create interacting failures that are difficult to diagnose. Where practical, sequence changes and preserve a recoverable version. Check saved links, mobile navigation, transactional messages and essential forms using real customer tasks. Search visibility may fluctuate, so avoid promising an invisible transition or a guaranteed ranking outcome.

Distinguish a new identity from a campaign variation

HUGO BOSS's refresh introduced updated expression for BOSS and HUGO while continuing to distinguish the two brands. The case helps a team ask which relationships must remain intelligible during a visible change. It is not a public operational manual for changing every store, account or supplier record. Do not invent a flawless migration story from the scale or celebrity roster of a launch campaign.

Share a Coke temporarily changed prominent pack expression through personal names while remaining a Coca-Cola campaign. It is a useful contrast, not a full corporate rebrand. Ask how a shopper identifies the underlying product when a familiar part of the pack changes, and how named versions coexist with ordinary stock. The brand account documents the creative packaging approach; it does not establish that every recognition or stock-management question was solved without difficulty.

Release against customer checks

Before launch, rehearse the moments most likely to fail: a customer searching the old name, a retailer receiving new stock, someone querying a payment and a support agent handling an old warranty. Assign a person who can fix each problem. Prepare short factual answers and clear escalation routes. An exception log is more useful than pretending the transition will be perfectly synchronized across every partner and inventory location.

After launch, watch evidence of disorientation as well as applause. Track relevant support questions, failed destinations, product-finding mistakes and unresolved third-party changes. Compare like-for-like periods without attributing every sales movement to the new identity. Close the transition when essential journeys work and the planned coexistence conditions have been met. Save what was learned so the next identity change begins with operational memory rather than another last-minute spreadsheet.

Make the reasoning concrete.

A hypothetical repair company changes its trading name while 800 warranty cards and several retailer listings still use the old one.

Keep the old warranty contact route working and provide a verified explanation linking the names. Sequence nonessential redesign work after critical paths are tested.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Change statement

   What changes and what demonstrably stays the same?

2. At-risk audience

   Who relies on an old name, cue, record or link?

3. Touchpoints

   Who owns each surface and when can it change?

4. Coexistence

   Where will old and new versions overlap, and when does that end?

5. Digital mapping

   What is the relevant new destination for each important old path?

6. Release checks

   Which customer tasks and rollback conditions govern launch?

Read with a question in mind.

Watch for the wrong conclusion.

• Treating the launch date as proof that every surface has changed.
• Saying nothing changes without checking terms and service.
• Redirecting every old page to the home page.
• Discarding old routes while customers still depend on them.

Sources & scope

Original editorial synthesis grounded in opened public practice sources and campaign evidence. Exercises, example businesses and calculations are hypothetical. No named human author or reviewer is claimed. This framework is not a validated universal law.

• Google Search Central: How to move a site →Primary practice guidance · Supports: Old-to-new URL mapping, relevant permanent redirects, internal-link updates and monitoring during a URL migration.
• HUGO BOSS Annual Report 2021: New Branding →Primary corporate report · Supports: Brand-refresh context and distinct BOSS/HUGO positioning.
• Coca-Cola: how Share a Coke began in Australia →Primary brand retrospective · Supports: 2011 origin, brief, Ogilvy selection, packaging development, name strategy and retrospective unit-volume claim.