X
How to Prepare a Bulk 도메인 이전 List
받는 사람 prepare a bulk transfer list, create a spreadsheet with each 도메인 name, current registrar, expiration date, lock status, AuthInfo / EPP code, DNS provider, nameservers, email provider, 도메인 status, owner 또는 client, TLD notes, pri또는ity, 및 risk level. Separate ready 도메인s from 도메인s that need unlock, fresh codes, DNS backup, renewal, ownership confirmation, 또는 special TLD review.
Who This Guide Is F또는
This guide is f또는:
· 도메인 invest또는s consolidating p또는tfolios
· Agencies managing client 도메인s
· 호스팅 providers moving customer 도메인s
· 리셀러s preparing large transfer 또는ders
· Businesses 또는ganizing 도메인 assets
Bef또는e You Start
Bef또는e you start, prepare:
· Permission to transfer every 도메인
· Current registrar f또는 each 도메인
· EPP codes can be requested
· Lock status can be checked
· DNS 및 email rec또는ds are backed up
· Expiration dates k지금n
· Client 또는 owner auth또는ization confirmed
· 결제ment 또는 reseller balance ready
Step-by-Step Instructions
Step 1: 생성 a Master Spreadsheet
Use structured columns rather than plain text lists.
· 도메인 name
· TLD
· Current registrar
· Expiration date
· Lock status
· EPP code
· DNS provider
· 이름servers
· 이메일 provider
· Owner/client
· Pri또는ity
· Risk level
Step 2: Clean the List
삭제 duplicates, misspellings, wrong extensions, expired 도메인s, 및 도메인s already at NiceNIC.
· 확인 exact spelling
· 확인 ownership 및 intent
Step 3: Group by Current 등록기관
Unlock 및 request codes efficiently by registrar.
· Each registrar may have different transfer-out w또는kflow
Step 4: Group by TLD
Some TLDs have special transfer rules, pricing, 또는 document requirements.
· Separate ccTLD 및 restricted TLDs
Step 5: 확인 Expiration Dates
S또는t by expiration 및 flag near-expiration 또는 expired 도메인s.
· Avoid last-minute transfer risk
Step 6: 확인 Lock 상태
Rec또는d locked, unlocked, clientTransferProhibited, serverTransferProhibited, 또는 unk지금n.
· 제출 only ready 도메인s first
Step 7: Request EPP Codes
Match one code to one 도메인 및 rec또는d request date.
· Protect codes from unauth또는ized access
Step 8: Back Up DNS 및 이메일 Rec또는ds
Flag 도메인s using old registrar DNS 또는 active business email.
· MX, SPF, DKIM, DMARC are critical
Step 9: 확인 Pricing 및 Premium 갱신al Risk
확인 transfer, renewal, 및 premium costs bef또는e moving client 또는 invest또는 도메인s.
· Avoid surprise renewals
Step 10: Assign Risk 레벨s
Classify low, medium, 및 high risk 도메인s.
· Transfer low-risk first
· H및le high-risk separately
Step 11: 제출 Ready 도메인 First
Do not let problem 도메인s block ready ones.
· Track status after submission
Step 12: Verify After Transfer
확인 account appearance, nameservers, website, email, privacy, lock, 및 auto-renewal.
· 아니요tify clients 또는 team
Troubleshooting
Many 도메인 Failed
Possible reasons:
· Locked 도메인s
· Wrong codes
· Bulk f또는matting issue
· Unsupp또는ted TLDs
What to do:
· Separate by err또는 reason
· Request fresh codes
· 제출 ready 도메인s only
Some 도메인 Transferred but Others Did 아니요t
Possible reasons:
· Different registrars
· Different TLD rules
· Approval missed
What to do:
· Track each 도메인 individually
DNS Risk Found Late
Possible reasons:
· Old registrar DNS
· Unk지금n DNS provider
· Business email not backed up
What to do:
· Pause affected 도메인s
· Back up 또는 recreate DNS first
Common Mistakes
Mistake 1: Sending a plain list without EPP codes
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 2: 아니요t checking lock status
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 3: Mixing up codes
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 4: Ign또는ing expiration dates
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 5: 아니요t backing up DNS
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 6: F또는getting business email rec또는ds
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 7: Treating all TLDs the same
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 8: 아니요t confirming client auth또는ization
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 9: 제출ting high-risk 도메인s with ready 도메인s
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 10: 아니요t updating the spreadsheet after submission
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
FAQ
1. What is a bulk transfer list?
A structured spreadsheet of multiple 도메인s with transfer 및 risk data.
2. Can I transfer many 도메인s to NiceNIC?
예, but prepare data carefully.
3. What columns should I include?
도메인, registrar, EPP, lock, expiration, DNS, email, owner, TLD notes, pri또는ity, risk, 및 status.
4. Do all 도메인s need EPP codes?
Many do, but some TLDs have special processes.
5. Should I transfer high-risk 도메인s first?
Usually no. Transfer low-risk 도메인s first.
6. How do I avoid downtime?
Back up DNS, identify old registrar DNS, 및 protect MX rec또는ds.
7. What if some 도메인s fail?
Group by reason 및 fix separately.
8. What should agencies check?
Client auth또는ization, ownership, DNS, renewal responsibility, 및 post-transfer account ownership.
받는 사람 prepare a bulk transfer list, create a spreadsheet with each 도메인 name, current registrar, expiration date, lock status, AuthInfo / EPP code, DNS provider, nameservers, email provider, 도메인 status, owner 또는 client, TLD notes, pri또는ity, 및 risk level. Separate ready 도메인s from 도메인s that need unlock, fresh codes, DNS backup, renewal, ownership confirmation, 또는 special TLD review.
Who This Guide Is F또는
This guide is f또는:
· 도메인 invest또는s consolidating p또는tfolios
· Agencies managing client 도메인s
· 호스팅 providers moving customer 도메인s
· 리셀러s preparing large transfer 또는ders
· Businesses 또는ganizing 도메인 assets
Bef또는e You Start
Bef또는e you start, prepare:
· Permission to transfer every 도메인
· Current registrar f또는 each 도메인
· EPP codes can be requested
· Lock status can be checked
· DNS 및 email rec또는ds are backed up
· Expiration dates k지금n
· Client 또는 owner auth또는ization confirmed
· 결제ment 또는 reseller balance ready
Step-by-Step Instructions
Step 1: 생성 a Master Spreadsheet
Use structured columns rather than plain text lists.
· 도메인 name
· TLD
· Current registrar
· Expiration date
· Lock status
· EPP code
· DNS provider
· 이름servers
· 이메일 provider
· Owner/client
· Pri또는ity
· Risk level
Step 2: Clean the List
삭제 duplicates, misspellings, wrong extensions, expired 도메인s, 및 도메인s already at NiceNIC.
· 확인 exact spelling
· 확인 ownership 및 intent
Step 3: Group by Current 등록기관
Unlock 및 request codes efficiently by registrar.
· Each registrar may have different transfer-out w또는kflow
Step 4: Group by TLD
Some TLDs have special transfer rules, pricing, 또는 document requirements.
· Separate ccTLD 및 restricted TLDs
Step 5: 확인 Expiration Dates
S또는t by expiration 및 flag near-expiration 또는 expired 도메인s.
· Avoid last-minute transfer risk
Step 6: 확인 Lock 상태
Rec또는d locked, unlocked, clientTransferProhibited, serverTransferProhibited, 또는 unk지금n.
· 제출 only ready 도메인s first
Step 7: Request EPP Codes
Match one code to one 도메인 및 rec또는d request date.
· Protect codes from unauth또는ized access
Step 8: Back Up DNS 및 이메일 Rec또는ds
Flag 도메인s using old registrar DNS 또는 active business email.
· MX, SPF, DKIM, DMARC are critical
Step 9: 확인 Pricing 및 Premium 갱신al Risk
확인 transfer, renewal, 및 premium costs bef또는e moving client 또는 invest또는 도메인s.
· Avoid surprise renewals
Step 10: Assign Risk 레벨s
Classify low, medium, 및 high risk 도메인s.
· Transfer low-risk first
· H및le high-risk separately
Step 11: 제출 Ready 도메인 First
Do not let problem 도메인s block ready ones.
· Track status after submission
Step 12: Verify After Transfer
확인 account appearance, nameservers, website, email, privacy, lock, 및 auto-renewal.
· 아니요tify clients 또는 team
Troubleshooting
Many 도메인 Failed
Possible reasons:
· Locked 도메인s
· Wrong codes
· Bulk f또는matting issue
· Unsupp또는ted TLDs
What to do:
· Separate by err또는 reason
· Request fresh codes
· 제출 ready 도메인s only
Some 도메인 Transferred but Others Did 아니요t
Possible reasons:
· Different registrars
· Different TLD rules
· Approval missed
What to do:
· Track each 도메인 individually
DNS Risk Found Late
Possible reasons:
· Old registrar DNS
· Unk지금n DNS provider
· Business email not backed up
What to do:
· Pause affected 도메인s
· Back up 또는 recreate DNS first
Common Mistakes
Mistake 1: Sending a plain list without EPP codes
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 2: 아니요t checking lock status
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 3: Mixing up codes
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 4: Ign또는ing expiration dates
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 5: 아니요t backing up DNS
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 6: F또는getting business email rec또는ds
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 7: Treating all TLDs the same
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 8: 아니요t confirming client auth또는ization
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 9: 제출ting high-risk 도메인s with ready 도메인s
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
Mistake 10: 아니요t updating the spreadsheet after submission
Review this item bef또는e making changes 또는 opening a supp또는t ticket.
FAQ
1. What is a bulk transfer list?
A structured spreadsheet of multiple 도메인s with transfer 및 risk data.
2. Can I transfer many 도메인s to NiceNIC?
예, but prepare data carefully.
3. What columns should I include?
도메인, registrar, EPP, lock, expiration, DNS, email, owner, TLD notes, pri또는ity, risk, 및 status.
4. Do all 도메인s need EPP codes?
Many do, but some TLDs have special processes.
5. Should I transfer high-risk 도메인s first?
Usually no. Transfer low-risk 도메인s first.
6. How do I avoid downtime?
Back up DNS, identify old registrar DNS, 및 protect MX rec또는ds.
7. What if some 도메인s fail?
Group by reason 및 fix separately.
8. What should agencies check?
Client auth또는ization, ownership, DNS, renewal responsibility, 및 post-transfer account ownership.
도움이 필요하신가요? 저희는 언제나 곁에 있습니다.
티켓 제출
