How to Transfer a SaaS Business After Acquisition
Domain, hosting, payment processor, customer data — every transfer step explained.
Transferring a SaaS business after signing the asset purchase agreement (APA) requires a structured 30–45 day handoff that protects revenue, data, and customer trust. The process breaks down into seven sequential workstreams—domain & DNS, hosting & infrastructure, payment processors, code & credentials, customer data, team & contractor access, and post-close monitoring—that buyers must execute in parallel with the seller under strict escrow release conditions.
1. Secure Domain, DNS, and SSL Records
Start by moving the domain registrar account to the buyer’s preferred provider within seven days of APA signing. Update WHOIS privacy settings and extend registration for the maximum ten-year term to lock in brand protection. Simultaneously point nameservers to the buyer’s DNS provider (Cloudflare or AWS Route 53) while keeping TTL values low (300 seconds) for a clean cutover. SSL certificates must be re-issued under the buyer’s account; most acquirers on hades.ae report that certificate migration takes 48–72 hours and should be scheduled during the lowest-traffic window.
2. Migrate Hosting, Databases, and CI/CD Pipelines
Whether the SaaS runs on AWS, GCP, Vercel, or a managed Heroku successor, create new production environments under the buyer’s billing profile before any data sync begins. Use infrastructure-as-code (Terraform or Pulumi) to replicate the seller’s setup exactly, then perform a full database dump and restore using encrypted S3 or GCS buckets. Update environment variables, rotate all database credentials, and re-deploy via the buyer’s GitHub Actions or GitLab CI runners. Sellers typically grant temporary IAM “break-glass” access that auto-expires 14 days post-close to prevent lingering privileges.
3. Switch Payment Processors and Subscription Billing
Most SaaS acquisitions valued at 3–4× ARR on platforms such as Acquire.com or FE International involve Stripe or Chargebee accounts. Open a new Stripe Connect or merchant account in the buyer’s entity, then import customer payment methods via Stripe’s “Account Migration” or Chargebee’s “Migration API.” Keep the original processor live for 30 days to catch any failed webhooks, then issue prorated refunds and update all billing portal URLs. Escrow agents usually hold back 10–15 % of the purchase price until the first full billing cycle shows <5 % involuntary churn after the switch.
4. Transfer Code Repositories, Secrets, and Third-Party Integrations
Move GitHub or GitLab organization ownership and immediately enable SAML SSO under the buyer’s identity provider. Rotate every API key, OAuth token, and webhook secret listed in the data room; popular targets include SendGrid, Twilio, OpenAI, and Intercom. Document all third-party contracts with annual spend above $2,000 and assign them to the buyer via novation agreements within the first month. This step typically surfaces 15–20 credentials that the seller forgot to include in the original disclosure schedule.
5. Migrate Customer Data and Maintain Compliance
Export the entire production database and any S3-stored user uploads, then import them into the buyer’s isolated VPC. Run automated PII scans to confirm GDPR and CCPA compliance before go-live. Notify all active users via in-app banner and email 72 hours before the migration window, offering a 10 % loyalty credit to offset perceived risk. Benchmarks from MicroAcquire deals show that transparent communication keeps logo churn below 3 % during the transition quarter.
6. Onboard Internal Teams and Contractors
Transfer employee and freelancer accounts for Slack, Notion, Linear, and any monitoring dashboards. Schedule a two-week “shadow period” where the seller’s lead engineer remains available at $250/hour through an escrow-funded retainer. Update all incident-response runbooks and rotate PagerDuty or Opsgenie ownership so alerts route directly to the buyer’s on-call rotation by day 21.
7. Monitor Post-Transfer KPIs and Release Escrow
Track MRR retention, deployment frequency, and infrastructure cost per customer for the first 90 days. Provide the escrow agent with weekly snapshots; once 90-day revenue exceeds 95 % of the pre-acquisition run rate, the remaining holdback is released. Most buyers on Empire Flippers and hades.ae close this final milestone between days 75 and 85 when churn stays under 2 % monthly.
How long does domain transfer usually take?
Registrar-to-registrar transfers complete in 5–7 days; plan an additional 48 hours for DNS propagation and SSL re-issuance.
Who pays for the payment processor migration?
Standard APA terms assign all processor setup and migration fees to the buyer; the seller covers any chargeback liabilities arising before closing.
What happens if churn spikes after transfer?
If monthly churn exceeds 5 % in the first 60 days, buyers can claim against the 10–15 % escrow holdback, typically recovering 1–3× the lost ARR depending on negotiated terms.
Ready to acquire?
Browse curated digital platforms on hades.ae — every listing is built and owned by our team. View available platforms →