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. Third-party guides report that sub-accounts under a white-labeled agency cannot be transferred, and HighLevel's own transfer guide does not settle it. Get written transfer terms, and check with HighLevel support before you rely on a move.
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.
What happens to my GoHighLevel account if my agency closes?
Your sub-account sits under the agency's account, so it is at risk if the agency stops paying HighLevel. Ask for a transfer to your own agency account or a new agency while the old one can still send it. HighLevel's guide says to contact its support if the transfer cannot be completed in the app.
Can I export all my contacts from GoHighLevel?
Yes. Users with export permission can export contacts to a CSV file from the contacts list. Make sure at least one admin user on your account belongs to your business, and export a copy on a schedule, such as once a month, so your data never depends on someone else's login.
Do I own my phone number if the agency set it up?
The number serves your business, and FCC rules let you keep it when you change providers. How it moves depends on the setup: LC Phone numbers move with a sub-account transfer, while Twilio numbers need the agency and the Twilio account owner to work it out. See keeping your number.
Who owns my A2P 10DLC registration?
It is registered to your business's legal name and EIN, so the brand is yours. When a sub-account moves between two agencies on LC Phone, HighLevel says eligible A2P registration stays with the numbers. If you start over somewhere else, plan to register again, which usually takes up to 3 business days.
Who owns a snapshot built for my business?
The snapshot sits in the library of the agency that created it, so the contract decides who may use it. If you paid for it, ask for the rights in writing and a share link that lets your own agency account import it. Without that, you keep the live workflows but not the reusable template.
Who owns my website and funnels built in GoHighLevel?
They live in your sub-account, and the domain is what really ties them to you. Register the domain in your business's name with your own login, then point it at GoHighLevel. If an agency registered it in its own name, ask for it to be transferred to you.
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.