Elementor Pro white label: who holds the licence, who owns the site, and what a clean handoff looks like

If you sell websites under your own brand and a partner builds them, Elementor Pro quietly creates a few decisions that nobody puts in the quote. Whose name is on the licence? Who can renew it? What happens to the site if the partnership ends? An Elementor Pro white label arrangement works well when those answers are agreed early, and badly when they are discovered at renewal time.

This is general guidance for agency owners. Licence terms change, so always check Elementor’s pricing page and help centre for the current rules before you commit.

Four things people call “ownership”

When someone says “who owns the site”, they usually mean one of four different things.

Most disputes come from treating these as one thing. A builder who holds the domain “for convenience” has quietly created lock-in, even if no one meant it.

Who should hold the Elementor Pro licence

There is no single right answer, but there are two sensible models.

The agency holds it. You buy the licence, activate it on the client site and pass the cost through as a line item or inside a care plan. This keeps renewals in your hands and lets you manage several sites in one place. The trade-off is that you carry the obligation, and the client needs a plan if they ever leave you.

The client holds it. You buy it in the client’s name (or they buy it) and you are added as the person who manages it. This makes handoff trivial. The trade-off is that you rely on the client to renew on time.

What matters more than the model is that it is stated. The same advice appears in our note on Elementor Pro versus free: put the holder, the renewal date and the cost in the proposal.

How licensing works, at a high level

Elementor Pro is sold as an annual licence, tiered by the number of websites you can activate it on. A licence is activated per site, and an active licence is what keeps updates and support flowing. If it lapses, the site usually keeps running, but you lose updates and support until it is renewed. Moving a licence between sites is normally done by deactivating on one site and activating on another.

That is a general description only. Plan tiers, site limits and renewal terms change, so confirm them on Elementor’s pricing and Pro pages, and read the licence terms yourself. Do not rely on a summary, including this one.

Working with a partner who builds under your brand

We are a small, owner-led studio that builds WordPress with Elementor under the agency’s brand, so this is a conversation we are used to. If you want to see how that arrangement works, start with white label Elementor development and our white label Elementor agency page. They explain what you hand over and what comes back.

Whoever you choose, ask the same questions before kickoff:

• Which accounts will be created, and in whose name?
• Will the builder ever need to hold the licence or the hosting?
• What do I receive at the end, and in what form?
• What happens if either of us stops working with the other?

If the answers are vague, that is information. Our guide to choosing a white label Elementor agency covers more of what to ask.

What to put in the agreement

You do not need a thick contract, but a few clauses prevent most problems. Our post on what a white label agreement should include goes deeper; for licences and ownership, cover these:

1. Licence holder and renewal. Name who buys it, who renews it and who pays.
2. Transfer on request. The builder must help move any licence or account to you or your client on request.
3. Ownership on payment. Design, content and custom work pass to you or the client when the invoice is paid.
4. No lock-in. The builder does not hold the domain, hosting or licence unless you have agreed it in writing.
5. Confidentiality. Your client relationship stays yours. An NDA is a reasonable thing to ask for, and we can sign one.
6. Exit support. What help the builder gives if the arrangement ends, and on what notice.

What a clean handoff looks like

A handoff does not need ceremony. It needs completeness. At the end of a build, or when a partnership ends, you should be able to tick off:

• Access: admin logins, hosting, domain registrar and any connected tools, all in the right owner’s name.
• Licence: active, in the agreed holder’s account, with the renewal date recorded.
• Backups: a recent full backup you can restore from. WordPress’s own backup guidance is a good baseline.
• Customisation notes: any custom code, plugins and settings, and where they live. If a child theme is used, say so.
• Test: someone who is not the builder logs in, edits a page and updates a plugin.

That last item is the one most teams skip, and it is the one that proves the handoff worked. If you are inheriting a site rather than handing one over, see how to take over an Elementor site someone else built, or our site takeover page.

Avoiding lock-in without drama

Lock-in is rarely malicious. It is usually convenience: a builder sets up hosting on their own account to move fast, and nobody moves it afterwards. Three habits remove most of the risk.

1. Create every account in the final owner’s name from day one, even if the builder is invited as a user.
2. Keep credentials in a shared password manager, not in email or chat.
3. Review the accounts sheet at every renewal, not only when something breaks.

None of this is specific to one partner. It is just good practice for any agency that resells builds.

Next step

Pick one live client site this week and fill in an accounts sheet: domain, hosting, licence, backups, who holds what. Then check it against the list above. If you are planning a new build and want to talk through licence and handoff arrangements, get in touch or read how we work first. A clear brief makes the conversation quicker.

Frequently asked questions

Keep reading

How to take over an Elementor site someone else builtElementor Pro vs free for client sites: when it is worth payingHow to choose a white label Elementor agency