Why combined programmes break quietly
A merger is decided by finance, lawyers and the leadership of two companies. Marketing usually hears about it late and inherits a second programme with its own history: an ad account built by an agency nobody has met, a website on a domain the acquired business has used for years, an email list with consent collected under its own wording, a CRM with different stages, a calendar that already promises customers a sale, and a set of numbers measured in a different way. The takeover tutorial explains why the first job with one inherited programme is an inventory, not a change. With two, the same rule applies twice, and a third problem appears: the two programmes overlap. They may bid against each other for the same searches, mail the same customers, run competing promotions and report the same sale twice.
The failures are rarely dramatic on the day. A list is merged and the record of what each person agreed to stays behind in the old tool. A website is redirected to the parent's homepage and the acquired business's organic enquiries drain away over a quarter. A tag is removed with the old site and nobody notices until the monthly report. A customer of the acquired business receives a welcome email from a company they have never heard of. Each is preventable by doing the work in an order where every decision is made before the work that depends on it.
| Area | What each business usually brings | Where the method lives |
|---|---|---|
| Brand | A name, identity and reputation with its own customers | Brand architecture and the rebrand rollout tutorial |
| Websites | A domain, pages, links and search visibility | Microsites and multiple domains, and site migrations |
| Customer data | A CRM, lists, consent records and opt-outs | Moving to a new CRM, and list building and consent |
| Paid media | Ad accounts, conversion tracking and history | The Google Ads and Meta Ads audit checklists |
| Tools and suppliers | Platforms, contracts and agencies | Retiring a marketing tool, and agency offboarding |
| Plans and numbers | A calendar, promises to customers and a baseline | The campaign calendar and the measurement plan |
Before you start
- The deal is complete and announced. Planning can start earlier among the people allowed to know; when customer-facing changes, list use and account access may begin is a question for the business's advisers, along with the deal itself, contracts, staff and competition rules.
- A sponsor who can decide. Integration decisions cross both leadership teams. Name the person who settles disagreements about brand, budget and priority, and agree how quickly they will decide.
- Access to both programmes. Admin access to every account, site, tool and file of the acquired business, or a named person there who has it and will stay through the move. The access step of the takeover tutorial applies before anything else.
- Someone who handles data protection. Combining customer data is the step most likely to need their view, so involve them from the start rather than at the moment of the first send.
- Time in the calendar. An integration competes with both businesses' normal campaigns. Mark the weeks the team will spend on it and the busy periods it must avoid, before anything is promised to leadership.
The steps
Inventory both programmes side by side
Run the inventory from the takeover tutorial for each business, into one sheet with a column for each: accounts and their owners, websites and domains, tracking and the events it records, live spend and commitments, contracts and agencies, creative and brand assets, customer data and where consent is held, and what the calendar already promises. Then add the rows that only appear when two programmes meet: searches both businesses bid on, customers who appear in both lists, pages on both sites that answer the same question, tools that do the same job twice, and agencies whose scopes overlap. Record for every row which business owns it today, who has access, and what depends on it. The inventory is also the first entry in the integration's Change LogA dated record of changes made to tracking, accounts, reports, lists or rules, with who made each and why, so later movements in the figures can be traced..
Settle the brand structure before anything else
Almost every later step depends on whether the acquired brand stays. The brand architecture guide sets out the four options for an acquired brand: keep it apart, put the buyer's name beside it, phase it out over a set period, or fold it in at once. It names the honest input, which is what the acquired name means to the people who buy from it, and notes that a tracking survey can estimate that before the decision rather than after; the acquired name's Branded SearchSearch queries that contain a company's or product's brand name. volume, read beside the survey, shows how many people still look for it by name. Whether either identity needs a refresh at the same time is a separate decision for the guide to a brand refresh or a rebrand. Write the decision down with its timetable. If a name is to change, the move is run later with the rebrand rollout tutorial, which this tutorial does not repeat.
Name one owner per decision and set a freeze
List the integration decisions (the brand, the website, the CRM, each ad platform, email, agencies, tools, the combined calendar, reporting) and give each exactly one accountable person, with the people who must be consulted and those who only need to be told. The RACI matrix is the usual format, and its rule of one accountable role per row matters more here than in most projects, because two leadership teams each assume the other is deciding. Then set a Change FreezeA set period around a peak when changes that are hard to reverse are stopped while routine, reversible work continues through an agreed route. on both programmes: no new tools, no new campaigns beyond the calendar already promised, no site redesigns and no list imports until the move for that area has been planned. Record who may approve an exception. The phase-gate reviews framework is the habit of deciding beforehand what has to be true for each move to go ahead.
Join the two measurement baselines
Before any account, site or tool changes, record where each business stands: enquiries, orders and revenue from the systems that record money, traffic by source, searches for each brand name, list sizes and the results of each paid channel. Write down how each business counts a lead, a sale and a customer, because the definitions rarely match, and decide the combined definition in the measurement plan. Mark every break the integration will cause in the measurement change log: a tag that moves, a property that closes, a definition that changes. The guide to comparing periods explains how to read a figure across a break in tracking or definitions, which every report in the coming months will need. Keep both baselines, not only the combined one: the acquired business's own figures are the only way to see whether the move has cost it customers.
Combine lists without losing consent or objections
Treat the acquired business's contacts as an import, however familiar the customers seem. The list building and consent guide puts the question for any imported file plainly: whether the people on it said yes to this sort of message from this business, with proof that they did. It summarises the GDPR's requirements that consent be demonstrable and no harder to take back than it was to grant, and that people may object to direct marketing at any time, and the ICO's direct marketing guidance on when consent is needed and on an opt-out in every message. The tutorial on restarting a dormant list answers the acquired-list case directly: the sign-up promise decides whether people agreed to hear from the business that now owns their record, so rebuild the Consent RecordThe stored evidence of a marketing permission: the channel, the wording the person saw, the date and the source of each opt-in, kept with the contact record. for those addresses, ask again or suppress where there is doubt, and get a decision from whoever handles data protection before the first send. Combine both businesses' suppression listsA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints. before any contact moves, so that a person who objected to either business stays suppressed in every tool; the consent map records which system holds each permission, and the opt-out request SOP is how a new objection reaches all of them. Moving records between CRMs follows the CRM migration tutorial, which carries source, consent and suppression across intact, and a list loaded into an existing CRM follows the import tutorial, which stops an import overwriting what is already there.
Decide which accounts, tools and agencies continue
For every overlapping account, tool and supplier, decide which one continues, which is retired and when. Paid media accounts are reviewed before anything is merged or rebuilt: the Google Ads account audit checklist names inheriting an account in a merger as a reason to run it, and the Meta Ads audit checklist covers ownership, events and structure in the same way. Each platform's own help pages decide what can be moved or linked, so read them before promising a date. Tools that do the same job twice are retired with the tutorial on retiring a marketing tool, which finds every dependency and export before the contract ends. An agency that will not continue is offboarded with the agency offboarding checklist, which confirms the business owns every account and asset first. Agencies that do continue need one plan, one calendar and one set of measures, as the guide to coordinating several agencies sets out, and the shape of the combined team is a question for the guide to team models and organisation design. Rename everything that continues under one Naming ConventionAn agreed pattern for naming campaigns, ads, events and tracking parameters so that reports can group them reliably., with a marker for campaigns created before the merger.
Merge or link the websites
The brand decision sets what happens to the acquired business's website. A brand kept separate keeps its site, and the work is to stop the two sites competing for the same searches. A brand that is absorbed or migrated means a site merge, which the guide to microsites and multiple domains treats as a site move: inventory each site separately, decide per page whether it merges, moves or retires, keep the old name findable with a page that explains what happened to it, change one thing at a time, and keep the old domain registered and redirecting. The site migrations guide holds the mechanics, the website migration checklist the sequence, and the redirect map template the one-to-one permanent redirectsA permanent server redirect telling browsers and search engines a URL has moved for good. from every old address to its new equivalent. Business listings and citations then change from one Source of TruthThe system whose figure is treated as authoritative for a given number, such as billing for revenue or the CRM for pipeline, with other tools reconciled to it., as the citations and NAP guide describes, once the address, phone number or name customers see has actually changed.
Combine the calendars and keep both sets of promises
Lay both businesses' plans on one campaign calendar: the always-on activity, seasonal peaks, launches, content and promotions each had planned. Every promise already made to customers stays, whichever business made it: an announced sale, a loyalty reward, an event with bookings, a price held for existing customers. Where two promotions now collide or contradict each other, decide which runs and how the other's customers are treated, and record the decision. Then find the weeks when the integration work itself will take the team's time, and keep the busiest trading periods free of website moves, list changes and account rebuilds. Risks that could derail the integration, such as a key person leaving, an agency's notice period or a consent question unresolved, go into the marketing risk register with an owner and a warning sign.
Tell each business's customers what changes for them
Customers care about what changes for them, not about the deal. Write separately to each customer base, from a sender name they already recognise, and say what is changing, what is not, when, and what they need to do, if anything. The acquired business's customers usually have the most questions: who now holds their account and data, whether their prices, contacts and service stay the same, and whether they will start receiving a new kind of message. If a sending domain changes, the deliverability guide explains why a new domain starts without a reputation and why volume should grow gradually. Tell staff and partners first, with the same facts and a short script, because they will be asked before any email is read.
Move channel by channel and read each move against both baselines
Move one channel at a time, in the order the freeze and the calendar allow, with a go or no-go review before each move against criteria agreed in advance. After each move, read the acquired business's figures against its own baseline as well as the combined figures against theirs, using the breaks recorded in the change log. A fall confined to one business after one move points to that move: missing redirects after the site merge, a tag left behind with an old property, a sender name customers did not recognise. Fix it before the next move starts. When every channel has moved, run a clean-up pass on the inventory: open rows, old names still visible, tools still billing, access still held by people who have left, and close the integration's section of the change log with a note of what was decided and why.
Which decision waits for which
Most integration mistakes come from doing a step before the decision it depends on. The order below is the reason the steps run as they do; when a team is under pressure to show progress, it shows which work can start safely and which must wait. The academy exercise on absorbing a smaller rival's paid programme for a cloth nappy maker practises this ordering for paid media after an acquisition: working the overlap rows, freezing both programmes with one approver, keeping two baselines and gating the new CRM connection before any customer record moves.
| Work | Waits for | Why |
|---|---|---|
| Website merge or redirects | The brand decision | Whether a site survives depends on whether its brand does |
| Any account, site or tool change | Both baselines recorded | Without a before figure, a loss cannot be seen or attributed |
| Mailing the acquired business's customers | Consent records rebuilt and suppression lists combined | Who may be mailed, and with what, depends on what they agreed to |
| Retiring a tool | Exports, dependencies and consent records moved | A retired tool can hold the only copy of a permission or a history |
| Ending an agency | Ownership of every account and asset confirmed | An agency can leave with access the business needs |
| Renaming anything customers see | The rebrand rollout plan | Surfaces seen together change together |
| The combined promotion calendar | Both businesses' existing promises listed | A customer promised an offer keeps it whatever the merger decided |
A window blind maker absorbs a smaller rival (illustrative)
Zandoriq Blinds absorbs a smaller blinds maker
Zandoriq Blinds, an invented maker of made-to-measure window blinds with 2 showrooms and a busy website, buys a smaller blinds maker in the neighbouring region. The acquired business has its own website on a domain it has used for 11 years, an email list of 6,400 contacts, a Google Ads account run by a local agency, a separate email tool and a spring promotion already announced to its customers.
The inventory finds 74 rows, 19 of them overlaps: both businesses bid on 140 of the same search terms, 820 customers appear in both lists, and the two email tools do the same job. A tracking survey and the acquired name's branded searches show that the name matters to its existing customers, so the brand team chooses to migrate it over 12 months, endorsed as "a Zandoriq Blinds company" in the meantime. One accountable owner is named for each of 9 integration decisions, and a freeze starts across both programmes.
| Area | Decision | When |
|---|---|---|
| Brand | Migrate the acquired name, endorsed for 12 months | Decided in month 1 |
| Customer data | Rebuild consent records; 1,900 contacts with no record left out pending advice; both suppression lists combined first | Month 1 |
| Paid search | Keep Zandoriq's account, audit the acquired one, move its best campaigns across, end the overlap | Month 3, weeks 1 to 2 |
| Keep one tool; retire the other after exports | Month 3, weeks 3 to 4 | |
| Agency | Offboard the acquired business's agency after confirming account ownership | Month 4 |
| Website | Merge the acquired site page by page with 310 redirects | Month 5, after the spring offer has run |
| Promotion | Honour the acquired business's announced spring offer in full | Month 2, kept free of other moves |
No more than one channel moves in any fortnight, each after a go or no-go review.
Baselines are recorded for both businesses before anything moves: the acquired business averaged 210 enquiries a month over the previous year. After the website merge in month 5, its region's enquiries fall to 150. The change log points straight at the merge, and a check of the redirect map finds 46 gallery and fabric pages sent to the homepage instead of their equivalents. Once they are mapped one to one, enquiries recover to 205 within 2 months. By month 12 the old name's searches have fallen to a third of their starting level, and the clean-up pass closes the last 6 open rows of the inventory.
Common mistakes
- Starting with the logo. Merging websites, accounts and lists before the brand decision forces every piece of work to be done twice.
- Mailing the acquired list as if it were your own. Customers agreed to hear from the business they joined; rebuild the consent records and ask whoever handles data protection first.
- Merging suppression lists last. A person who objected to either business must stay suppressed in every tool from the first day of the combined programme.
- Changing everything in one week. A site merge, an account rebuild and a list import together make every loss impossible to trace.
- Keeping only the combined baseline. Without the acquired business's own figures, a loss among its customers is hidden by the parent's numbers.
- Redirecting the acquired site to the homepage. Every old address should point to the page that replaces it, and the old domain is kept and kept redirecting.
- Cancelling the other business's promises. An announced offer or a held price is a promise to customers, not a line in the old plan.
- Ending an agency or a tool before collecting what it holds. Accounts, histories and consent records can leave with them.
- Declaring the integration finished when the last channel moves. The clean-up pass and the comparison with both baselines are part of the plan.
