Taking over a client from another MSP?
Enter the client's domain. Public records show a lot of what the outgoing provider holds: registrar, DNS host, mail flow, the Microsoft 365 tenant, SaaS verified on the domain. Get it as a handover checklist and a letter the client signs.
Read from your browser: public DNS, RDAP and Microsoft's public sign-in metadata. Nothing is stored.
Want the outgoing MSP chased for you?
We're running a few takeovers by hand: the checklist shared with the outgoing provider, each item tracked until it's handed over, and reminders sent. Ask to try it.
Had a takeover go badly (or been the outgoing MSP)? Tell us what happened (4 questions, written, no call).
What it reads, and what it can't
- Public records: name servers (DNS host), MX (mailbox provider or gateway), TXT verification tokens (SaaS where someone proved the domain: each has an admin account), SPF senders, DMARC, www host, RDAP (registrar, expiry), Microsoft's tenant ID and whether sign-in is managed or federated.
- Can't see: firewalls, backups, RMM agents, licence channel or who holds which admin account. Those items are on every checklist anyway.
- Microsoft facts as of 2026-10-13: partner-to-partner licence transfers are requested by the new partner and approved by the current one in Partner Center within 30 days; customers remove a partner's admin roles in the Microsoft 365 admin center, but only the partner can end a reseller relationship. Not legal advice; check your contract's notice and data-return terms.
Built by Hieu Tran with AI agents. Not affiliated with Microsoft, Google, Pax8 or any vendor named here.