Keep, merge, bridge or retire: a decision framework for every system
Every system in the inventory ends up in one of four places. Three questions decide which: is it still used, does the other company have an equivalent, and can you switch safely now?
Retire a system that is no longer used. Keep one with no equivalent on the other side. Merge when both sides do the same job and switching is safe: pick the winner and move people and data to it. Bridge when both do the same job but switching is risky or locked in for now: connect them and set a review date. Use the tool below on each system in your inventory.
Salesforce
HubSpotShopify
WooCommerce
QuickBooks
NetSuite
Slack
Microsoft Teams
Make
Decide one system
My decisions
| System | Decision |
|---|
How does the framework work?
Ask three questions in order. Not used: retire. No equivalent on the other side: keep. Equivalent exists: merge if you can switch safely now, otherwise bridge.
- Is the system still used and needed? If not, retire it after archiving its data.
- Does the other company run something that does the same job? If not, keep it.
- Can you switch within a reasonable window without unacceptable risk? If yes, merge; if not, bridge and set a review date.
When is bridging the right answer?
When a contract, a regulation, a close, a peak season or a deep integration makes switching too risky right now. A bridge is a decision with an end date, not a way to avoid deciding.
- Name the owner of the bridge.
- Write the conditions for revisiting it.
- Track it in the risk register.
How do you avoid endless debates?
Decide by the same three questions every time, record the answer and the reason, and escalate only when two owners disagree on a fact.
- Publish the decisions list so everyone sees the same answers.
- Choose winners on fit for the combined company.
- Re-run the tool when a contract date or a fact changes.
Questions on this topic
What if we cannot decide between merge and bridge?
Bridge, with a review date. You can merge later; a rushed merge is harder to undo.
Do the example decisions apply to us?
They show how the questions work. Your contracts, data and people may give a different answer.
Is the tool saving my answers?
No. It runs in your browser and nothing is sent or stored.
Vendor documentation to check against
Product details change. Confirm current options in each vendor's own documentation. Consultants in a Box is an independent consultancy; this page is not published or endorsed by any vendor named. Names and logos are trademarks of their owners.
Related guides
Day 1, 30 and 100 plan
Integration goes wrong when everything is urgent. Split the work into three checkpoints: keep the business running on Day 1, make the decisions by Day 30, and complete the moves by Day 100.
Read the guideIntegration patterns and iPaaS
You will not merge everything on Day 1, so you will bridge. A bridge you design (owners, logging, an end date) is an asset. One built from forgotten zaps is a risk.
Read the guideRisk register
Most integration failures are predictable. A risk register makes them visible early, with an owner and a mitigation each.
Read the guideAll M&A tech stack guides
The full playbook, from diligence to synergy capture.
See the hubMerging two stacks?
Start with the free business analysis, or book a call and we will talk through both companies' systems and where to begin.
