Moving domains in ยท arranged by our team
Domain Transfer to PKDomain.net
Bring .pk names and international domains over from another provider without breaking the website or the mailboxes that depend on them. Transfers are not ordered through the online cart; our team arranges each one, checks the domain's status first and walks you through the registry's requirements, so this page explains how to prepare.

How transfers are handled
Domain transfers are arranged personally, not through the cart
Every registry has its own rules for moving a name between providers, and the right sequence depends on the extension, the current provider and how close the name is to expiry. Rather than offering a one-size checkout, we look at each request first.
Arranged by our team
Talk to us before you start a transfer
Send the list of domains you want to move, the provider each one is with now and its expiry date. Our team will check the status of each name, explain what the registry requires, confirm any cost and tell you exactly what to do at your current provider, in English or Urdu.
Transfer sequence
The stages of moving a domain to PKDomain.net
Contact our team
Share the domains, current provider and expiry dates. We check status and confirm the requirements for each extension.
Prepare at the old provider
Remove any registrar lock, confirm the registrant email works and request the authorisation code where one is used.
Freeze DNS
Record every existing record and leave the nameservers alone so the website and mail keep resolving during the move.
Approve the request
Confirm the transfer from the registrant email or as the registry requires, then let the process complete.
Verify and tidy up
Check the new status, confirm records with dig, and only then decide whether DNS should move as well.
Good reasons, and weak ones, for transferring a domain
The strongest reason to move a domain is consolidation. When names are scattered across several providers, renewals arrive from different places, logins are forgotten and nobody is sure where DNS is hosted. Bringing them into one client area, next to the hosting or server they point to, removes a whole category of avoidable mistakes.
Support is another good reason. If the current provider is slow to answer, hard to reach in your time zone or unable to explain a problem, moving to a team that answers by phone, email and ticket in English and Urdu can save hours when something goes wrong at an inconvenient moment.
Payment convenience matters too, especially for Pakistani businesses billed in foreign currency on an international card. Moving names to a provider that accepts local bank transfers and mobile wallets can make renewals far easier to approve inside the company and less likely to be missed.
A weak reason is chasing a small saving on a single invoice. A transfer takes some effort and carries a little risk, so it is worth doing for lasting benefits rather than for a one-off difference. If price is your main concern, compare the renewal figures over several years before deciding.
What to check at your current provider before anything moves
Log in to the current provider and look at the domain's status. Many providers apply a registrar lock by default to stop unauthorised transfers; it has to be lifted before a move can start. If you cannot find the setting, ask their support to remove it and to confirm in writing when they have done so.
Check the registrant email address. Transfer approvals are usually sent there, and if the address is out of date or on a mailbox nobody reads, the request will stall. Update it first if you can, and give the change a little time to settle before requesting the move.
For most generic endings, you will need an authorisation code, sometimes called an EPP code or transfer key, which proves you are entitled to move the name. Request it from the current provider and keep it private. Some country registries, including PKNIC for .pk names, use their own procedures instead, which our team explains for each case.
Finally, note the expiry date and the date the name was registered or last transferred. Registries commonly block moves for a period after registration or a previous transfer, and a name very close to expiry may need renewing first. Sharing both dates with our team at the start avoids a request that is bound to fail.
Keeping records answered while the registrar changes
The single most useful rule for a smooth transfer is to separate the registrar change from the DNS change. The registrar is who manages the name; the nameservers are who answers for it. If the nameservers stay the same throughout the transfer, visitors and mail servers notice nothing at all.
Before starting, export or copy every record in the current zone: A and AAAA records for the site, CNAMEs for subdomains, MX records and their priorities, and TXT records for SPF, DKIM, DMARC and service verifications. A screenshot is better than nothing, but a plain-text list is easier to recreate accurately.
Check what is actually being served, not just what the panel shows. Run dig NS, dig MX and dig TXT against the domain and save the output. If the panel and the live answers differ, the panel you are looking at is not the authoritative one, and you need to find out which provider really hosts the zone.
If the old provider's nameservers will stop working when the domain leaves, recreate the zone in our DNS first and switch the nameservers before the registrar transfer begins. Wait until dig shows the new nameservers answering correctly from a public resolver, then proceed with the move itself.
Checks to run once the domain has arrived
Once the transfer completes, the domain appears in your client area here. Check the expiry date first. For many generic endings a completed transfer adds time to the term, while for others the date stays the same; either way, confirm that the date shown is what you expected and that auto-renewal settings suit you.
Next, confirm the registrant details are unchanged. The holder name, organisation and contact email should match what was on the domain before. If anything looks different, raise it straight away, because correcting a registrant record is far easier soon after a move than months later.
Run the same DNS checks you ran before the move and compare the output. The nameservers, A records, MX records and TXT records should be identical. Load the website on mobile data as well as workplace Wi-Fi, and send a test email to an external mailbox and back to confirm mail flows in both directions.
Finally, close the loop with the old provider. Cancel any renewal that was set up there so you are not billed twice, but do not close the account until you are sure no other services, such as hosting or mailboxes, still depend on it. Keep a note of the transfer date with your domain records.
Transferring many domains without losing track of any
When dozens of names are involved, organisation matters more than speed. Build a list with each domain, its current provider, registrant, expiry date, nameservers and whether it carries a website or mail. That list becomes your checklist and your record of what has moved and what has not.
Group the names by registry and current provider, because each group follows the same steps. Move a small test group first, ideally names that do not carry live mail, to confirm the process works with your old provider. Once that group has arrived cleanly, the rest can follow in larger batches.
Leave the most important names, such as the one your company email runs on, until you are confident in the process, and schedule them for a quiet period rather than the week of a product launch or a busy sales season. A calm transfer is a safe transfer.
As each name arrives, tick it off and run the post-transfer checks. When the list is complete, align renewal dates if you wish, so that the whole portfolio falls due together, and store the final list with your company records for whoever manages the domains in future.
Extension differences
How transfers vary between .pk and international names
The general sequence is the same everywhere, but the details differ by registry. Our team confirms the current requirements for each name before you start.
| Aspect | .pk family | Most generic endings such as .com | Other country endings |
|---|---|---|---|
| Who sets the rules | PKNIC | The ending's registry | Each country's registry |
| Proof of entitlement | PKNIC's own procedure | Authorisation or EPP code | Varies; some use their own method |
| Registrar lock | Depends on the current provider | Usually on by default; remove first | Varies by registry |
| Effect on expiry | Confirmed case by case | Often adds time to the term | Varies by registry |
| Approval | As PKNIC requires | Usually via registrant email | Varies by registry |
Snapshot first
Recording a zone before a transfer, with dig
Run these before you request anything, save the output to a file and keep it until the move is complete. Replace the example domain with your own.
dig NS yourdomain.com.pk +short > before.txt
dig A yourdomain.com.pk +short >> before.txt
dig MX yourdomain.com.pk +short >> before.txt
dig TXT yourdomain.com.pk +short >> before.txt
After the transfer, run the same commands into a second file and compare the two with diff. Any line that appears in one file and not the other is a record that changed, and it is worth understanding why before you call the move finished. Subdomains such as www, mail or shop need their own queries, so add a line for each one your setup relies on.
diff before.txt after.txt
It also helps to note the TTL on each record before you begin, which dig prints when you leave off the short flag. A record with a TTL of a day can take up to a day to change everywhere if you ever do need to edit it mid-move. Lowering the TTL a day or two before planned DNS changes gives you room to correct a mistake quickly, and you can raise it again once everything has settled.
dig A yourdomain.com.pk @1.1.1.1
Keep both snapshot files with the rest of your domain notes. If a question about a missing record comes up weeks later, they are the quickest proof of what the zone contained on the day the transfer started.
Domain and server together
Pairing a transferred domain with hosting or a VPS here
Once a domain has arrived, many customers take the next step and move what it points to. That is entirely optional, but having the name and the server in one account means one login, one set of invoices and one team that can see both halves of a problem when a site stops responding.
If the website runs on shared hosting, the plans include free migration of files, databases and mailboxes, so our team copies everything across and tests it before you switch any records. If you need root access instead, KVM virtual servers in Karachi, Islamabad and the global range accept any stack you choose to deploy.
Plan the order of changes calmly. Let the domain transfer settle first, migrate the site next, and switch the A and MX records last, after testing the new server through a hosts-file entry. That way each step can be checked on its own, and if something looks wrong you know exactly which change caused it.
- Domain first, website second, records last
- Free migration on shared hosting plans
- Test through a hosts-file entry before switching

Transfer questions
Questions about transferring a domain
Does moving a domain to you change who owns it?
No. A transfer changes which provider manages the name on your behalf, not who holds it. The registrant should stay exactly as it was, whether that is you personally or your company. If you also want to change the holder, for example after a sale, tell our team at the start, because ownership changes follow their own registry procedure and are best handled as a separate, clearly documented step.
Will my website go offline while the domain is moving?
It should not, provided the DNS stays answered throughout. The safest approach is to leave the nameservers unchanged during the transfer so the same servers keep serving the same records. Only once the move has completed, and you have checked that everything resolves, should you consider moving DNS too. Changing provider and DNS on the same day is what usually causes outages.
Can I transfer a domain that expires next week?
It is better not to cut it that fine. A name close to expiry may need renewing at the current provider first, and some registries refuse or delay transfers in the last days of a term. Raise it with our team as early as possible, quoting the exact expiry date, and they will advise whether to renew first or proceed with the transfer straight away.
Why was my transfer request rejected?
Common causes are a registrar lock that was not removed, an incorrect or expired authorisation code, a registrant email that did not confirm the request, or a name that was registered or transferred too recently. For .pk names, missing details in the request can also hold things up. Our team will tell you which step failed so you can fix that one thing and resubmit.
Do I need to move my hosting at the same time?
No. The domain and the hosting are independent, and there is no need to move both together. Many people transfer the domain first, keep the website exactly where it is, and decide about hosting later. If you do want both moved, the shared plans include free migration of the website and email, which is usually best scheduled after the domain has settled.
What do I do if my old provider will not release the domain?
Start by asking them in writing for the authorisation code or the release your registry requires, and keep a copy of the request. Make sure the registrant email on the domain is one you can access, since that address normally has to approve the move. If they still refuse, explain the situation to our team and we will advise what the registry's procedure allows.
Can I move many domains in one go?
Yes. Send our team the full list with the current provider for each name, and they will group the work so names under the same registry move together. It is wise to start with one or two less important names, confirm the process works smoothly with your old provider, and then move the rest of the portfolio in a single batch.
Is there a guarantee that my email will keep working?
Email depends on MX, SPF and DKIM records, so it keeps working as long as those records keep being served. Export them before you start, confirm them with dig after each step, and leave the nameservers alone until the move is complete. If mail is hosted with us, our team can check the records on your behalf before and after the transfer.
PKDomain.net · help in English & Urdu
Ready to bring your domains over?
Send our team the names, current provider and expiry dates. We check each domain and tell you exactly what to do next, before anything is moved.