Post-Merger Integration under Georgian Law
Post-merger integration is an international consulting label, but its Georgian legal content is concrete: the mechanisms of the Civil Code govern the transfer of obligations after closing, the migration of encumbered assets and the unwinding of redundant long-term contracts. This page carries the post-closing contractual-continuity layer and is distinct from sibling pages on pre-signing structuring and on debt-transfer details. At the same time, the merger procedure itself is governed by the Entrepreneurs Law, which the page only names — here the civil-law integration mechanics are central; integration has no separate Georgian statute.
Transferring Obligations
The first legal step of integration is moving debts: under a contract concluded with the holder of the claim, a debt may be assumed by a third person — by assumption of the debt; the third person then takes the place of the original debtor. For integration planning this has a second half: the original debtor has the right not to consent to this agreement and to pay the debt itself — assumption can fail against the creditor's resistance. And where the third person and the debtor agree on assumption, its validity depends on the consent of the holder of the claim. In the integration plan this means: the schedule of obligations standing in the acquired company's name and the creditors' consents are the first worksheet; and since the creditor's resistance voids the assumption, the integration timetable must place creditor agreements before closing.
The procedure of assumption is bound documentarily to three points: the contract between the debtor, the new debtor and the holder of the claim; the determination of the fate of the pledge securing the claims; and the consideration of the debtor’s possible refusal — the law leaves it the right to object to the assumption. This last point often diverges: the integration plan builds on the transfer of a debt only where each debtor’s position has been verified separately.
Migrating Encumbered Assets
In moving asset groups a pledge is not lost: on the disposal of a pledged object, ownership encumbered by the pledge passes to the acquirer, and the acquirer receives the asset with its burden. With a registered pledge, upon disposal of the object the pledgor and the acquirer are jointly charged with updating the entry in the public registry. For integration planning this means that moving pledged property into the acquiring group demands more than a transfer act: the object's documents, the registry update and agreements with third persons are decisive. The code names exceptions as well: in possession-based pledge the pledge terminates upon disposal if the pledgee transfers possession of the object to the acquirer; and in disposal within the ordinary entrepreneurial activity unencumbered ownership passes to the acquirer — unless acquirer and pledgor acted in bad faith. The integration context thus decides the pledge's fate through the concrete construction chosen.
Unwinding Redundant Contracts
The third pillar of integration is the unwinding of legacy contracts: any party to a contract may, for a compelling reason, refuse the long-term contractual relationship notwithstanding the period established for termination. A compelling reason exists where, considering the concrete situation — including force majeure and the interests of both sides — the terminating party cannot reasonably be asked to continue the relationship until the agreed term expires. Where the reason is a breach of obligation, termination is admissible only after the fruitless expiry of the cure period or after a fruitless warning. In integration practice this instrument is the legal path to cleaning up redundant, duplicating contracts; to this is added that the authorised person retains the possibility to refuse within a reasonable period, and breach-based termination demands the fruitless expiry of a cure period or a fruitless warning — a procedural discipline the integration manager plans in advance.
The decision to unwind redundant contracts grows out of the integration plan: first the functionally duplicative contracts are identified, then the ground of breach of each is verified — a material breach and the futile expiry of the period — and finally the warning procedure is completed. A breach of sequence not only breeds a dispute: it creates a ground for a compensation claim, and the loss is here always measured by documentary precision.
What must be verified before transferring debts?
The complete register of claims, the fate of the pledge securing them, and the debtor’s position — the right of refusal remains with it.
Frequently Asked Questions
Below we summarise the questions that arise most often in practice on this topic.
How is a debt transferred into the acquiring group?
By a contract with the claim holder — assumption of the debt; the third person takes the debtor's place, and the original debtor retains the right to object.
What happens to pledged assets?
The pledge passes to the acquirer; with a registered pledge the registry update is jointly charged to pledgor and acquirer.
How is a redundant contract unwound?
For a compelling reason — upon breach, after the fruitless expiry of the cure period or a warning.
Does integration have its own statute?
No — its legal content is filled by the Civil Code's mechanisms; the merger procedure belongs to a separate law.
How We Help on Legal.ge
Our team will help with the legal part of the integration plan — inventorying and transferring obligations, migrating encumbered assets and running contract-unwinding procedures. Contact us on Legal.ge — we will carry the post-closing unification with legal risk under control.