Software modernization
Preparing your company for a merger: the technology work that actually matters
Deal teams talk about revenue and headcount. Operators live in the software that invoices, schedules, and stores regulated data. This is the technology inventory Enterprise Technology Group uses when a company must keep working through a merger.
Published 2019-03-04 · Updated 2026-09-19
What should you inventory before letters of intent freeze the stack?
List systems of record, not logos. For each: who authenticates, where the data lives, which nightly jobs must complete, and what breaks if the vendor contract is not assumed. Duplicate CRMs and orphaned access-control lists are more expensive on day 90 than a missing banner on the website.
If two desktop products do the same warehouse job, that is a software modernization decision, not a branding decision. If both companies sell a multi-tenant product, treat the overlap as SaaS platform tenancy and billing — not a simple domain redirect.
How do you keep customers online while the legal entity changes?
Prefer dual-run over a weekend cutover. Keep identity, invoicing, and the primary workflow on the surviving stack. Wrap the rest with APIs. Public pages can wait. Field apps and native clients usually cannot — see iOS and Android app development when the surviving process lives on a phone.
Use the software scope estimator to sketch whether you are looking at a staged modernization or a net-new platform before anyone promises a 30-day merge of production data.
| Area | High-risk shortcut | Safer path |
|---|---|---|
| Identity | Share one admin password across both companies | Federate, then retire the weaker directory |
| Data | Copy production into a new schema over a weekend | Dual-run, reconcile, then cut a single workflow |
| Customers | Point DNS at a new brochure | Keep the live product URL stable; change legal copy later |
Continue with the software scope estimator, software development services, or request a project quote.