What if a developer refuses to hand over access?

First check the signed contract, platform terms and invoices to establish what was agreed and who owns each account. Request a written transfer plan naming the specific assets and deadlines. If the disagreement concerns legal rights, obtain qualified local advice. Do not assume access to a hosted subscription means ownership of proprietary software.

Gavior Journal · Web Development · 4 min read

Website Ownership and Handover Checklist After a Developer Builds Your Site

Gavior Editorial Team

Design and engineering editorial team

Published: 2026-10-07Updated: 2026-10-07

Know which accounts, files, licenses, credentials and support documents to receive when a new business website goes live.

A live website is not fully handed over because someone emailed you a login. You need control of the accounts and assets required to operate, update and move it. This matters even when you are happy with the developer: staff change, contracts end, and a future redesign should not depend on one person's private account.

Ask for ownership or appropriate administrator access to the domain, hosting, source files or repository, CMS, analytics, Search Console, design assets and third-party integrations. Also request a content-editing guide, backup and recovery instructions, license list, renewal schedule and a clear support contact. The contract should say what is transferred and what remains licensed.

Asset	Check before sign-off	Common issue
Domain	Registered to your business; renewal and DNS access confirmed	Developer holds the only registrar login
Hosting and deployment	Billing owner, admin access, environment and deploy method recorded	Site works but no one can update it
Source and design	Repository/files, final designs and rights documented	Buyer receives screenshots rather than editable assets
CMS	Admin roles, editor instructions and recovery email tested	Shared credentials with no individual accountability
Analytics and Search Console	Business account is owner; tags and properties verified	Data stays in agency account
Integrations	Forms, email, CRM, payment and API ownership listed	Leads stop arriving after an account expires
Licenses	Fonts, images, plugins and subscriptions identified	Paid asset may not transfer with the site
Security and recovery	Backup cadence, restore method and access revocation agreed	No tested route to restore the site

Website Ownership and Handover Checklist After a Developer Builds Your Site

Ready to turn a better idea into a better business?

Use this handover inventory

Test the access, not just the account list

Record what ongoing support covers

What if a developer refuses to hand over access?

Keep a small operating file

Gavior Editorial Team

Explore Related Gavior Capabilities

Custom website development

UI/UX design

SEO services

Real estate Software Solutions

Retail Software Solutions

Further Reading

Website Redesign Without Losing SEO Leads: A Practical Migration Plan

Business Website Content Checklist Before You Hire an Agency