“You own your website” can mean several different things. You may own your copy and domain registration but only have a license to use the theme, stock photo, font, or page builder. You may be able to export pages but not the proprietary system that renders them. Before changing providers, make an asset list and read the contract and third-party terms for each item.
Separate access from rights
Access means you can sign in, download, or edit. Rights determine what you may reuse, modify, or transfer. A hosting login does not necessarily give you rights to a designer’s source files; possession of a stock image file does not necessarily let another agency use its license. Ask for both the technical access and the legal or contractual basis for reuse.
Create rows for domain and registrar account, DNS, hosting, content management system, source repository or export, design files, copy, images, fonts, plugins, analytics, forms, and integrations. Record the account holder, billing owner, available export format, license owner, renewal date, and any transfer restriction. Do not send passwords over ordinary email to prove control; use invited roles or secure transfer methods.
Test transferability before a crisis
Ask a prospective new provider to review a sample export and identify what it can rebuild or import. A zipped website may include static output but not editable templates, database content, or form logic. A design file may capture the appearance while leaving code and subscriptions behind. If portability matters, request a demonstration: export a page, import it to a clean environment, and list what broke.
Check domain control separately. The registrar account holder should be identifiable, renewal notifications should reach the business, and DNS changes should require authorized approval. ICANN’s domain-registration guide explains the registrant’s role; a domain transfer is not the same as moving hosting or changing a web designer.
Put the answer in the proposal
Before signing, ask: “At project completion or termination, what exact files, exports, credentials, and documentation will you provide; in what format; and which third-party licenses stay with your account?” Add when handover occurs, including any payment condition already in the agreement. For separately billed software or media, record who will maintain the subscription after handover.
If the current provider says a platform cannot be exported, ask which content and data can be exported and what a rebuild would require. Avoid assuming a new provider can copy proprietary designs or code. The practical goal is to know the migration cost and business continuity risk before you need to move.
Keep an updated copy of the asset inventory with the business's own project records.
ARCHV’s website service page says domain, hosting, files, content, licenses, and postlaunch responsibilities should be defined in the proposal. It does not promise that third-party rights transfer automatically. If two offers use different platforms, compare their handover language in the website quote review. A public agency handover discussion shows how varied buyer expectations can be; it is qualitative context, not a rule governing your agreement.