Two people handing over a portable drive

Ownership / Handover

What you own
when the site is done.

Your domain and your content should always be yours. The code and platform access depend on your agreement. With ORYNX AXIOM, once the build is paid, your content, your domain and the finished site are yours to keep.

Project information / Ownership Know the parts / Confirm them in the agreement
HANDOVER / AN INVENTORY
01
Accounts Who controls access
02
Content What can be exported
03
Code What is delivered
04
Licenses What continues to apply
Understand each part

The component inventory

A website is not
one kind of asset.

Your agreement identifies the delivered work, account control, licenses and exclusions. Our own terms are on the project terms page.

Component Control or access Deliverable or dependency
Domain Registrant, administrator, renewal billing and DNS access. The domain account and its authorization are separate from source files.
Hosting Hosting account, technical access and billing owner. The server setup, settings, media and backups your site needs.
Content and data Who supplies, approves and has rights to use it. Export formats, media, structured data and the scope of any migration.
Custom implementation What the project agreement transfers or licenses. Source, templates, configuration and supporting documentation.
CMS / Platform Accounts, license and supported version. Content export does not necessarily include the application or the platform.
Extensions and media Third-party terms, accounts and renewal owners. Plugins, fonts, photography, feeds and other licensed dependencies.
Integrations Authorized accounts, keys and operating owners. Connection configuration, field mapping, failure handling and provider requirements.

Account responsibility

Control is more
than a login.

A person can have technical access without being the account owner or the person paying for renewal. Make those roles explicit.

Registration

Who controls the asset?

Record the registrant or owner for domains and other critical accounts, and establish the process for authorized changes.

Administration

Who can change the system?

Identify administrative and technical access, the recovery route and what ordinary editors are permitted to do.

Billing

Who keeps it active?

Document license and service renewal responsibility. An expired subscription can affect a connection even when the website files have not changed.

Illustrative website files and editing environment, not evidence of a completed client handover
Different parts. Different responsibilities.

Portability

An export is not always
the whole website.

Content, media, application code, configuration and third-party services are separate parts of a runnable system.

Content export

The information and its structure, in the available format. Review what the export includes and whether images or relationships are separate.

Theme or source files

Templates and implementation files may be reusable within a particular platform. Paid themes and plugins stay under their own licenses.

A working copy of the site

A copy that runs also needs the server setup, settings, data and add-ons. Passwords and API keys are handed over privately, never in a shared file.

External services

Hosted platforms, APIs and provider accounts are not files inside the ZIP. Document what must remain active or be replaced.

The delivery record

A useful handover
is specific.

  1. 01

    Accounts and permissions

    List the accounts and authorized roles, with recovery and transfer requirements.

  2. 02

    Files and data

    Record source, content, media, configuration and any exports included in delivery.

  3. 03

    Licenses and renewals

    Identify transferred work, licensed components and continuing subscriptions.

  4. 04

    Documentation and training

    Explain the routine editing or operational tasks that the scope covers.

  5. 05

    Backups and ongoing work

    Identify the backup/restore owner, support route and dependencies that remain.

A checklist to take into any project.

Your ownership check

Eight things
to confirm you control.

Ownership is usually a mix, so check each piece rather than assume. If you cannot confirm most of these, it is easier to sort out now than during a move.

  1. 01

    Domain registrar account

    The domain is registered in your business name, not a provider's.

  2. 02

    DNS control

    You can point the domain wherever you need to.

  3. 03

    Source and production files

    If the site was custom built, you have the files another developer would need to take it over.

  4. 04

    Content and media rights

    The words, images and video you paid for are yours to reuse.

  5. 05

    Analytics and Search Console

    Access sits under your own account, so the history stays yours.

  6. 06

    CMS or platform admin

    Your access does not depend on one provider staying involved.

  7. 07

    Licensed versus owned

    A list covering themes, fonts, plugins, apps and stock media.

  8. 08

    Written transfer terms

    No dispute about what you keep if you leave.

Who owns my website if I build it on Wix or GoDaddy?

You own your content, but the site runs on the platform's system, and export options are limited. Check what you can actually take with you before you rely on it, and keep your domain registered in your own name.

Do I own my website if an agency built it?

Not automatically. Some agencies keep the files, the hosting or the domain. Ask in writing, before you start, whether you receive the files and whether the domain is registered to you.

Is ownership all or nothing?

No. You might own your content and domain while licensing a theme, or own custom code that runs on a platform you cannot fully export. The goal is knowing which parts you control and which you rent.

Continuity

Changing providers?
Plan the transition.

A move is easier to scope when the current files, accounts, licenses and operating requirements are documented.

Can another developer maintain the website?

That depends on the delivered implementation, access, licenses and documentation. Make those requirements part of the agreement rather than relying on an informal assurance.

Does a CMS content export include the entire site?

Not necessarily. An NXT content export contains content.json. The runtime, templates, media, configuration and license are separate considerations.

Which terms control the project?

The approved project agreement and applicable policies identify your rights and responsibilities. Our privacy and project policy contains project confidentiality and intellectual-property provisions. This guide does not amend them.

Before you sign

Ready for
ORYNX AXIOM?

Put the important details in writing.

ORYNX AXIOM

Site navigation

Find a service

ORYNX AXIOM

contact@orynxaxiom.com
ORYNX AXIOM

More information