The agency keeps the site's hosting on their own servers — we can't control it, it becomes a crisis if there's a problem

I had the same issue, the agency kept the hosting on their own account. Then when I got mad at the agency, they said: 'okay, migrate it then'. Of course we couldn't migrate because all the files were with them. We switched to another company, they opened hosting under the customer's name, and we control it. Much more comfortable.

the agency said on day one: 'we manage the hosting but control is yours'... so the agency has it on their account but gave me the password... worked out better.

Control Steps: 1. Read the contract: which party manages the hosting? 2. Send a written request: hosting details (FTP, cPanel, passwords) 3. Who is the domain registered to in the registry? 4. Make a written agreement for data migration 5. Confirm you have access rights to backups 6. Define an emergency protocol (in case the agency collapses)

Is there really nothing written in the contract about data transfer? Did you ask the agency? Maybe there's an unwritten agreement, why did you ask? Asking for written info is the right step but you might need to be a bit more aggressive.

Hosting and domain control is very important! Write to the agency immediately, ask for hosting details. If they avoid giving it, show it to your contract advisor. You're paying the money after all you have a right to the info. Move to another agency if necessary but get written permission first.

I have an objection here. When making a decision, first look at what data you have on hand.

Thats all, sorry if I went on too long.

There's a trap here, let me mention it. Taking notes for two weeks yields better results than a six-month estimate.

If you have questions, write them; I'll answer as best I can.

I'm curious too. Everything goes well for the first three months; problems arise in the fourth.

Proven by experience.

Looking at it as a process, the picture changes. Don't hesitate to ask; those who don't ask always pay more.

We got stuck at the same point for a while. Everyone rushing into is hosting with the agency or with me gets stuck at the same point.

That's all sorry if I went on too long.

This thread is archived. The harder it is to reverse a decision, the slower you should make it.

Let me share my experience. Everyone rushing into is hosting with the agency or with me gets stuck at the same point.

When making a decision, first look at what data you have on hand. I'm also curious if anyone does it differently.

Great work. Mistakes made on the is hosting with the agency or with me side are usually reversible but expensive.

Just leaving this note, it might be useful.

Let me speak from the other side; I'm on the supplier side. In legacy systems the most expensive thing is unknown dependencies.

I'm also curious if anyone does it differently.

the answer above hits the nail on the head. most time waste accumulates in tasks waitiing for approval.

if I were you, I'd go this route.

Great work.

I'm curious too. The biggest time-waster for us was not knowing who had the final say.

That's all, sorry if I went on too long.

I felt relieved reading this answer, so it's not just me. If it's your first time, start small; scaling comes later.

That's all, sorry if I went on too long.