Who owns the CRM, automations and data you pay an agency to build?
You should, but it depends on whose name the accounts are in and what the contract says. With Autoesta, accounts are set up in your name and paid by you, and for custom software the code and documentation are handed over on completion as set out in the contract. Before hiring any agency, check four things: account ownership, admin access, data export and a written transfer of rights.
Ownership gets messy because modern systems are rented, not bought. Your CRM, phone numbers, domain and automation tool each live in someone's account, and whoever holds the account controls it. If an agency builds everything inside its own account and you part ways, you can end up asking permission to reach your own customers.
This page is general information for business owners, not legal advice. For anything with significant value, have a lawyer read the ownership clause of your contract.
Which parts of a system can you actually own?
A typical automation system has six parts, and each has its own owner: the CRM account, the data inside it, the phone numbers, the domain and email sending setup, the automation tool account, and any custom code. Ownership of one does not imply ownership of the others, so check each one separately.
Six parts, six owners to check
| Part | Who should own it | What to check |
|---|---|---|
| CRM account | You, or your sub-account with a transfer path | Whose card pays, who is the account owner |
| Contacts and history | You | You can export them at any time |
| Phone numbers | You | Numbers can be ported out if you leave |
| Domain and email sending | You | The domain registrar account is in your name |
| n8n, Zapier or Make account | You | Workflows are in your account, not the agency's |
| Custom code | You, by written assignment | The contract transfers copyright to you |
What happens to a GoHighLevel account if you leave the agency?
Many businesses run in a sub-account under an agency's GoHighLevel account. HighLevel lets a whole sub-account move to another agency, with its contacts, conversations, pipelines, custom fields, forms and workflows. Integrations, billing, agency email domains and some phone setups do not move, and a sub-account on an agency's white-label (SaaS) plan has to have SaaS mode turned off before the transfer. The step-by-step version is in how to transfer a GoHighLevel sub-account.
What moves in a sub-account transfer
Those rules are from HighLevel's sub-account transfer guide (updated August 7, 2026). By default only the releasing agency's owner can start a transfer, so the practical question for your contract is: will the agency release your sub-account when asked, and how fast? If you want to avoid the question entirely, run your own GoHighLevel account, which is how we set up client accounts. Moving an existing account is covered in GoHighLevel migration.
Who owns custom code written for you?
Under US copyright law, code written by an outside contractor is not automatically yours just because you paid for it. The US Copyright Office explains that a commissioned work only counts as "work made for hire" if it falls into specific categories and both sides sign a written agreement saying so. Most software does not fit those categories, so ownership should be transferred by a written assignment in the contract.
Is contractor-written code yours?
The rules are set out in the Copyright Office's Circular 30, Works Made for Hire, which lists the nine categories of commissioned work and requires a written agreement. In practice, a good software contract says three things plainly: the client owns the code on payment, the client receives the source code and documentation, and any third-party or open-source parts keep their own licences. Our custom software page covers how we hand over code, and the HirePrep and GoHangars case studies are examples of products we built for clients to own.
What should a contract say about ownership?
A contract should state that accounts are in your name, that you get admin access, that data can be exported at any time, that custom work is assigned to you on payment, and what the agency will do to hand over if you part ways. If any of that is missing, ask for it before you sign.
- Accounts in your name, paid with your card, with you as owner or admin.
- Admin access for someone in your business from day one.
- Data export of contacts, conversations and records at any time.
- Assignment of rights to custom code, designs and workflows on payment.
- Handover terms: documentation, a transfer of any sub-account, and a notice period.
How do you check what you own today?
Log in to each tool and look at who the account owner is and whose card pays. If you cannot log in to your own CRM, domain registrar, phone system or automation tool as an admin, you do not fully control it. Fix that first, while the relationship with your current provider is good.
This check is the first step of any GoHighLevel account cleanup we do, and it matters before moving phone numbers, covered in keeping your business number. If you are weighing snapshots or templates, note that a pre-built snapshot may come with restrictions set by its creator.
Questions about ownership
Can an agency keep my contacts if I leave?
Your customer data should always be exportable by you. Make sure you have admin access and export rights in writing, and export a copy periodically.
Who owns workflows built inside my GoHighLevel account?
They live in your account and run on your subscription. For clarity, the contract should also say that the agency assigns any rights in them to you.
Is a white-label GoHighLevel account a problem for ownership?
It can be. HighLevel says white-label sub-accounts cannot be transferred to another agency, so if you leave, the build may have to be recreated elsewhere.
Do I own the AI agent's instructions and knowledge base?
If they were written for you under a contract that assigns the work to you, yes. Keep a copy of the prompts and knowledge files outside the platform.
Sources and further reading
- US Copyright Office, Circular 30: Works Made for Hire.
- HighLevel, Sub-account transfer guide, updated August 7, 2026.
- FCC, keeping your phone number when you change providers.
