The most expensive web problem rarely starts with design. It starts months later, when a business discovers that its former vendor holds the domain, the hosting account, or the analytics history the company assumed it owned.
Before signing with any website design company, settle ownership in writing. Whoever controls the domain, hosting, analytics, and custom code controls your ability to leave.
This guide walks you through the real failure mode, why ownership is a pre-contract question, and six practical steps: confirming you are the registered name holder on the domain, finding out whose hosting account the site lives in, getting admin access to analytics, securing theme and plugin terms in writing, settling what happens to the site and its data when the agreement ends, and requesting a documented handoff even when you intend to stay. A pre-signature checklist ties it together.
OneStop Northwest helps organizations reduce vendor complexity across websites, marketing, technology, IT, printing, signage, branded merchandise, apparel, company stores, and fulfillment. We serve Shelton, Mason County, Western Washington, Washington State, the Pacific Northwest, and organizations nationwide.
The Real Failure Mode: You Can See the Site, Not the Accounts
A site can launch on time and look right while the important controls sit elsewhere: the domain in the vendor’s registrar account, the hosting bill in the vendor’s name, and the analytics property tied to a login no one at your organization owns. That is the real failure mode. Whoever holds the account holds the ability to leave. Control of the account, not the design file, is the leverage.
At launch, buyers commonly receive a live URL and an editor login for pages. Neither is ownership of the domain, the hosting account, or the analytics property. Under ICANN’s Transfer Policy, the Registered Name Holder is the party with authority to approve or deny a domain transfer, which is why the name on the account matters. Everything beyond that policy point in this piece is a recommendation.
OneStop Northwest designs and hosts websites, so we benefit when clients can leave cleanly. We are naming that interest up front rather than presenting as neutral.
Use this as a pre-contract checklist when comparing website design companies. Confirm policy requirements against ICANN, and treat every other item as recommended practice. For a clearer view of a professional build, see our guide to website design for small businesses.
Why Ownership Is a Pre-Contract Question, Not an End-of-Contract One
The timing matters as much as the terms. Before signatures, ownership is a negotiating point. After launch, every change needs cooperation from someone who may have little reason to provide it.
This article separates two kinds of claims. ICANN’s Transfer Policy sets verifiable requirements, including that the Registered Name Holder is the only party with authority to approve or deny a transfer request. Hosting credentials, analytics access, license terms, end-of-term handling, and handoff documents are our recommendations, not regulation.
When accounts stay with a vendor, a buyer can lose three things: authority over the domain, the site’s operating environment, and the record of how the site performed.
Put all of it in the agreement itself, not a later email thread. Name each account, name who owns it, and name what happens at termination.
Owners, marketing and communications leads, procurement, IT, and the school, agency, or nonprofit administrators who inherit a site someone else built should read this before the next contract.
Step 1: Confirm You Are the Registered Name Holder on the Domain
With the contract established as the place to settle ownership, start with the domain. Under ICANN’s Transfer Policy, the Registered Name Holder, the party of record on the domain, is the only party with authority to approve or deny a transfer request to the gaining registrar (ICANN’s domain transfer rules). Registrars should also make reasonable efforts to inform that holder of, and provide access to, the published documentation for the transfer process. The consequence is blunt: if your vendor is the Registered Name Holder, leaving is a request you make, not a right you exercise. Policy context: ICANN’s 2009 Registrar Accreditation Agreement committed ICANN to publishing a registrant rights and responsibilities summary, and the Transfer Policy was updated in February 2024 to align with the Registration Data Policy, with implementation required by August 2025. As a recommendation, confirm the registrar account is in your organization’s name with an address you control; record the registrar and expiration date where the whole team can find them; and keep login, recovery, and the authorization code the losing registrar releases in your own hands.
Step 2: Find Out Whose Hosting Account the Site Lives In
With the domain settled, the hosting account is the next place control quietly moves. Before anything is built, ask three questions: whose name is on the hosting account, whose payment method renews it, and whose inbox receives the renewal and suspension notices. If all three answers are the vendor, you are renting access to your own site.
Hold admin-level credentials for the hosting control panel and the content management system, and make sure at least two people at your organization can sign in without asking the vendor for help. Then ask where the site actually lives. A standard hosting account, a managed platform, and a site builder tied to a vendor account behave differently, and only one is straightforward to move. Our managed website hosting vs. DIY hosting comparison walks through those tradeoffs.
Ask how backups are taken, where they are stored, and how you would get a current copy if the relationship ended next month.
Finally, flag the courtesy arrangement. Hosting bundled in at no separate charge often means your site sits inside the vendor’s account with no defined exit, the hardest version to unwind. Our affordable web hosting FAQ covers the common questions.
Step 3: Get Admin Access to Analytics and the Records Around It
Hosting is settled. Analytics is a separate account with its own owner, so a clean site transfer can still leave your historical performance record behind.
What to confirm. Get admin access to the analytics platform in use, along with tag management, search console verification, and any advertising or CRM tracking identifiers tied to the site. Better still, have analytics created under your organization’s account from day one, with the vendor added as a user. The reverse arrangement, a vendor-owned account where you are a viewer, is the one that creates problems later.
Ask about export. Find out whether the data can be exported and in what format, because account ownership on some platforms limits what a non-owner can retrieve.
Check the adjacent records. DNS entries, TLS certificate renewals, and email authentication records (SPF, DKIM, DMARC) usually live in the domain or hosting account. Losing access to those breaks email along with the site, often quietly, days after the handoff looks complete.
Next, the code itself: themes, plugins, and who actually holds the licenses.
Step 4: Get Theme, Plugin, and Custom Code Terms in Writing
With account access settled, turn to what runs inside the site. Ask which licensed themes, plugins, fonts, and stock assets the build depends on, who holds each license, and whether it follows the site or stays with the purchaser. Many premium licenses are personal or capped to a set number of sites; a folder of plugin files is not a license you can keep updating. Settle custom code ownership in the agreement itself. A work-for-hire clause naming deliverables plus repository access is a different commitment than a verbal assurance that you own the site. Name source files, the database, and build documentation as deliverables due before final payment, not favors requested after launch. This matters operationally: an expired license stops receiving security updates, so a licensing question becomes a maintenance and risk question within a year or two. The habit is the same one that protects any large purchase, whether code or custom promotional products with your logo: get the terms in writing before you commit.
Step 5: Settle What Happens to the Site and Its Data at the End of the Agreement
With licenses settled, close the loop by making termination terms as specific as the build. Treat these as advisory terms to negotiate, not regulatory requirements. Put in the hosting agreement what you receive for site files, the database, and analytics data at the end of the term, including the export format and the retrieval window. Ask for the notice period required on both sides and confirm whether the site stays live during a transition; a site going dark mid move is its own emergency. If you choose not to migrate, name who deletes what and when, and whether any copy is retained afterward. Apply identical language to the domain registration and any email service hosted alongside the site, so the clause covers the full arrangement rather than one piece. For budget approval, frame it plainly: an exit clause is not distrust. It is the same discipline as a lease that spells out move-out conditions.
Step 6: Ask for a Documented Handoff Even If You Intend to Stay
Once end-of-term terms are set, apply the same discipline at launch: require a written handoff document even if you expect a long relationship. It costs little now and is nearly impossible to reconstruct later.
The document should list the registrar, domain expiration date, DNS provider, hosting account owner and credential holder, CMS admin accounts, analytics property identifiers and admin users, license keys, third-party integrations, and a named contact for each.
Have someone on your team walk the handoff and log in to every account before final payment, not after. Gaps surface while you still have leverage. This also protects you when vendor staff turnover changes your day-to-day contact; the document carries the knowledge, not the relationship.
When evaluating website design firms, ask to see a sample handoff document before signing. A firm that has one has done this before. If you also manage uniform or print programs, our Corporate Apparel Buying Guide for HR and Operations Leaders and guide to choosing a commercial printing partner for ongoing marketing collateral apply the same vendor-evaluation discipline.
The Pre-Signature Checklist
The handoff document is step six. This checklist is what makes it, and the five steps before it, enforceable: complete it with the vendor and attach it to the agreement.
Domain
- Registered Name Holder is your organization
- Registrar and expiration date recorded
- Login and recovery details held internally
- Transfer authorization process understood
Hosting and analytics
- Account owner named
- Payment method and renewal notices in your name
- Admin credentials held by at least two internal people
- Analytics property created under your account, with data export confirmed
Code and licensing
- Licensed themes, plugins, fonts, and assets listed
- License holder named
- Custom code ownership and deliverable files written into the agreement
Exit and handoff
- End-of-term data handling
- Notice periods
- Deletion terms
- Handoff document defined as a deliverable
Attach the completed checklist to the contract or RFP as an exhibit so it is enforceable rather than aspirational, and route it to procurement, IT, and legal before signature. The same discipline applies to every asset you commission, including business signage planning. When you are shortlisting website design companies, a vendor who answers these without hesitation is showing you their process.
Control Is the Deliverable Nobody Puts in the Proposal
The checklist above protects one line: whoever holds the account holds the ability to leave. That is settled before the project starts or not at all.
This week: confirm the registered name holder is your organization, move admin credentials for hosting and analytics into internal hands, and put end-of-term data handling in writing. The same discipline applies to any web portal, including an online company store.
The habit that prevents most problems: ask for the handoff document at the proposal stage. The answer tells you how the engagement will end before it begins.
OneStop Northwest provides website design and hosting from Shelton, Washington for organizations across the Pacific Northwest and nationwide. Consolidation with a single source partner is only an advantage when ownership terms are clean, and clean terms are yours to require.
Conclusion
Website ownership is not a parting formality. It is a pre-contract discipline. Make sure your organization is the registered domain name holder, know whose hosting account the site lives in, and secure admin access to analytics and related records. Put theme, plugin, custom code, and end-of-term data handling terms in writing, and request a documented handoff even when the relationship is going well. Together, these steps protect your ability to manage, move, or leave without losing control of the asset.
As a next step, attach the completed checklist to the contract or RFP as an exhibit and route it to procurement, IT, and legal before signature. OneStop Northwest provides website design and hosting from Shelton, Washington for organizations across the Pacific Northwest and nationwide. Clean ownership terms make any partnership stronger. Ask for the handoff document at the proposal stage, and make control part of the deliverable from day one.
Frequently Asked Questions
Why should I settle website ownership before signing with a design company?
Ownership is a negotiating point before signatures. After launch, every change needs cooperation from someone who may have little reason to provide it. Whoever controls the domain, hosting, analytics, and custom code controls your ability to leave.
Who is the Registered Name Holder for a domain, and why does it matter?
The Registered Name Holder is the party of record on the domain. Under ICANN's Transfer Policy, it is the only party with authority to approve or deny a domain transfer request to the gaining registrar. If your vendor is the Registered Name Holder, leaving is a request you make rather than a right you exercise.
How can I tell whose hosting account my site is in?
Ask three questions: whose name is on the hosting account, whose payment method renews it, and whose inbox receives the renewal and suspension notices. If all three answers are the vendor, you are renting access to your own site. Hosting bundled in at no separate charge often means the site sits in the vendor's account with no defined exit.
Why is analytics access important when changing vendors?
Analytics is a separate account with its own owner, so a clean site transfer can still leave your historical performance record behind. Get admin access to the analytics platform, and ideally have it created under your organization's account from day one with the vendor added as a user. Also confirm the data can be exported and in what format.
What should a documented handoff include, and why request one even if I plan to stay?
The handoff document should list the registrar, domain expiration date, DNS provider, hosting account owner and credential holder, CMS admin accounts, analytics property identifiers and admin users, license keys, third-party integrations, and a named contact for each. Requesting it even if you intend to stay is inexpensive now and nearly impossible to reconstruct later, and it keeps the knowledge in the document rather than in the vendor relationship.
