Don't open this thread if you're not a website-builder/designer.

[Jeff Vh]

Quick question for website builders.

When building a new website for a new client, how do you transfer the client's domain to its new website?
Considering the client worked with another agency before.

Do you call the company your client worked with before to transfer the domain to your account?
Or how do you approach this? Also, if you do it this way, what are the agency's reactions?
Must be pretty funny, no?

 

[DunDidIt2X]

Depends on who controls the registrar, and the hosting.

 

[Jeff Vh]

Depends on who controls the registrar, and the hosting.

How do you find this information? WHOIS?
Most domains are 'protected', aren't they?

 

[693840]

I write up an email, and tell the client to send this to his old agency.

 

[DunDidIt2X]

How do you find this information? WHOIS?
Most domains are 'protected', aren't they?

Whois prolly wont work since its probably privacy protected. Your client should know. If he doesnt then his former agency probably controls everything, in which case you will need your client to send an email to former agency for that information.

 

[Jeff Vh]

@Blackhat Lifter @DunDidIt2X
Awesome, thanks for the replies.

 

[Yrior]

Just ask the client to call his agency and give them your account details for an easy push, it shouldn't take more than 5 minutes to do it unless the old agency is trying to delay things.

I actually had the same encounter with a client, things didn't end well between him and the agency he used to work with and he was the one who asked me the be the medium. Thankfully the team were decent and honoured my request rather quickly.

 

[Gogol]

It varies client to client, but I try not to purchase a hosting plan or a domain on his behalf. That's extra burdain for no real gain except for some pocket change for the affiliate may be? I don't need that, I need peace of mind.

What I normally do is ask for a barebone server, like a VPS with Ubuntu/CentOS installed. Then I configure everything on that server.

As for files, I always do it via git. I share the project with the client from bitbucket/or from my own gitlab server. That way, the client always has access to the code, and (s)he is never screwed over even if I am dead. As for the db, I use migration scripts, so that I don't have to run the sql scripts manually. I use Yii framework mostly, and it can do that out of the box.

Now, you might ask; what if the client does not pay you and run away with the files? Well, I wouldn't work without advance payment to begin with. That ensures that I am not screwed if the client runs away lol.

git helps to ease the production push and bugfixing. For example, if I fixed some bugs, I can just do (or tell the client to do)
git pull origin master
and run migration, if the db is changed. That way, I would never have to deal with FTP clients. Plus the files will always be backed up, and ready to be "re pulled" if it gets hacked or something. There are certain precautions that have to be taken with this approach though (like write permissions and stuffs.. but that's offtopic).

Oh, and as for pushing/pointing the domain, the client can just connect it with the new server by setting the proper dns records. If he can't, I would do it for him over teamviewer.

 

[Jeff Vh]

@magicoo @Gogol
Awesome insights, very useful stuff.

Thank you both!

 

[ss1180]

Client need to ask to the agency for the panel of domain and hosting.
Many times agencies make excuses but a good company just provide the details as per client request.

 

[marketpros44]

Just ask for asking to the hosting..

 

[Yrior]

@magicoo @Gogol
Awesome insights, very useful stuff.

Thank you both!

You're welcome, although @Gogol gave you a more detailed and indepth solution. I actually think I'll start doing what he recommended.