The buyer wants to tie our earnout to customer retention metrics, but they plan to migrate our clients to their legacy ERP system. How do we protect our earnout payout from being penalized by technical migration delays that are completely out of our control?

Question

Tyler Smith · Accepted Answer

Tying an earnout to operational metrics like customer retention is highly risky when the buyer plans to integrate your systems post-close. System migrations are notoriously prone to delays, data loss, and operational friction that can cause temporary customer dissatisfaction, which will wipe out your earnout through no fault of your own.

To protect your payout, you must negotiate strict operational covenants in the purchase agreement. First, specify that any customer churn directly associated with the ERP migration or other buyer-initiated system changes must be excluded from the earnout calculation.

Second, establish a clear protocol for the migration process. If the buyer fails to meet agreed timelines or causes operational disruptions, the earnout metrics must be automatically adjusted or deemed fully achieved for that period.

Third, maintain operational control over the customer success team during the earnout period. Use your Accountability Chart to keep your customer retention seats occupied by your own staff, running under your established processes, until the transition is complete.

Use your Level 10 Meeting™ to track integration milestones transparently. If a migration issue arises, bring it to the weekly IDS® portion of the meeting with the buyer's integration lead. Having these issues documented in real time provides the evidence you need to defend your earnout metrics if the buyer tries to penalize you for their operational missteps.