OneAge Design
Brand & Websites

October 17, 2026

Who controls your website’s code and data? Plan the handover before signing

Clarify accounts, deliverables, licenses, export formats, and exit procedures so another maintainer can operate the website.

Who controls your website’s code and data? Plan the handover before signing

The difficult questions often appear when a contract ends. Define what is rented, licensed, delivered, and transferable while the arrangement is still easy to discuss.

Define a usable handover

A source archive without a database schema, build instructions, or necessary licenses may not be enough to run a site. Agree on deliverables that another qualified maintainer can rebuild and operate. Check whether the arrangement is a hosted subscription, a license, or development with specified rights.

Check domains, code, and records separately

Confirm domain registrant details, administration, renewal, transfer, DNS, and email dependencies. Specify frontend and backend code, repository, database migrations, configuration templates, and deployment documents. Commissioning work does not by itself settle every intellectual-property question; define rights and exceptions in the agreement, including existing modules, open-source packages, and paid assets.

Ask for a meaningful data export

Request suitable CSV, JSON, or SQL exports with field definitions and relationship keys. Check menus, options, customers, orders, payment references, and image indexes. Portability does not give unrestricted permission to reuse personal information; the original purpose and applicable requirements still matter.

Compare control with ongoing responsibility

SaaS can reduce infrastructure work but comes with platform export and cancellation rules. Independent deployment offers more control while requiring updates, backups, and maintainers. Choose around actual switching costs and operational needs.

Rehearse a small migration

Agree on export fees and timing, transition support, a cancellation buffer, retention, and deletion. Verify access to key accounts and restore in an isolated environment. Have appropriate professionals confirm transaction-specific terms; a vague “all rights included” clause is not an acceptance plan.

Before you start

  • Confirm domain and service account control.
  • List code, documentation, licenses, and exceptions.
  • Inspect an export with relational data.
  • Test restoration and agree on exit support.

Your next step

Bring your proposal or handover list. We can identify technical gaps so ownership and delivery expectations can be discussed concretely.

Brand websites and visual design · Contact us

Features, third-party support, fees, and delivery scope are subject to assessment and the current agreement.

Further reading

Template or custom website? Spend on the requirements that matter

References and example assumptions

References follow the Traditional Chinese edition. Numerical scenarios illustrate calculation methods; they are not customer results, service quotes, or guarantees. Monetary examples are in New Taiwan dollars (TWD). Cover images illustrate service concepts.

More Insights

Related reading

View more
Who controls your website’s code and data? Plan the handover before signing | OneAge Design