Creowix

Journal · Web Development

Who Owns Your Contractor Website After the Agency Builds It?

Know who controls your contractor website, what files and licenses you get, and how to test the handover before you sign off.
Written by
Creowix Team
Published
November 7, 2026
Reading time
7 min read
Who Owns Your Contractor Website After the Agency Builds It?

Ask for written control of the domain, hosting, analytics and other business accounts, plus clear terms for the website files and licenses. Confirm which assets can be transferred and have the agency show the handover before final acceptance.

A website comes with more than one set of keys. You might be able to edit your homepage while the agency controls the domain renewal, the hosting bill, and the inbox that gets estimate requests. Before you compare proposals, ask each agency to tell you who holds each key and how you’d get it back.

List what must transfer

Make a handover list before you ask anyone to quote the rebuild. For each item, write down the provider, who controls it today, who should control it at handover, and what you’ll do to verify access. Include the tools attached to the website. Those are easy to miss when everyone’s looking at the homepage.

  • Domain and DNS. Record the registrar, the registered holder, the renewal date, and the account that manages DNS, which directs traffic for your website and email. Check who controls billing, recovery, and two-factor authentication.
  • Hosting and publishing. Identify who pays the host or website builder. Ask for the access needed to publish changes, manage billing, download backups, and restore the site. If the agency hosts several clients together, ask how your site could be moved to an account your business controls.
  • Files and content. List the editable source code if there is any, the database or content export, page copy, original photos, and design files you expect to receive. Ask for setup and deployment instructions so another developer can use what you get.
  • Measurement and search. Record the exact Google Analytics property and Search Console property for your site. As of November 7, 2026, Analytics manages access at the account or property level, and Search Console distinguishes verified owners, delegated owners, and users. Ask for the role you need on the property you actually use. Google Analytics access guide and Search Console permissions guide
  • Lead handling. List your forms, scheduling tool, call tracking, and customer records. Confirm who controls each service, where requests go, and whether you can export the records you need. Agree on how customer data will be handed over securely.

Example. A roofing company’s estimate form emails the office and adds the request to a shared job board. Put both destinations on the checklist. A new site can look ready while the form still routes requests through an account the roofer can’t manage.

Separate domain access, files and licenses

Domain access starts with the registered holder and the registrar account. Ask for the business to be listed as the registered holder where appropriate, with a business-controlled login and recovery method. Confirm whether you need a new registrar or simply control at the current one. Moving a website to a new host and moving a domain to a new registrar are separate jobs. ICANN’s domain transfer guide

As of November 7, 2026, ICANN says a transfer between registrars for a generic top-level domain such as a .com requires an Auth-Code, sometimes called a transfer code. The registrar may let the holder generate it in the control panel. Otherwise, ICANN says the registrar must provide it within five calendar days of a request. Ask your registrar to confirm any applicable locks and when the move can happen. ICANN’s Auth-Code guide

Files and copyright belong on separate lines in the agreement. Getting a copy of the site files and getting copyright rights are separate under US law. A copyright ownership transfer generally requires a written instrument signed by the rights holder or an authorized agent. Ask what custom work the agency will assign, what it will license, and whether you can have another developer maintain or adapt it. Have your attorney review the language and any disputed rights. U.S. Copyright Office, Copyright Ownership and Transfer

Licenses and subscriptions need their own list. Ask the agency to identify third-party fonts, stock photos, themes, plugins, and tools it plans to use. For each one, ask whose account holds the license, whether your business can keep using it after handover, and whether you’ll need a replacement license or subscription.

Example. An HVAC company wants to carry its service pages and online booking into a rebuild. Ask for the editable page content and check the booking tool separately. Find out who controls its subscription and what the next provider would need to reconnect it.

Write handover into the agreement

Take the same checklist to every proposal meeting. Ask the agency to attach the agreed deliverables, exceptions, and acceptance checks to the contract. Get specific while there’s still time to change the scope.

  • Name the deliverables. List each account, file, export, and guide. For a custom build, ask which source repository and revision you’ll receive. For a website builder, ask for a sample export and a list of features that stay tied to the platform.
  • Name the people and dates. Decide who creates business accounts, who grants access, who moves the files, and when you’ll verify delivery. Ask what help you can expect if you change providers later.
  • Spell out ongoing dependencies. Record what needs a renewal, who pays it, and what happens when maintenance or a subscription ends. Ask which services can move to your billing and which would need replacing.
  • Define final acceptance. Agree on the checks you’ll run, who fixes anything that fails, and how you’ll handle work that’s still open. Have your attorney review the wording and any link between handover and final payment.

Example. A landscaping company has separate service-area pages that it wants to carry into the new site. Add a list of old page addresses and their new destinations to the handover. If SEO is part of the rebuild, agree on who will set up and check redirects and confirm access to the search reporting tools.

Bring this list into any website development conversation. If a proposal leaves an item out, ask the agency to explain what you’d need to buy, export, or rebuild later.

Run a transfer rehearsal

Ask the agency to show the handover while there’s still time to fix gaps. Use a private test copy for changes that could affect the live site. If the project includes a live switch, agree on who can restore the old setup and how you’ll decide when to do it.

  • Sign in yourself. Use a business-controlled account to verify access to the registrar, hosting, analytics, and search tools. Confirm you can manage the agreed settings and that recovery goes to someone at your business.
  • Open the delivery package. Download the files and check the folders against the agreement. If the site is supposed to move, ask for a restore or deployment on a test host using the delivered files and instructions. For a hosted builder, open the export and check what it actually contains.
  • Try the jobs your team does. Edit a service page on the test copy. Send a labeled test estimate request from a phone and check the right inbox or scheduling tool. If you track submissions, confirm that the test shows up where you expect.
  • Walk through the switch. Have the agency point out the DNS records used for web and email. Agree on how to preserve mail delivery and what to check after the switch. Once you’ve verified business access, review agency permissions and remove access the agency no longer needs.

Example. A plumbing company routes emergency requests to a different inbox than routine estimates. Try both paths during the rehearsal. Open the requests at the receiving end so you know the right person can act on them.

Related guides

Common questions

Who should control the registrar login?

Ask for a business-controlled registrar account with recovery details your team can reach. Give the agency its own access where the registrar supports that, and confirm who is listed as the registered holder.

Do I receive source files?

That depends on what you agree to and what the platform can export. Ask the contract to name the editable files you’ll receive and spell out what rights you’ll have to use and modify them.

Can I move hosting?

Ask whether the site, data, and required components can run with another host. If the agency says yes, ask it to restore or deploy the delivered package on a test host before you accept the handover.

What if the agency uses a proprietary platform?

Ask whether the platform allows a transfer into your own account and which content or data you can export. Find out which layouts, forms, and integrations you’d have to rebuild if you left the platform.

Next step

Planning a rebuild? We’ll help you put together a free plan that identifies the accounts, files, and handover checks to bring to your proposal meetings. Get my free plan

Free strategy plan · no sales pitch

Got aproblemworthsolving?

Tell me what's not working. I'll find the leak and send you a clear plan: what to fix, in what order, and what it'll take. No obligation. I read every request myself and reply within one business day.

01 / 04

Who are you?

Reply within one business day.

Rather talk?
+1 (818) 278-0368
Address
1001 S. Main St. Ste 600
Kalispell, MT 59901, USA
Hours
Mon – Fri, 9:00 AM – 6:00 PM ET