How to take over an Elementor site someone else built

A client’s last developer has gone quiet, or the build stalled at 70%, and now the site is yours. The mistake that costs agencies the most is quoting a date before looking inside it. A site you did not build is a set of unknowns, and every unknown you promise around becomes your problem.

Our rule: the audit comes before the quote, and the audit is its own small step. It takes an hour or two. Here is what goes in it.

Before you touch anything

Take a full backup (files and database) and work on a staging copy if you can. Then get access to three things: WordPress admin, the hosting panel and the domain registrar. If any one is missing, solving that is the first job. You cannot responsibly change a site you cannot recover.

The 10 checks

1. Hosting and PHP version. Old PHP versions cause plugin errors that look like “Elementor bugs”. Note the version and whether the host will let you move to a supported one.

2. Versions and the Elementor Pro licence. Check WordPress, Elementor and Elementor Pro versions. Then find out whose licence it is. A licence tied to the previous developer’s account is the classic hand-off trap: updates and support stop at the worst moment. Transfer or replace it before launch.

3. Plugin inventory. List every plugin and ask of each one: is it active, is it used, is it maintained? Deactivated plugins nobody removed are a security risk. Two plugins doing the same job (two SEO plugins, two caching plugins) are a conflict risk.

4. Theme and child theme. Is there a child theme? Edits made in a parent theme vanish on the next update. Look for custom code in functions.php and work out who wrote it and why.

5. How the pages are built. Open a few templates. Are they built with Elementor containers, or older section and column structures? Is there custom CSS or code inside widgets that only the previous developer understands? Mixed methods mean slower edits and surprises.

6. Global styles. Are colours and fonts set as global settings, or hard-coded on each widget? Hard-coded styling turns a simple brand change into a page-by-page job. In our experience this is the biggest hidden cost in a takeover, so look for it early.

7. Performance baseline. Run the key pages through PageSpeed Insights and save the numbers before you change anything. Otherwise you will be blamed for problems you inherited. Our guide to what you can honestly promise clients on speed covers how to talk about it.

8. Forms and integrations. Test every form end to end. Where do submissions go, and to whose inbox? Check analytics, CRM connections and third-party scripts. A broken form is the most expensive silent failure on a small business site.

9. SEO safety. Export the URL list, titles and meta descriptions before any restructure. Check redirects and the sitemap. If URLs will change, plan the 301s first.

10. Security basics. Who are all these admin users? Check file permissions, login protection, and whether the backups actually restore. Remove accounts that should not exist.

Turn the audit into a quote

Sort what you found into three buckets: must fix before launch, should fix soon, and leave alone. Quote the first as fixed scope, offer the second as an optional phase, and write down the third so nobody is surprised later.

Be willing to say “this part should be rebuilt, not repaired.” If most of the styling is hard-coded and the logic lives in custom code, a repair can cost more than a rebuild, and your client is better served by hearing that from you early.

When the date cannot move

If there is a launch date that cannot slip and the build is stuck, that is what our Priority Pass is for: an Elementor rescue where we confirm feasibility before we commit.

If you would rather not run the audit yourself

We take over inherited Elementor sites under your brand, and we start with the audit above so you get a scoped quote, not a guess. If you have one waiting, tell us about it.

Frequently asked questions

Can I take over a site without the previous developer's help?

Usually, if you have admin access to WordPress, the hosting and the domain. Without all three, stop and get them first.

Should I rebuild instead of repair?

If the structure is mostly hard-coded styling and custom code, rebuilding is often cheaper. The audit tells you which.

What if the Elementor Pro licence belongs to someone else?

Transfer or replace it before launch, or updates and support will stop working when you least want that.