· 1 min read
Moving servers and files to Amazon Web Services or Microsoft Azure can reduce the equipment you look after and make remote work easier. It can also bring surprise bills, broken connections and a weekend of lost work. Most of that can be avoided with questions asked early.
Five questions to answer first
- What do we run today, and what depends on what? Applications that talk to each other should move together or not at all.
- What should not move? Some systems are better left where they are, or retired.
- What will it cost each month? Ask for an estimate and set spending alerts before you start.
- How do we get back if a step fails? Keep the old system running until the new one is proven.
- Who looks after it afterwards? Cloud services still need updates, access reviews and monitoring.
Do it in steps
Start with something small and low risk, such as file shares or a test system. Learn from it, then move the important systems. Test each step with real users before you call it done.
Which platform fits depends on what you already use. Azure often suits businesses that rely on Microsoft products. We compare the options against your needs before recommending one.
General information. It is not legal or professional advice for your situation.