Re licensing the carved out business from scratch.

Re licensing the carved out business from scratch means giving the new standalone entity its own software contracts, sized to its own usage, instead of borrowing the parent entitlements it can no longer legally rely on. Done well it resets the cost base for years and removes inherited audit risk. Done as a last minute scramble it locks in list price terms and stranded commitments that take a full renewal cycle to fix.

Why re licensing the carved out business from scratch is unavoidable

Most software licences are not freely transferable. Enterprise agreements, named user licences and SaaS subscriptions carry assignment and change of control clauses that limit what can move to a new owner without the publisher consent. When a unit is carved out, the cleanest legal position is rarely to drag the old contracts across. It is to stand up fresh agreements that belong to the new entity, govern its actual deployment, and carry none of the parent baggage. That is what re licensing from scratch means in practice.

The alternative, relying on the parent contracts through a transition services agreement, is a temporary bridge, not a destination. Every TSA has an end date, and the software critical path inside it is unforgiving. If the new entity reaches that date without its own contracts in place, it faces an access cliff. Re licensing is therefore not optional housekeeping. It is the work that lets the business keep running on the day the TSA stops.

The four stages of a clean re licensing programme

Re licensing works as a sequenced programme. The first stage is a full inventory of what the carved out unit actually runs, captured from deployment data rather than the parent contract schedules, which describe the whole company. The second stage is the entitlement gap, the difference between live usage and any rights the new entity can legitimately claim. The third stage is sequencing, because not every contract carries the same urgency. The systems on the operational critical path, usually identity, ERP and core line of business applications, are licensed first. The fourth stage is signing standalone paper sized to real demand.

Each software category has a different fastest route and a different point of leverage. ERP and database estates are usually right sized away from the parent over provisioning. Productivity and identity move to a fresh tenant. SaaS applications transfer or re contract according to each publisher consent terms. The table below maps the practical options.

This sequencing is the heart of our carve out and TSA separation service, and it ties directly to standing up the new entity software estate.

The mistakes that turn re licensing into a scramble

Re licensing fails in predictable ways. The first failure is starting from the parent contract schedules instead of deployment data. The schedules describe entitlements bought for the whole company, so a buyer who treats them as the shopping list over buys from the first signature. The second failure is leaving consent dependent transfers until late, when vendor response times no longer fit the TSA runway. The third is sequencing by convenience rather than criticality, signing the easy low risk tools first and discovering too late that identity or ERP, the systems with the longest lead time, are still uncontracted as the TSA exit approaches.

A short composite shows the stakes. A buyer carving out a regional services business assumed re licensing was a procurement exercise it could run in the final quarter of a twelve month TSA. Identity and ERP were left until the contracting team had cleared the smaller subscriptions. When the ERP publisher consent and migration testing took longer than the remaining weeks, the buyer faced a choice between an emergency TSA extension at the parent price or a rushed cutover that risked the financial close. The cost of that late start dwarfed any saving the careful procurement of smaller tools had produced.

The avoidable theme in every failure is the same. Re licensing is a critical path programme, not a purchasing queue. The contracts that gate operations come first, the verified usage baseline drives the quantities, and consent dependent items start early because they are the least controllable. A buyer that holds those three disciplines reaches the TSA exit with the estate it needs and a cost base below the parent run rate.

Turning a forced reset into a buyer advantage

Re licensing is a rare moment of leverage. The new entity is a green field. It is not locked into the parent metrics, its over deployment, or its legacy bundles. A buyer that treats re licensing as a strategic reset can right size every commitment to genuine usage, run competitive bids before the TSA ends, and consolidate overlapping tools into single contracts. A buyer that treats it as a procurement formality tends to clone the parent estate at list price and inherit the same waste the carve out was supposed to leave behind.

The discipline that protects this advantage is the same deployment to entitlement reconciliation we use to find stranded software costs. Measure first, then buy. Re licensing from a verified usage baseline almost always lands below the parent run rate, because the parent number carried slack that the new entity does not need.

Continue with negotiating software terms for the new entity and the TSA exit timeline and software critical path.