Procedure for adding customers from other Hosts

[Possum11]

Hi

Whats the procedure of transferring your new client who is already hosted with someone else..

For Example So they done loose any E-Mail

What other details do I need to know.. UDAI number is one for example..

cheers Possum..

[adwatson]

It depends a lot on the nature of the site being transferred - obviously a small site is easier than a large server with many sites, email accounts, etc. I think the key is to get the site up and running on the new server before transferring the domain, and ensuring a period of overlap as the domain updates, so no users end up going to a dead site.

[dbdev]

If working with MS based servers...

1. create a new site in IIS
2. use one of your IP addresses to that the site can be viewed from the internet...
3. when satisfied on the move and new deployment add a host header containing the domain name
4. modify DNS to point to your new server

I don't know anything about Linux but would be happy to answer further questions on site transfers using MS based servers.

Also, I don't know your level of knowledge on these things so if the isntructions are too simple or too complicated just ask for clarification (or PM me.)

Mike.

[jtara]

While I've never heard it called that before (I had to look it up) the UDAI has nothing to do with hosting.

(UDAI is apparently a term for the authorization code needed to transfer a domain registration from one registrar to another.)

As far as email, set-up the email server, test it, then change the MX record(s) in DNS. Make sure they keep their old mail server running until the TTL (time-to-live) on the old MX records expire.

For any DNS changes, it's useful to first lower the TTL for any records that are being changed. Let's say the TTL is 1 day. Change it it, say, 1 hour, then wait 24 hours for all caches to time-out. You can then change it again, to, say, 5 minutes, or less (not all DNS providers will permit you to change it to a very small value). Then wait an hour.

Bring up the new site.

If the site involves a database that is written-to, at this point, shut off that functionality on the old site, or simply have it display a "we are doing maintenance" page.

Finally, make your DNS changes. Some users will be inconvenienced for as long as 5 minutes. Much better than 24-48 hours of limbo.

After the small TTL has expired, kick the TTLs back up to your normal values. (Typically, 1-2 days.)

I haven't addressed the issues revolving around web server and script configuration, compatibility, and versions. That, it seems to me, is the bigger problem.