Cloud & server migration · Udupi & Mangaluru
We move working websites, stores and business software to a better server, with files, database, email and domain settings carried across. Our studio is in Udupi, open for a visit, and we are still around once the new server is live.
In short
Cloud and server migration means moving a working website or business system, with its files, database, email and domain settings, from one server to another, such as from shared hosting to a cloud server. Whirl Designs runs these moves from Udupi for businesses in coastal Karnataka. Each site is tested on the new server first, and the old server stays running as a way back.
Start here
A slow or crowded website does not always need a cloud server. Each of these three homes suits a different kind of site, and every step up brings more to look after.
Best for: Most business websites, small stores and many web apps
Best for: A busy store, a web app, or software with background jobs
Best for: Systems that must grow, or must keep data in India
If a better shared host fixes the problem, you will hear that on the first call, and that is where we will move you.
Our work
None of our client work yet includes a move to a cloud server that we can put on this page, so you will not find a case study here. The move checklist at the top of the page is an example with made-up figures.
What we can point to is the part of any move that decides whether it is safe: knowing that a system can be copied and brought back whole. We run our own software that way.
Closest projects
ERP Sutra
Software products · Karnataka
Our own product arm — a shared platform layer with two industry ERPs built on top of it, both live with paying users rather than sitting in a pitch deck.
Rebar — Construction ERP
Construction ERP · Private system
Site-to-payroll software for reinforcement-steel contractors: bar bending schedules, sub-contractor bills, weekly labour runs and the statutory returns that follow them.
What you get
Copying files is the easy part of a move. These six parts are the rest of it, and all six are written into the move plan before work starts.
How it runs
Your customers keep using the old server until the new one has passed every check. Pointing your domain at the new server comes last.
A careful look at your current host: disk space, memory limits, traffic, PHP version, scheduled jobs and who holds each login. Nothing is changed at this stage.
Shared host, VPS or cloud, and which region. The plan lists what moves, in what order, when the switch happens and how we would undo it. Nothing starts until you have read it and agreed.
Every domain has a setting, called TTL, that tells the internet how long to remember where your site lives. A day or two ahead we cut it to a few minutes, so the switch spreads fast and can be reversed fast.
The new server is set up and your site copied onto it. Then the whole move is rehearsed once, so the real switch follows steps that have already been tried and timed.
We pick an hour when few customers are on the site, often late in the evening. The last changes are copied across, DNS is pointed at the new server, and then mail, forms and error logs are watched as visitors arrive.
Where your old host allows, the old server stays as it was for a week or two, so you can switch back if something turns up. Once mail, forms and Google Search Console look clean, you close the old account, and the new server passes to whoever will look after it: us, or your own IT person with our notes.
Not a fit
Moving servers is not always the answer to a slow or unhappy website.
Questions
Usually only for a few minutes, and often not at all. The new server is built and tested while the old one keeps running, and DNS changes only at the end. A plain website sees no break. A store or billing system pauses new orders for a few minutes during the last database copy, so that no order is saved on the old server after it has been copied.
Not if the page addresses stay the same and the site stays up. A server move changes where the site lives, not its addresses, so Google keeps the pages it already knows. We check that the padlock (HTTPS), the sitemap and the robots.txt file, which guide Google around the site, came across unchanged. Then we watch Google Search Console for errors in the weeks after the switch.
Move when your host warns you about resource limits, the site slows at the same busy hour every day, background jobs stop before they finish, or you need software the host will not install. If none of that is happening, shared hosting is probably still enough, and a better shared host may be all you need.
Moving a typical business website usually takes a few days from start to finish, and most of that is testing. The switch itself takes minutes. A store, a web app or business software with years of records and scheduled jobs usually takes one to three weeks. The date often depends on how quickly the old hosting, domain and DNS logins can be found.
It should keep working right through the move. Mailboxes are ready on the new side before DNS changes. For a day or so after the switch, some mail may still reach the old server while the change spreads, so we collect it from there and copy it across. If email shares a host with the website, it can be a good moment to move it to Google Workspace or Microsoft 365, so one problem cannot take down both.
Many hosts will, and their move copies the files and the database. What it usually leaves out is the rest of the job: the mail records, scheduled jobs and hidden settings of the old host, a hand test of forms and payments on the new server, and a way back if the switch goes wrong. Those are the parts we plan, test and write down.
Yes. We set up the server in an Indian data centre, such as the Mumbai or Hyderabad region, which keeps data in the country and close to your customers in Udupi and Mangaluru. The account is registered to your business, with its GST number, so it stays yours. We will also tell you plainly when a simpler host would do the same job with less to look after.
Often, yes, if it is web-based software or a database that a server can run. Moving it to a cloud server lets branches and staff on phones use it without the office computer staying on. We can visit your office, whether it is in Udupi, Manipal, Karkala, Kundapura or Mangaluru, to copy it, and the office copy stays untouched until the new one is proven.
Worth reading first
Clean, documented, tested code on a modern, proven stack — the foundation that keeps your cloud & server migration fast and dependable for years.
Ready when you are
Tell us where your site or software runs today and what is going wrong, and we will send you a written move plan to read before anything is touched.
