Help for owners
My app runs on my old developer's own server
Short answer
If your app or website runs on a server in your developer's account, you depend on them for uptime, data and access, whatever the contract says. Find out what lives there, get a copy of the data, then move it to a server account your company owns in planned steps, with the old one left running until the move is checked.
Does this sound like your situation?
- I do not have a login for the server my app runs on.
- The hosting bill goes to my developer, or I pay them a monthly 'hosting' fee.
- I do not know where my customers' data is stored.
- My developer has left or stopped answering and the app is still running.
- I was told I cannot move my app because it is on their server.
Why does this happen?
It was the quickest way to launch
A developer with a server already running can put a client's app on it quickly. Nobody then moves it to the client's own account, and it stays there.
Hosting was bundled with the build
Some developers resell hosting with a markup. If that was never written down, you may not know the server exists as a separate thing you could own.
Several things live on one machine
The same server may hold your website, your API, your database, scheduled jobs, email sending and file uploads. Moving only part of it breaks the rest.
Only the developer knows the setup
Without notes, no one else knows which services run, how they restart, which keys they use or where backups go.
Technical detail: SSH to an EC2 instance fails with Permission denied (publickey,gssapi-keyex,gssapi-with-mic)
What can I do about it today?
- Find out what is on the serverAsk your developer for a plain list: which domain names, databases, scheduled tasks and outside services connect to it. A short written list is enough.
- Ask who pays and who owns the accountFind the hosting company and whether the account is in your company's name. Ownership of the account decides how easy the move will be.
- Ask for a full copy of the data and the codeBoth should be copied somewhere you control before anything changes. Do not delete or switch anything off on the old server.
- Check your domain name separatelyConfirm that the domain is registered in your company's name. If it is not, getting that right is the first job.
- Do not cancel the old hostingKeep it running until the new setup has been checked by real use. Cancelling early is the fastest way to cause an outage.
When should I bring someone in?
- Your developer does not answer, and you cannot log in to the server or see the hosting account.
- The server holds customer data, orders or payments.
- You need to move without any break in the service.
How do I handle it?
- Inventory the serverWith your developer's help or, if they are gone, through the access you have, I write down every service, domain, job and key the system uses.
- Build the same setup in your own accountA new server is made in a hosting account your company owns, with its own backups, and the app is installed and tested there while the old one keeps running.
- Switch over in a planned windowData is copied again just before the switch, the domain is pointed at the new server and I keep the old one running until the checks pass. A tested way back is ready.
- Hand over notes and accessYou receive a short document of how it runs and how to restart it, and the old access is removed once everything works.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I move without my developer's help?
It is much easier with it. If they have gone, I can often rebuild the setup from the app's code and your own copy of the data, though some details may need to be found out by testing.
Will my app go offline during the move?
The plan is built to avoid that. The old server keeps running while the new one is tested, then traffic is switched over in a planned window.
Is it wrong that my developer owned the server?
Not wrong in itself, but your company should hold the accounts that its business depends on. That is the part to fix.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.