IT handover checklist when you sell your business

When you sell your business, hand over every admin credential, tenant, domain, license and archive location against a written checklist signed off by both sides before closing. Record where historical email, ticket and file archives live so the new owner can still find them later.

What should a seller hand over in the IT transition?

A seller's IT handover should transfer every credential, tenant, domain, license and archive location the business depends on, and record where historical records live so the new owner can find them later. Do it against a written list, sign-off by both sides, and before final payment mechanics are settled where possible.

This checklist is for the owner, CFO or IT lead of a company being acquired. It also protects the multi-year records many companies hold, which stay useful long after closing.

Why a handover checklist?

Acquisitions lose access and knowledge in predictable ways: the one person who held the domain registrar login leaves, a Microsoft 365 or Google tenant is merged and old mailboxes are deleted, a legacy application is switched off to save a subscription. Each loss is cheap to avoid before closing and expensive afterwards. The seller also has duties: warranties about systems, cooperation covenants and transition services are set in the purchase agreement, so read yours with counsel.

The checklist

Accounts, admin access and identity

Named owner for each tenant: Microsoft 365, Google Workspace, identity provider
Global administrator accounts listed, with at least two current holders
Break-glass account created and its credentials stored with the new owner's agreed process
Multi-factor authentication devices and recovery codes transferred or reset
Shared and service account passwords moved into a password manager the buyer controls
Former employees' access removed and documented

Domains, DNS and email

Registrar account, domain list and renewal dates
DNS provider access and a copy of all records
Email routing, aliases and any third-party senders such as billing or marketing tools
Certificates and their renewal owners

Software, cloud and licenses

Application inventory with owner, vendor, renewal and contract terms
Cloud accounts for AWS, Azure, Google Cloud or similar, with billing contacts
Source code repositories and CI/CD access
Software licenses and any restrictions on transfer or change of control

Archives and historical records

Retired systems and where their exports are stored
Email archives, chat exports and shared drive snapshots with date ranges
Retention policies and legal holds in force
A person named to answer questions about each archive after closing
Owner personal data identified and handled; see the guide on removing owner personal data from company systems before a sale

Who does what, and when?

Timing	Seller's IT lead	Buyer's IT lead
Before signing	Build the application and account inventory	Review it and list questions
Between signing and closing	Close gaps, export archives, add second admins	Prepare accounts and password manager
At closing	Transfer ownership of tenants, domains and licenses	Accept and change credentials
First 30 days	Answer questions under any transition agreement	Confirm every system works and archives are readable

Put the schedule and the sign-off into the transition plan, and ask counsel how it relates to the cooperation covenants in the purchase agreement.

How to use the results

Result	What it means	Next action
One admin holds everything	Single point of failure at closing	Add a second administrator and document
Domain registered to an individual	Ownership could leave with that person	Transfer to the company account
Archive on a retired system with no export	Records may vanish when the subscription ends	Keep access or run a full export
License forbids assignment	Closing may need vendor consent	Ask the vendor early
Unknown account found	Possible shadow IT	Identify the owner or close it

Red flags

Cloud or SaaS accounts opened on personal emails
Admin credentials in someone's notebook or inbox
Retention settings that auto-delete after a short period
A migration scheduled in the weeks around closing; see the guide on selling a business with outdated technology
Customer or employee data stored where the buyer cannot lawfully receive it

Why archive locations matter beyond the sale

The older records in email, tickets, CRM and shared drives show how the business made decisions and what resulted. AI developers license that kind of material for training and evaluating agents. A company keeps ownership and licenses the data for a one-time payment, and nothing is binding until the company agrees price and terms and signs. Whether a license happens before, around or after closing is for the seller, the buyer and their counsel to settle. The data opportunity handoff checklist for a business sale covers that layer, and sector examples include selling a machine shop and selling a translation or localization company. Advisors can also read how AI data buyers fit into a buyer list.

Companies with 50+ full-time employees at peak (contractors excluded), years of documented operations and records across many systems are the ones that may qualify; see who qualifies or try the company fit checker for a preliminary, non-binding screen.

Next step

Preserve the archives first, then decide. Advisors and connectors can register as a partner to introduce a company, and owners can apply directly at sourcex.si/apply.

Step 1Share your linkSend your personal link to a company you know.
Step 2Company appliesThe company applies itself at /apply.
Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

Who should hold admin credentials at closing?

The buyer's named administrators should hold them, with at least two people and a documented break-glass account. Agree the transfer date in the purchase agreement or transition plan, and have the seller's IT lead remain reachable for questions. Never hand over credentials by email or chat.

Should I transfer the domain before or after closing?

Usually at closing or on a date set in the agreement, since the domain carries email and the website. Move it from any personal registrar account to the company's account first, record the renewal date, and keep DNS records documented so nothing breaks.

What happens to old mailboxes after an acquisition?

It depends on the buyer's plan and retention settings. Mailboxes may be migrated, archived or deleted. Ask for the retention terms in writing, keep exports of important date ranges, and check with counsel on legal holds and privacy duties before anything is removed.

Do I need to keep retired systems running after the sale?

Only if the archives cannot be exported another way or the agreement requires access. Often a complete export and a named custodian are enough. Confirm vendor terms, retention duties and the buyer's expectations before ending any subscription.

Can archived records still be licensed after the sale?

Possibly, if the company that holds the rights agrees, contracts permit it and someone can still export the records. Who holds those rights after closing depends on the agreement, so address it with counsel before closing rather than afterwards.

Free resources

Business succession planning assessment — Ten questions on successor, transition and documentation.
NPV calculator — Net present value with a discounted cash flow table.
Time value of money calculator — Future and present value with optional regular payments.
All free tools · MCP resource center

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment