Taking over from your developers: the handover checklist

1. Get a full copy of the source code

   It should sit in an account your company owns, not one the developer controls. Ask for access, then confirm you can download it.

2. Take owner access to the hosting

   Wherever the software runs, the account should be in your name with your payment card, and you should be able to log in.

3. Check who the domain name is registered to

   If it is in the developer's name, have it transferred. A domain is the hardest thing to recover after a falling-out.

4. Download a recent backup of your data

   Customer records, orders, files. Hold a copy yourself and note the date.

5. List every outside service the software uses

   Payments, email, text messages, maps, AI services. Each has an account and a bill; each should belong to you.

6. Confirm the app-store accounts are yours

   Apple and Google developer accounts should be registered to your company. Moving an app between accounts later is slow.

7. Read your contract

   Find the clause on who owns the work, the notice period, and anything still owed. Know your position before the conversation.

8. Ask for a one-page "how to run it" note

   How to release a new version, where things are kept, what breaks most often. Even a rough page saves weeks.

9. Have the new team check what you have

   A short, independent review tells you what is solid, what is risky and whether to repair or rebuild, before you commit money.

10. Change every password once the handover is done

    Then remove the old team's access everywhere on your list. Tick each account off.

From Wope, the tech team for businesses that do not have one. wope.ai