Direct answer: An NZ business should be able to retain control of its domain, website, email and recovery records when a developer or hosting provider changes. Before selecting hosting, prepare an exit-ready handover: identify the authorised domain holder, separate registrar and server changes, verify exports and agree how a replacement will be tested.
This guide focuses on continuity for New Zealand small businesses and developers. It does not rank untested local servers or report a latency experiment. The general hosting selection guide explains infrastructure requirements; this NZ page addresses the distinct handover and .nz domain workflow that can keep a business from depending on one person’s account.
Domain registration, authoritative DNS, website hosting and email hosting can be supplied by different organisations. Changing one does not automatically move the others. Write which provider controls each component and who can authorise a change. A renewal invoice for the server is not proof that the same account controls the domain.
For an NZ project, include the business’s authorised decision-maker in that map. A developer may have technical access without authority to change the domain holder or cancel a service. A registrar transfer, a holder change and a website migration have different purposes. Keep their approvals and verification steps separate.
No actual transfer or account change is performed in this article. The process below is a planning method. It deliberately avoids a promise that every migration can complete instantly, preserve all data automatically or avoid every interruption. A responsible handover starts with the real system and the available evidence.
Record the current .nz domain holder and the authorised person acting for the business. Confirm the contact details through the registrar’s appropriate process. Do not assume that the person who originally commissioned the design is still the authorised holder or that a developer’s personal account is the intended permanent home.
The InternetNZ .nz Rules describe the registry, registrar and domain-holder framework. Review the applicable current rules before acting. This guide does not settle an ownership dispute or authorise changing a holder’s identity without the proper process.
Write whether the project changes the registrar, domain holder, DNS operator, website server or mail provider. The business may need only one of these changes. Combining them without a reason makes investigation and rollback harder. Preserve the intended scope in the NZ handover document.
For example, moving WordPress files does not necessarily require moving domain registration. A registrar transfer also does not establish that mailboxes or the application database have moved. Our domain transfer guide complements the local .nz procedure without replacing registry-specific requirements.
The Domain Name Commission’s transfer guidance explains requesting an authorisation code and supplying it to the new registrar. Use the authorised process and protect the code. Do not publish it in a support screenshot, article draft or broadly shared project document.
DNC’s authorisation-code guidance also explains its security role and current expiry and use conditions. Check that source when planning a real transfer rather than copying an old code-handling instruction. No code was requested or entered while writing this NZ article.
Record the actual records and services that matter before an authorised change. The public website, mail routing, sender authentication and third-party verification can depend on different entries. Copying only the web address records is not a complete DNS migration. Keep the original configuration in an appropriately protected record.
The nameservers and DNS guide explains the distinction between delegation and record content. For an NZ business retaining its mail service, preserve the relevant mail records and verify the outcome. Do not assume that a new hosting account automatically reconstructs the old zone correctly.
List the files, database, uploads, configuration and external dependencies required to operate the site. A WordPress content export is useful for some purposes but is not automatically a complete server backup. Identify the actual restore or import method needed at the destination. Keep credentials and confidential data out of public handover material.
Use the website migration workflow to organise a controlled move. An available download is not proof that the replacement works. The NZ project owner should approve a destination validation plan that covers the important application states, not only the homepage.
Record whether the business keeps or changes its email provider. If mail stays elsewhere, document that boundary so a web-server change does not unintentionally replace the mail routing. If mail is moving, it needs a separate authorised migration scope, user preparation and verification plan.
Our email versus web hosting guide explains the independent services. For an NZ handover, identify the recovery addresses used by the registrar and server accounts too. A working public website is not proof that staff can receive mail or recover administrative access.
The New Zealand Privacy Commissioner’s principle 12 guidance explains disclosure outside New Zealand. Its supporting guidance document distinguishes some agent or cloud-processing arrangements from disclosure where information is used for the recipient’s own purposes. The actual role matters.
Have the responsible privacy owner assess the arrangement and applicable obligations. Do not declare every offshore host prohibited, or every NZ-branded provider compliant. Map the relevant application, backup, support and integration services. This article supplies a technical handover question, not a legal determination for the reader’s organisation.
State the currency of each quote and the actual period covered. If a provider charges another currency, keep the original amount and any planning conversion separate. Do not label a foreign-currency advertisement an NZD offer simply because the page targets New Zealand visitors.
Include any agreed overlap while the replacement is validated. The business may temporarily retain two services for a controlled transition, but the duration and responsibility need approval. The renewal budgeting workflow helps organise the general calculation without inventing a local provider price.
Define the safe conditions for a representative restore or destination test. A file archive can exist while important uploads or database changes are missing. A store may contain orders newer than a backup. Agree how the move will account for new activity instead of assuming a generic archive is enough.
Use backup planning and the forms test matrix to specify evidence. Record the environment and result. This NZ guide reports no successful restore, actual test submission or measured uptime result on a provider’s infrastructure.
Verify that the authorised business can access the necessary accounts through the agreed method. Give staff a plain-language index of responsibilities and recovery routes. A bundle of passwords without context is not a reliable handover. Use appropriate delegated access where supported rather than retaining a shared administrator login indefinitely.
The roles guide and authentication guide support a scoped access review. Removing or changing someone’s real access requires its own authorised action; no account permissions were changed for this article.
Use one entry for each provider and identify its function. Include registration, DNS, application hosting, mail, backups, payments and other critical integrations. Record the authorised owner and renewal contact. The map should explain what would stop working if that service expired or its account became unavailable.
Do not include unnecessary secrets in the map itself. Refer to the approved location of recovery material instead. A staff member should be able to find the right owner without gaining broad access to private customer information. Separate a public project summary from the confidential operating record.
Write the planned order and the evidence required before the next step. For example, a destination can be prepared and checked before an approved public DNS change. The exact method depends on the application and services. Do not present a universal sequence as safe for every store, membership system or external integration.
Record the rollback decision point and owner. A technically possible rollback can still have consequences if new orders or edits occurred on the replacement. Preserve that uncertainty and plan how newer data would be handled. The NZ handover should make those decisions explicit before a problem occurs.
List the public pages and visitor journeys the owner considers important. Record expected and observed results separately. Include a date, environment and evidence reference. Keep not tested and blocked distinct from passed. A migration checklist that silently treats every blank item as complete does not support a reliable acceptance decision.
After an authorised cutover, verify the actual public URL, relevant mail behaviour and the agreed application tasks. Do not infer complete success from a registrar’s transfer notification. That notification concerns a specific domain operation, while the website and email may still depend on separate configuration.
Imagine a consultancy retaining its current hosting while appointing a new developer. The handover focuses on authorised access, the code and content workflow, backups and the service map. It does not automatically require a registrar transfer. The owner verifies that recovery contacts remain under business control.
The new developer documents the application before proposing changes. This avoids treating an unfamiliar configuration as a reason to replace every service immediately. The example is a planning pattern, not a report of a real NZ customer’s transition or a claim that keeping the old infrastructure is always preferable.
A store owner approves a new web-hosting service while retaining domain registration and mail. The team records the relevant DNS changes and the period of transaction activity during the move. It tests the destination under the approved conditions and defines who can authorise the public switch.
The owner keeps the old service until the agreed acceptance conditions are met. The team does not assume that a successful homepage request proves payment, download or notification delivery. This example contains no actual migration result, provider performance claim or financial saving.
Promotional recommendation: KAWEDMA hosting, domain and website services may be considered for a scoped transition proposal. Confirm support for the required extension, service location, quote currency and handover responsibilities. This is not a claim that KAWEDMA operates an NZ data centre or can bypass .nz registration and transfer rules.
When the documented application needs fit shared hosting, investigate the supplied hosting.com shared hosting referral. Affiliate disclosure: Hostreta may receive a commission for eligible purchases under applicable terms. Confirm the actual plan and regional options; the referral does not guarantee NZ latency, NZD billing or a successful migration.
A useful NZ handover gives the business a clear map, a controlled change plan and a record of the tested result. It should not require a national best-host label or a fictional local speed comparison. The right infrastructure decision depends on the actual workload and responsibilities.
Review the map after material changes in staff, providers or integrations. Check the current .nz rules when a domain operation is proposed. Preserve the distinction between a prepared plan, an authorised action and a verified outcome so that the next owner can continue without repeating risky assumptions.
Ask a second authorised staff member to locate the service map and explain which provider handles the domain, DNS, website and mail. The aim is not to share every administrator credential. It is to confirm that the organisation can identify the correct recovery route if the main contact is unavailable.
If the answer depends on a former employee’s personal email, record that as an access-planning issue for an authorised review. Do not bypass recovery controls or impersonate the person. A documented legitimate process protects both the business and the people who previously managed its NZ website.
Identify the technical records needed to operate the application and the business records needed to explain decisions. The former might include configuration and a usable database export; the latter includes approvals and acceptance evidence. Keep retention decisions with the responsible owner rather than saving every private record indefinitely because it might be useful.
When a provider changes, ask what happens to residual copies, account access and support records under the actual agreement. The developer can document the question, but should not promise immediate deletion from every backup without evidence. An NZ handover record should state what is confirmed and what remains to be clarified.
A hosting move does not require changing the public URL merely for convenience. If the project also changes a domain or page structure, create a separate link and redirection plan. Verify representative old addresses through the public site and inspect the relevant technical response where available. Do not assume a design import preserves every old path.
Our page review checklist supports maintaining accurate public links. A domain registration operation alone does not establish search indexing or preserved rankings. Keep those outcomes separate from the basic continuity checks and avoid guaranteeing an SEO result.
Write who should be contacted for a domain issue, a DNS issue, an unavailable application and a missing email. These may be different teams. Record the supported channel and the evidence staff should collect. A vague instruction to contact the host can waste time when the actual problem lies with a separate service.
For an NZ business working with an overseas developer, record exact working hours and an agreed timezone rather than assuming identical calendars. If urgent coverage is required, confirm the actual arrangement and scope. The document should not invent a response guarantee that the provider or developer has not accepted.
Make retirement a separate authorised decision after the agreed acceptance conditions are met. Check for forgotten dependencies such as old mailboxes, scheduled jobs, downloads or externally referenced files. A new homepage appearing correctly does not prove that the previous account contains nothing the business still needs.
Keep the retirement decision and its evidence in the change record. If something remains unresolved, name the owner and the next check. Avoid retaining a duplicate paid service forever through neglect, but do not cancel it merely because an editorial checklist says the move should be finished.
State the component changed, the authorised scope, the observed outcome and the remaining limitation. Include the date and responsible contact. Use precise statements such as a verified public page or a confirmed test mailbox receipt rather than a broad declaration that everything is perfect.
The best handover is understandable to the next authorised person. It explains the system without exposing secrets, preserves evidence without pretending to measure every possibility and makes future NZ provider decisions easier to review.
Comments are closed.
We may earn a commission on purchases made through these links, at no extra cost to you.
Don’t miss the chance to participate in the biggest giveaway of this year.