Written by DROPS.ST.
Before a website vendor leaves, establish who holds the domain registration, who can change DNS, who pays for renewal, and who can recover the accounts. Then agree separately how the shop itself will move. A working website proves that an address resolves; it does not prove your business controls it.
DROPS gives you an organized catalogue, customer-linked orders and connected web/Telegram shopping. Keep address control separate, with named ownership for its registration, DNS and recovery.
First identify what address you have
Write down the exact customer-facing hostname. Your business may hold the registration for a domain, or you may use a subdomain supplied by a platform. Those arrangements create different handover options.
If the address sits beneath somebody else’s domain, ask what rights you have to retain it, redirect it or use it after the contract ends. Do not assume the whole parent domain can be transferred to you.
Obtain the registrar and registration record through the supported interface. Check holder, expiry, renewal and transfer restrictions. Public lookup need not show private registration details.
Separate three moves that vendors often bundle together
A registrar move changes the company administering the domain registration. A DNS change changes the records directing the address to websites, email or other services. A shop-data move transfers agreed business information into the destination platform.
Each needs its own owner and acceptance test. Transferring the registration does not import your products or customer records. Changing the website destination does not automatically move email. Moving catalogue files does not transfer domain recovery control.
ICANN’s registrant guidance explicitly distinguishes changing hosting or nameservers from changing registrars. Ask which operation is actually needed before approving a transfer. ICANN domain-transfer FAQs.
Use a control-and-proof handover sheet
This is an owner checklist, not a request for the vendor to paste passwords into a document.
| Control | Confirm | Evidence |
|---|---|---|
| Registration | Business details and decision-maker | Current record |
| Registrar | Business-controlled account and delegated access | Independent owner sign-in |
| DNS | Provider, nameservers and record inventory | Change authority known |
| Renewal | Expiry, payer and notices | Status visible |
| Recovery | Business-controlled recovery routes | Process confirmed privately |
| Destination | Hostname and shop responsibility | HTTPS and routes checked |
| Business data | Agreed transfer scope | Reconciliation complete |
Keep authorization codes and other secrets in the approved secure channel. The sheet should record who completed each action and what was checked.
Check the rules for your actual domain extension
Under ICANN's Transfer Policy, a registrant change can trigger a 60-day registrar-transfer lock. Check the registrar's supported process before changing ownership or planning a transfer. Current ICANN Transfer Policy
Country-code domains need their own policy check. For example, IANA classifies .st as a country-code top-level domain. Do not apply a generic-domain transfer timetable to it merely because the address belongs to an international business. Ask the relevant registrar and registry to confirm the requirements. IANA .ST delegation record.
Hypothetical example: a shop changing website vendors
A shop owner wants a DROPS storefront behind the address customers already recognize. The departing vendor manages DNS, while the owner holds the registration account. Email uses the same domain through a separate service.
The owner’s first task is to recover business control of DNS administration and obtain the record inventory. A registrar transfer is a separate decision. The website change must preserve the required email records, and the shop-data plan must identify exactly which catalogue and business records will move.
Accept the handover beyond the homepage
Before signing off, check independent account control, the intended HTTPS shop and routes, required email/services, old-link decisions, reconciled data and the departing vendor's remaining access.
Schedule the change and its recovery path with the responsible providers. A handover plan should describe potential interruption and link changes; it should not promise automatic zero downtime or unchanged search rankings.
Give your shop a destination and your address an owner
DROPS puts your catalogue and customer-linked orders into a coherent shop workflow. Use that as the operating destination, then require explicit responsibility for the public address, DNS and record transfer around it.
See the platform at DROPS.ST and explore the shop demos. Bring the exact hostname, current provider list and completed handover sheet so the migration discussion starts with confirmed control, not assumptions.