Online Business Handover Checklist
By Graham Ashler · Last checked October 2026
Founder & Editor · Deal Field Guide
The Online Business Handover Checklist turns a signed deal into a business you can control: assign every asset and obligation, agree the permitted transfer steps, test payments and service under the new owner, and follow the contract's release conditions. Receiving passwords does not prove ownership, working billing or permission to keep earning.
The awkward moment is after the seller says, “You have everything,” and before you discover which things “everything” excludes. This checklist makes that sentence testable.
Use it as a shared document between buyer, seller and their advisers. Copy the tables or print the page. Do not put passwords, payment details or customer records into a shared checklist. Link to restricted records instead.
Best for: the period between an agreed transaction and the end of the seller's transition support. Settle first: whether the purchase covers assets or the legal entity, which liabilities follow, who coordinates closing, and the documents controlling delivery and payment. This checklist is not a substitute for those documents.
Online Business Handover Checklist: the master acceptance record
List each asset, its permitted transfer route and the exact test that proves the buyer has it. A green row needs both delivery and evidence. “Seller sent login” is not an acceptance test.
| Asset or obligation | Current owner | Receiving owner | Required permission or process | Delivery evidence | Acceptance test | Status / deadline |
|---|---|---|---|---|---|---|
| Domain registration | Enter | Enter | Registrar confirms route and locks | Registrar confirmation | Buyer controls renewal, contact and recovery | Enter |
| DNS, hosting and SSL | Enter | Enter | Provider account migration | Configuration and backup | Site works on buyer-controlled infrastructure | Enter |
| Files, database and code | Enter | Enter | Written rights; secure delivery | Repository/archive and rights schedule | Buyer restores backup and deploys | Enter |
| Content, brand and creative assets | Enter | Enter | Assignment or license rights | Signed schedule; editable files | Buyer can lawfully use and update assets | Enter |
| Store or application listing | Enter | Enter | Platform's permitted procedure | Platform confirmation | Buyer has required owner role | Enter |
| Payments and monetization | Enter | Enter | Provider approval or buyer account | Approved account/configuration | Legitimate transaction and payout route tested | Enter |
| Customers and data | Enter | Enter | Counsel-approved data transition | Data inventory and access log | Only authorized people can access it | Enter |
| Supplier and customer contracts | Enter | Enter | Consent/assignment where required | Signed consent or replacement contract | Service and terms continue as agreed | Enter |
| Staff and contractors | Enter | Enter | Their agreed continued engagement | Scope, rate and dates | Named coverage for next scheduled task | Enter |
| Refunds, credits and open orders | Enter | Enter | Purchase agreement allocation | Cutoff schedule | Owner and funding identified for each obligation | Enter |
| Seller support | Enter | Enter | Written scope and end date | Support schedule | Buyer knows how to raise a covered issue | Enter |
Use supported by the stated evidence, does not fit, unresolved, conflicting or not applicable in the status column. Do not turn “unresolved” into “done” to meet a closing date.
Agree who can do what before moving anything
One named coordinator should manage the sequence, while each party keeps its own responsibilities. A broker may coordinate a migration; that does not authorize it to override a platform's terms, a customer's contract or an escrow instruction.
Write the actual person's name beside each role in your private copy:
| Role | Responsibility | Confirmation needed |
|---|---|---|
| Seller / authorized account owner | Supplies records, grants permitted access, initiates required transfers | Has authority over every listed asset |
| Buyer / receiving account owner | Opens eligible accounts, accepts delivery, tests operation | Can operate and fund the business |
| Closing coordinator | Maintains schedule and issue log | Who has authority to change timing? |
| Legal advisers | Deal structure, rights, data, assignment and release documents | Who signs each document? |
| Accountant / bookkeeper | Cutoff, receivables, inventory, refunds and cost allocations | Common accounting definitions and currency |
| Technical operator | Backup, deploy, DNS, integrations, monitoring and recovery | Access and rollback plan agreed |
| Escrow or funds holder | Holds and releases money under its instructions | Exact conditions, deadlines and dispute route |
Before the first transfer, write down the dependencies. For example: backup verified → receiving hosting ready → copy tested privately → DNS change → live tests → access cleanup. That is an example sequence, not a universal closing instruction. Your parties and funds holder must agree the order for the actual assets.
Never remove the seller's access early because a generic checklist says to. Never leave it open indefinitely either. Agree the least access needed during transition and the event that ends it.
Check the account rules before you set a closing date
Some accounts allow a formal ownership change, some need provider help, and some cannot be transferred. Treat that as a deal-design question before it becomes a deadline problem.
These are Provider published terms (dated), checked October 24, 2026. They describe public procedures, not approval for your particular transaction.
| Platform or asset | What the official guidance establishes | What your handover must settle |
|---|---|---|
| Domain | ICANN distinguishes changing registrant from changing registrar; transfer locks can affect sequencing | Ask the actual registrar about this domain's lock, ownership and account-change route before editing contact details. ICANN |
| Shopify | Only the store owner can transfer it. Shopify Capital or Credit prevents transfer; active Balance needs emptying and Support assistance. Payments business changes also need Support | Store ownership, custom domain, billing, bank details, apps and payment providers need explicit treatment. Plus stores may require a different route. Shopify |
| Stripe | An existing owner selling the business should contact Stripe Support to establish required changes; cross-country acquisitions follow a different process | Confirm your entity, country, owner, tax, customer-facing and payout changes; do not assume moving subscriptions to another account is included. Stripe |
| Google AdSense | Account ownership transfers are not permitted | Plan lawful monetization under the buyer; do not buy a personal login as the payout plan. Google AdSense |
| Google Analytics, Ads and Merchant Center | Google publishes administrator-access procedures for transfer | Confirm relevant accounts, properties, linked services, billing and recovery; then remove obsolete access as agreed. Google |
| iOS app | Apple has a formal transfer subject to criteria; an eligible app retains ratings, reviews and Bundle ID | Transfer code and build assets separately. Test subscriptions and special capabilities. Apple Pay merchant IDs do not transfer with the app. Apple |
| Affiliate, ad-network, supplier and customer relationships | No single rule applies to them all | Get the actual agreement and written permitted route; record reapproval, changed rates and any non-transferable rights |
| Amazon businesses and publishing catalogs | A business sale is not itself an account permission | Obtain the platform-specific permitted route for the exact structure. We did not verify an Amazon account change for a particular deal |
A 60-day registrar lock is not necessarily a 60-day inability to control the website. Changing registrar, changing registrant and changing hosting are separate actions. Ask the registrar which combination is available and have the deal documents match it.
My view: “We will sort the account later” is an expensive line to leave in a deal. If that account earns most of the income, its allowed transfer route belongs beside the price, not at the bottom of the task list.
Before cutover: preserve what works and record the cutoff
Make a recoverable copy and a clear financial starting point before changing live systems. You need to know both how to restore service and who owns money earned around closing.
Business and technical preparation
- Confirm the final asset and exclusion schedules against the purchase agreement.
- Record the legal/business owner of each account, not just the person who knows the password.
- Confirm provider approvals, consents and receiving-account eligibility.
- Export the reports each party may lawfully retain. Avoid unnecessary customer data copies.
- Capture the domain, DNS, email, hosting, billing, software and integration settings.
- Back up files, database and code; verify that someone can restore them.
- Test a deploy or restore on a private environment where appropriate.
- Inventory API keys, certificates, webhooks, renewals and recovery methods without exposing secrets in the checklist.
- Record scheduled tasks, subscription billing runs, open support tickets, open orders and inventory commitments.
- Name the person handling the first failed payment, refund, supplier problem or outage.
- Agree a change freeze or approval rule for major changes during migration.
- Write down rollback triggers and the person authorized to act. Some completed account transfers cannot simply be reversed.
Financial cutoff record
| Line at agreed cutoff date/time | Amount or count | Belongs to / funded by | Evidence and settlement date |
|---|---|---|---|
| Cash included or excluded | Enter | Enter | Agreement definition |
| Receivables and unpaid payouts | Enter | Enter | Platform ledger and cutoff report |
| Pending refunds and chargebacks | Enter | Enter | Case list and contract allocation |
| Annual subscriptions already paid | Enter | Enter | Future service obligation schedule |
| Gift cards, credits and warranties | Enter | Enter | Outstanding liability report |
| Inventory on hand and in transit | Enter | Enter | Count, condition and valuation basis |
| Open purchase orders | Enter | Enter | Supplier confirmation and deposits |
| Accrued software, staff and tax bills | Enter | Enter | Statements and agreed allocation |
| Holdback or escrow retention | Enter | Enter | Amount, release test and deadline |
For U.S. asset purchases, ask the accountant about purchase-price allocation. The IRS says Form 8594 applies to buyers and sellers of qualifying groups of business assets when its conditions are met. That is a reporting question for the actual structure, not a tax calculation this checklist can do. Provider published terms (dated), checked October 24, 2026: IRS Form 8594 guidance.
During cutover: test the business under the buyer
The acceptance test is whether the buyer can run the relevant function through its own authorized setup. Seeing the site online proves little if its renewal still depends on the seller's card.
| Function | Practical test | Record to retain |
|---|---|---|
| Ownership and recovery | Buyer can reach owner settings and its own recovery methods | Role/ownership confirmation; no secrets |
| Website and checkout | Representative pages, forms and permitted test checkout work | Time, result and issue reference |
| Payments | Approved payout destination and legitimate transaction flow are correct | Provider confirmation and trace identifier |
| Delivery | An order, download, subscription or support request completes | Fulfillment/test record |
| Transactional messages arrive; support inbox works | Send/receive result | |
| Recurring services | Renewals and payment authorizations use the intended entity | Billing schedule and next charge |
| Software | Buyer deploys a small tested change or restores a backup | Deploy/restore log |
| Analytics | Measurements continue and buyer controls access | Account/property confirmation |
| Security | Access and key rotation follow agreed sequence | Access register and dated completion |
| Customer promises | Refunds, credits and prepaid service have an owner | Obligation register |
Use provider test modes where appropriate. Do not create fake orders, reviews or payments that violate a platform's rules. Confirm what a test establishes: a successful test checkout is not a future payout guarantee.
Escrow: the deadline is part of the checklist
Know when the inspection period starts, when it ends, and what happens if you do nothing. Escrow is a defined payment arrangement. It is not a guarantee of future earnings or an indefinite right to withhold payment.
Escrow.com's official FAQ says its agreed inspection period starts on receipt or confirmed delivery, can end when the buyer accepts, and can lead to release when the period expires without action. Its published range is 1–30 calendar days, agreed at the start. Provider published terms (dated), checked October 24, 2026: inspection-period rules. Other funds holders and arrangements have their own rules.
Write this block into your private closing record:
| Release item | Entry |
|---|---|
| Funds holder and governing instructions | Name and exact documents |
| Transaction reference | Private reference |
| What counts as delivered | Exact assets and evidence |
| Inspection starts | Date, time, zone and trigger |
| Inspection ends | Date, time and zone |
| Authorized acceptance/rejection method | Exact platform/process |
| Who monitors it | Named person and backup |
| What unresolved issues require action | Issue references and agreed process |
| Holdback conditions | Separate amount, tests, date and dispute path |
A message to the seller is not necessarily formal rejection under the funds holder's instructions. Follow the actual process in time, with your advisers where needed.
Fictional handover: the site works, but the payout does not
The case below is invented (User assumption) to show a useful stop point. It is not a report of a deal we handled.
A content site is being sold for $150,000. The parties' fictional agreement calls for $140,000 at the initial release and a separate $10,000 holdback subject to defined post-transfer conditions. Stock is not involved. No earnout or seller loan is added. The total consideration remains $150,000, not $160,000.
| Claim or task | Fictional evidence | Result | Remaining question / decision |
|---|---|---|---|
| Buyer controls the domain | Registrar confirms receiving account; buyer tests DNS | supported by the stated evidence | Record renewal and recovery |
| Website delivered | Buyer restores backup and site works | supported by the stated evidence | Monitor live functions |
| Affiliate income continues | Seller says account is included; program has not approved buyer | unresolved | Get permitted route; do not mark monetization accepted |
| Seller's personal bills removed | Hosting and email now use buyer billing; analytics tool still uses seller card | conflicting with “all billing complete” | Correct tool billing before seller cancellation |
| $140,000 release authorized | Agreement requires specified acceptance tests; one is unresolved | unresolved | Coordinator and counsel follow agreed instructions before deadline |
| $10,000 holdback payable | Separate conditions and date not yet met | unresolved, not an extra price item | Track exact condition and due date |
The checklist does not give the buyer a new right to delay money. The agreement and funds-holder rules do that. Its job is to put the unresolved payout problem in front of the right people before they click acceptance or miss a deadline.
After handover: end dependency on the seller
The transition is complete when the buyer can handle ordinary work and knows how to address exceptions. A support promise with no hours, scope or end date is difficult for both parties.
Agree the following in writing:
- Covered tasks, training sessions and excluded new development.
- Who answers, through which channel, and within what agreed response time.
- Dates, hours and any paid extension rate.
- Training recordings or process documents the buyer may retain.
- Access the seller keeps, why it is needed, and when it is removed.
- A list of open issues with owner, evidence and completion date.
- Final accounting settlement, including refunds, payouts and stock adjustments.
- The process for disputes or a failed transfer, rather than an improvised threat to reverse changes.
Field Notes — Operator experience: the first exception often reveals more than the smooth demo. The first expired affiliate offer, failed app renewal, broken integration or late supplier order shows whether the process lives in a document or in the seller's head. Ask the seller to explain a real past exception and show the records. For Shopify and ecommerce transfer specifics, our basis is research, not firsthand ownership of a Shopify store.
Deal Decision Check: your requirement is working, permitted control of essential assets. Your evidence is the register plus completed tests. Your rule is that each essential function needs its own supported result. One unresolved essential payout path keeps handover acceptance unresolved; ten completed minor rows do not average it away. The next step is the contract's agreed resolution process.
If you are still deciding who should coordinate this work, the provider comparison shows how transaction responsibilities differ. We publish guidance; we do not run migrations, hold funds or review individual deals.
How this checklist was checked
Deal Field Guide is published by Kozi Publishing LLC. Graham Ashler is its publisher's editorial pen name. The publisher has operated content/affiliate businesses, Amazon FBA, KDP, SaaS, iOS apps and YouTube channels, and has not worked as a broker or bought or sold through the covered marketplaces.
Deal Field Guide helps you buy or sell an online business with clear eyes — comparing the real routes, showing the money after fees, and telling you what owning each kind of business is actually like, with the source behind every number.
Research note: checked October 24, 2026. We read the public platform, domain, escrow and IRS pages below and built the example and working records. Their published rules are not approval of any individual transfer. We did not access private accounts, test a live acquisition or assess a particular data transfer. Software, including AI, may assist research and drafting; we remain responsible for the published copy. See our methodology.
This is education, not legal, tax or investment advice.