Moved to the cloud,
connections and all
We move applications and their data to the cloud, or from one cloud to another, with everything they connect to found first, inside your systems and out, so each step is planned around what depends on it.
Thanks, we’ll be in touch soon.
{{ heroStatus }}
{{ heroSay }}
You’re in good company
A few of the companies we’ve worked with.
{{ wallSay }}
More than the server list
Most moves start from a list of servers. What decides how a move goes is what the list leaves out: the jobs that run only at the end of a month or a year, the systems that call each other in ways no diagram shows, and everything outside your systems that knows them by their address, from partners and email to the networks your visitors use. Planning a move is mostly finding all of that first.
Here, an address is the name or number another system uses to reach yours, and the switch is the moment your users start using the new place.
Moving: Orders
Packed
- Web servers
- Database
- Files
Not on the label
- Jobs that run at month end
- Systems that call it
- Partners who know its address
- Mail sent in its name
What we do
Everything a move touches, found first and moved in the right order.
Everything it depends on, found
Servers, scheduled jobs, connections and accounts, found from how your systems actually talk to each other, and from the people who run them.
A move chosen for each system
Moved as it stands, moved onto services the cloud runs for you, or reworked first, by what each one needs.
Busy systems moved together
Systems grouped by how much they call each other, so no busy conversation is split between the two places.
The new place, set up first
Accounts in your name, networks, access and logging in place, written as code, before the first system arrives.
Databases moved while in use
Copied, kept in step with every change, compared with the original, and switched over with a short pause once any difference is explained.
Every address outside, updated
The names people reach you by, the servers allowed to send your email, partners’ lists of known addresses, and the links other services call.
The day, tried in advance
Every step of the switch written down and run on a copy first, the way back included.
Watched through a full cycle
The new place watched through your month end, or your busiest cycle, before the old one goes.
The old place, closed
Kept running until the new place has carried a full cycle of your business, and turned off only when you agree: data kept or deleted and contracts ended, as you decide.
Software to rework before it moves? Legacy Modernization →
Releases, security and day-to-day running once it’s there? Cloud, DevOps & Security →
Alerts and reliability targets once it’s there? Observability & SRE →
Pipelines and warehouses for the data that moved? Data Engineering →
Busy systems move together
For a while during a move, some of your systems run in the new place and the rest in the old one. Every call between them crosses the distance between the two. A page that asks its database many small questions in turn waits for each answer, so if the page moves and the database doesn’t, every one of those waits grows. So we find out which systems talk to each other, and how much, and move the busiest together.
- Website, Database and Search call each other often, so they move together.
- Monthly reports calls the database now and then, so it can move on its own.
Start with what’s running
We begin by finding what you run and what it talks to: from the systems themselves, from how they connect, and from the people who know the jobs that run once a quarter. You get a written map of every system and its connections, the groups we’d move together and the order we’d move them in, and a plan for the first group. Nothing moves until what it depends on, inside your systems and outside them, is found and written down.
The first group is a small one, well understood, so the way is tried before the systems your business can’t do without.
Work with us as a dedicated team, on a fixed price project or a mix of both. Compare engagement models →
How each is paid for: Pricing →
- FirstIntranetStaff directory
- WebsiteDatabaseSearch
- OrdersPaymentsStock
- Monthly reportsFile store
- Email sendingPartner feed
- Customer portalSupport desk
Questions worth asking
How long does a move take?
It depends on how many systems there are and how they connect. After the first look we can say how many groups there are and plan the first in detail. Each group after that is planned with what the one before it taught us.
Will our users notice the switch?
We plan each switch so they don’t, wherever the systems allow it. Where a database needs a short pause to catch up before it switches, we plan it for your quietest time and tell your users ahead.
Can we move one application first?
Yes, and we’d usually suggest it: a small one that’s well understood, moved from start to finish, so the ones after it follow a way you’ve already tried.
Which cloud should we move to?
The one that fits your systems, your team and what you already use. We compare the options against what your systems need, and set out what each would change for your team.
Should we change the software before we move it?
As a rule, only where it has to change to run in the new place. A system can often move as it stands, or with small changes, and be improved once it’s there. Where a system needs real rework first: Legacy Modernization →
Can we move from one cloud to another?
Yes. The work is the same: find what each system uses, set up the new place, move in groups and update every address outside. The services each cloud offers differ, so the plan says which have a close match and which need changes.
Will it cost less to run?
It can cost less, or more. It depends on what runs and how it’s sized. We estimate what each group will cost to run before it moves, sized from how it’s used today. Keeping costs owned once the systems have moved: Cloud Cost Optimization →
Do you run it for us after the move?
Either. Once it’s moved, we can run it with you: keep it patched and up to date, watch it, respond when an alert needs a person, and review access and costs on a regular rhythm. Or we hand it over to your team, with the runbooks and the knowledge behind them. The new place is set up in accounts you own, with access given to us, so the systems stay yours whoever runs them. Our engineers reach your data only for the move, or for a task you’ve agreed, and each time is recorded. Cloud, DevOps & Security →
What does a move cost?
It depends on what you run and what it connects to. The first call is free. Your proposal sets out the scope, the price or rate, and how you pay, before any work starts. Pricing →
Let’s run it better
Tell us what you run today and where you’d like it to be. We’ll suggest which group to move first.
Thanks, we’ll be in touch soon.
{{ ctaStatus }}