Post-closing integration: stages and deadlines
Post-closing integration is the sequence of steps that moves a licensed or assigned intellectual property right from the seller's records into the buyer's operating structure once a deal closes. It runs through fixed stages: notice, register update, sub-licensee handling, and system migration. Each stage carries its own deadline, and one of them marks the point after which reversal stops being practical.
What changes once the deal closes
Signing and closing are not the same moment as integration. Once payment clears, the licence or assignment agreement stops being a promise and starts being an operating fact. Notice periods begin running. Register deadlines start. Sub-licensees gain the right to ask questions, and some of them gain the right to walk away if a change-of-control clause was triggered.
Delay at this stage does not stop the clock. Most notice and recordal deadlines run from the closing date itself, not from the date someone gets around to sending the letter. A buyer who waits three weeks to notify a licensor has already used three weeks of whatever window the agreement allows.
The stages, in order
| Stage | What happens | Typical deadline | Who acts |
|---|---|---|---|
| Closing notice | Licensors, licensees and registry contacts are told that control has changed | within 5 business days of closing | Buyer's integration lead |
| Register update filed | Assignment or licence recordal is lodged with the relevant register | within 1 month of notice | Buyer's IP counsel |
| Sub-licensee review | Existing sub-licences are checked for change-of-control or consent clauses | 2–4 weeks | Legal team, with seller's cooperation |
| Systems and data migration | Licensed software, databases and related assets move into the buyer's environment | 4–12 weeks, depending on scope | IT and integration team |
| Point of no return | Consents obtained, registers updated, nothing left to unwind | marks the close of integration | Joint sign-off, both sides |
The last row is the one clients underestimate. Before it, a botched step can usually be corrected. After it, correcting a step means renegotiating, not amending.
What to do
- Confirm the closing date in writing and start the notice clock the same day.
- List every licence, assignment and sub-licence the transaction affects.
- Check each one for change-of-control or assignment clauses before sending notice.
- File register updates with the receiving authority without waiting for other stages to finish.
- Track every consent request and escalate silence early, not at the deadline.
- Record the point of no return in writing, signed by both sides.
Who decides, and how long it takes
The buyer's integration lead sets the internal timeline, but three other parties hold real decision power. Register authorities decide their own processing times and will not accelerate for a closing calendar. Counterparties decide whether to consent to a change of control, and silence from their side is a decision in itself. Disputes over any of the stages go to whichever forum the underlying licence or assignment agreement already names.
The team that runs these checks is not assembled overnight. How the team hires in detail sets out how integration specialists are brought in and vetted before they touch a live file.
If your file looks like this
If the portfolio includes trade marks currently under opposition, that item cannot close through the register step until the opposition resolves. How opposition proceedings trade mark runs in practice sets out how long that can take.
If the licensed asset is a database rather than software or a trade mark, the sui generis right needs a separate check before the register update is filed. Sui generis right in ownership of results explains what that check involves.
If any right in the portfolio sits on a distributed ledger, custody arrangements need confirming before migration starts, not after. Custody expectations in tokenised rights in practice covers what changed and who it affects.
What this page does not cover
This page starts at closing. It does not cover the checks a buyer runs before signing, and it does not set out what a decision-maker looks for in a chain-of-title review. It does not cover cost, and it does not tell you which register fee applies in your jurisdiction, because that depends on the specific register and asset involved. It also assumes the underlying licence or assignment is already valid; a defective agreement is a different problem with a different fix.
Reviewed
This procedure reflects our internal integration practice, reviewed on 2025-01-14. It describes typical sequencing and timing rather than a fixed statutory timetable, since integration steps are set by contract and by register practice, not by a single rule that applies uniformly across jurisdictions.
Frequently asked questions
How long does post-closing integration take in practice?
Straightforward files with a single jurisdiction and no sub-licensees usually close within six to eight weeks. Files with multiple registers, active sub-licences or unresolved oppositions can run several months.
Which documents are needed to start?
The closing agreement itself, the full list of affected licences and assignments, any existing sub-licence agreements, and current register extracts for each right involved. Missing extracts are the most common cause of delay at the register update stage.
What happens if the other side does not respond?
Silence does not pause the clock. Most agreements set a deemed-consent or escalation mechanism for non-response; where none exists, the buyer's team should document the attempt and move to the next stage on the planned date, flagging the gap rather than waiting indefinitely.
Related reading
For the stage before this one, Due diligence on chain of title step by step sets out what a decision-maker checks before signing, which is where most post-closing surprises originate.