Ask
74
@costbasis_carl ·

small sale agreed - the domain, the payment account and the play listing all move differently, what goes in the handover

Agreed a low five figure sale for a tool I've run for three years. Buyer is friendly, no lawyers, we're doing it on a two page agreement.

I naively assumed 'transfer the assets' was one job. It isn't. The domain has its own lock rules, the payment account apparently doesn't just change hands, and the mobile listing has a separate process with the store that neither of us has done before.

What did you put in the handover doc, and what bit you that I'm not thinking of yet? Particularly interested in the paying subscribers, since their cards are attached to my account and not his.

8 answers Share
Report

Answering anonymously — a moderator will review it first.

  • @tripodwobble · 4mo ago

    Write the handover as a runbook, not an inventory. Every credential, plus how you do the monthly things. The buyer is buying your habits more than your code.

    26
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @label_reader_lo · 4mo ago · 2 replies

    Subscribers are the hard part and you should sort them before anything else, because they decide the shape of the whole deal. Payment accounts are tied to the legal entity behind them. If the entity itself changes hands that's one story; if the buyer is a different entity entirely, then in the normal case they open their own account and you migrate.

    Ask the processor directly, in writing, before you sign. There is a documented path for business sales and they'll tell you which one applies to you. Stored card data can often be migrated between accounts on request, but it's a process with compliance checks, not a button - budget weeks, not days.

    41
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @gramgrader_gus · 4mo ago

      And put a clause in the agreement about what happens if the migration gets refused. That's the thing a two page agreement always misses.

      18
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @goroutine_gil · 4mo ago · 2 replies

    One push back: don't do it on two pages just because you're friendly. You need three specific clauses. Who answers support for the first 30 days and how many of your hours that is. What happens to refunds and chargebacks on transactions made before the sale. And a line saying nobody transfers customer data anywhere your privacy policy doesn't allow.

    The last one sounds like lawyer noise and isn't. Your users agreed to a policy that named you.

    22
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @visible_stitch · 4mo ago

      Chargebacks on pre-sale transactions are the classic surprise. They land months later and they land on the old account.

      9
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @warranty_wes · 4mo ago · 2 replies

    Practical list from doing this twice. Domain: expect a lock window after any registrant change - the standard one is 60 days and it will absolutely be what delays your handover if you edit the contact details first and think about the registrar transfer second. Push the transfer first, edit contacts after.

    Mobile listing: the store has a formal app transfer that needs both developer accounts active and the original registration transaction IDs for each, plus a review on their side that isn't instant. Earnings and payout report history doesn't come with it. Email: whoever owns the sending domain owns its reputation, and a new sender on an established domain is a fresh warmup problem.

    33
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @pgpolicy_nadia · 4mo ago

      The transaction ID requirement catches everyone. It's in the receipt from when the developer account was first registered, which for an old account might be in an inbox you no longer own.

      14
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @darning_dot · 4mo ago

    Tiny thing that cost me a week: the transactional email provider verifies your sending domain with DNS records, and when the buyer moved the domain everything silently stopped sending. Password resets, receipts, all of it. No error anywhere except a dashboard neither of us was watching.

    Make 'sign up end to end with a real address' the literal last line of the handover, and do it together on a call.

    12
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report