Insights: J. Hogue

Mergers and Rebrands: Keep Legacy Names Findable While You Introduce the New One

A customer-focused plan for brand and website transitions after a merger or acquisition, from legacy search mapping and redirects to product explanations and post-launch measurement.

Published
November 12, 2026
Contributor
J. Hogue
Director, Experience Design
Reading time
6 min

When a merger or acquisition changes a brand, customers keep searching for the name they know. While leadership has set the path of the new brand, a customer and search engines need time to catch up. They need to find products, support, documentation, and proof that the service they rely on still exists. The website has to carry those paths forward while introducing the new brand.

Customers know the acquired company’s product by a name that is about to disappear from the navigation. They rely on its support articles or webinars. They want to know whether the product will continue to receive investment. The marketing and digital team has to help those customers find what they need while introducing the new brand and product structure.

That work starts before the new site launches. It starts with a record of what people know today. Our earlier post on the UX of M&A covered which features of each platform to keep. This one picks up after the brand decision.

A Poor Transition Costs Traffic, Revenue and Loyalty

Leadership’s job is to look toward the future. Marketing’s job is to make sure the consequences don’t shrink current opportunities.

A poor brand transition can diminish organic search, referral traffic, and brand loyalty. An example of a rebrand — not an acquisition — that had dire consequences was Logojoy’s poor transition to Looka in 2019, resulting in financial losses that led to cutting 32 jobs out of 40. With an unsuccessful transition from old URL to new, the company lost 80% of its organic traffic which accounted for 50% of its revenue.

A 2024 Marketing Science study of 40 craft brewery acquisitions made between 2006 and 2016 estimated a 15% drop in baseline demand due to lost trust and brand affinity. The researchers attribute the drop to customers’ sense of ownership of a local brand, and they found no drop outside the brand’s home market.

The first example is a growth problem, with a poorly planned technical transition. The second is a trust problem, and our suggestions below are how to address it.

Find Out What the Acquired Brand Means to Its Customers

A product inventory tells you what the company owns. A customer and content inventory tells you what people recognize.

List the company names, product names and common variations people use. Then connect each name to the tasks behind it: evaluating a product, signing in, finding documentation, getting support or deciding whether to renew. Review the pages and resources that serve those tasks, including articles, webinars, events, podcasts and knowledge-base entries.

Look at each audience separately. An acquired product may be familiar in a market where the parent company is barely known. Customers in another region may need local proof or a clearer explanation of what the acquisition changes for them. Interviews and support questions can reveal concerns that search data alone cannot.

The aim is to identify what the new experience needs to preserve, explain or improve.

Our earlier post on the UX of M&A recommended tree testing when combining navigation. Use the same method here. Write tasks around the legacy names, such as “Find the setup guide for LegacyName,” and run them against the new structure before launch.

Map Legacy Searches to Pages That Explain the Change

Before changing URLs, establish a baseline for searches that include the acquired brand and product names. Record the pages those searches reach, the questions those pages answer and the actions customers take next. Review non-branded searches too: a resource attracts people who have never heard of either company. Google Search Console provides query and page performance data and, for eligible properties, a branded-query filter. Its automated brand classifications should be checked against the names that matter to your business.

Then make a decision for each important page and resource. Keep it, revise it, combine it with another resource, move it to a new home or retire it. Record the new destination and the reason for the choice.

URL redirects are part of that plan but where they go is an important decision. Google advises mapping old URLs to relevant new ones and warns against redirecting many unrelated pages to a new homepage. It also advises monitoring both sites during a move because search visibility can fluctuate while pages are recrawled.

Keep the Old Name Visible Where It Helps

Take an illustrative product called LegacyName, now presented as NewName. The new site might include an “All Products” page as a secondary destination. A visible alphabetical list lets people browse, while a search field recognizes both names. A search for LegacyName returns NewName with an accurate label such as “Formerly LegacyName.”

That solves one problem for visitors already on the site. The new product page needs to solve the next one: LegacyName is now NewName.

Explain when the change took effect, what the product does today and what customers should expect to remain available. Link to the relevant documentation and support. If customers are asking whether their account, features or service terms will change, answer those questions directly.

Adobe’s acquisition and transition for Magento is a good example of this: the old Magento product URL leads to a page that states the relationship between Magento, Adobe Commerce and Magento Open Source. Architecture and construction management software-maker Autodesk has a similar page explaining the transition of acquired product PlanGrid.

Choose the relationship language carefully. “Formerly,” “now part of” and “replaced by” describe different outcomes. The product page should use the wording that is true. Support, sales and customer emails should use the same wording as the site.

Consolidate Resources Around Customer Tasks

The product page is only one destination. A customer can reach the site through an old webinar, a support article or a link shared years before the acquisition.

Audit those resources by the question they answer and the audience they serve. Preserve a useful article when its information is still correct. Update names and links where the resource remains valuable. Combine overlapping explanations when one maintained answer will serve customers better. When a resource has a clear successor, send its old URL to that successor.

This is also an opportunity to introduce complementary products. First make it clear that customers have reached the right place for the product they know. Then show how another offering helps with a related task. The connection should be useful to the customer, not simply mirror the company’s new product organization.

Test the Transition From Both Sides

Before launch, test the routes customers are likely to take:

  • Search the web for the legacy company and product names. Does each result lead to a relevant page?
  • Search the new site using those names and common variations. Can someone identify the right product?
  • Open old links to product pages, documentation and resources. Do they reach useful destinations?
  • Read the new product explanation as an existing customer. Is it clear what changed and what continues?
  • Ask selected AI services the same product and ownership questions before and after launch. Are their answers accurate, and which sources do they cite?

These checks measure different things. A working redirect does not prove that a customer understands the new product structure. A clear page does not guarantee that an AI service will cite it. Record a baseline, check again after launch and use the results to decide what needs attention.

Use that baseline to track a few measures: the share of searches that still use the legacy name, how often site searches for that name reach the right product, support requests asking where the product went, and whether AI answers name the product and its owner correctly. When searches for the legacy name fall below a level you set at launch, the “Formerly” labels can come down.

Make the explanation page easy for AI services to cite. State the old name, the new name and their relationship in plain text near the top of the page, and list the legacy name as an alternateName in the product’s structured data.

The executive decision gives the combined company its future name. The transition plan gives existing customers a way to recognize their product, find reliable information and understand where they fit in that future.

Planning a merger or acquisition? Start a conversation with Pare about mapping the customer paths, legacy searches and content that need to survive the transition.

Contributor

  • J. Hogue

    J. Hogue

    J. Hogue is Director, Experience Design, at Pare. Consolidation recurs in his work — including a global intranet that connected employees across offices and surfaced the portfolio of a private equity firm, as well as platform merges following acquisitions.