# Server migration to Microsoft Azure

We move servers and business applications to Microsoft Azure: virtual machines, backup and disaster recovery, and Azure Virtual Desktop where it helps. We estimate costs up front so the bill holds no surprises.

- **What:** Servers, apps, backup, DR
- **Cost:** Estimated before migrating
- **Data:** In EU regions
- **After migration:** Monitoring and management

- ✓ Server and application assessment with cost estimate
- ✓ Azure landing zone: network, security, access
- ✓ Lift-and-shift or modernisation
- ✓ Backup and disaster recovery (DR)
- ✓ Azure Virtual Desktop for remote work
- ✓ Cost monitoring and optimisation
- …and more (not an exhaustive list)

## How we work

1. **Assessment and cost**: Servers, applications and their load; an Azure cost estimate before you decide.
2. **Azure setup**: Network, connection to the office, access, security settings and backup.
3. **Pilot move**: We move a less critical server first and test it with users.
4. **Migration and optimisation**: The remaining servers move at an agreed time; after a month we review sizes and cost.

## What you get

- **A cost comparison**: Azure vs your own server: hardware, power, licences, maintenance and risk.
- **A ready Azure environment**: Network, VPN to the office, access and security settings.
- **Backup and recovery**: Backups and a disaster recovery plan in the cloud.
- **Cost monitoring**: Budget alerts and regular optimisation reviews.

## Indicative timeline

| Phase | Duration |
|---|---|
| Assessment and cost estimate | 1–2 weeks |
| Azure environment setup | About 1 week |
| Pilot move | About 1 week |
| Migration and optimisation | 1–4 weeks + a review after a month |

Durations are indicative – you get an exact plan and dates in the proposal, after we have assessed your environment.

## What we need from you

To keep things moving, please have ready:

- a list of servers and applications with their purpose;
- admin access to the servers;
- your application vendors’ contacts (for cloud licensing and support questions);
- details of your office internet connection;
- an existing Azure subscription, or the go-ahead to create one.

## A typical project: a server out of warranty

**Situation.** The company’s server running its accounting software and files was out of warranty, and its Windows Server 2016 support ends in January 2027. The company didn’t want to invest in new hardware.

**What we do.** We compared Azure with a new server over several years, moved the server to an Azure virtual machine on a current Windows Server version, connected the office over VPN and enabled backups and budget alerts.

**Result.** No hardware refresh was needed, the application runs in the cloud, and the monthly cost is known in advance.

A composite example based on our most common projects.

**Is Azure more expensive than our own server?**

Not necessarily. We compare the full cost – hardware, power, licences, maintenance and risk – and show you the numbers.

**What if a Lithuanian data centre suits us better?**

Then we propose a [move to a data centre](https://ithink.lt/en/cloud-migration/data-centre/) – we choose the option that fits your needs.

**Will our applications run in Azure?**

Most Windows applications run unchanged. During the assessment we check licensing and cloud support with your application vendors.

**Where will our data be stored?**

In Azure regions within the European Union – we choose the region with you.

- [To a data centre](https://ithink.lt/en/cloud-migration/data-centre/)
- [Windows Server 2016](https://ithink.lt/en/cloud-migration/windows-server-2016/)
- [Infrastructure management](https://ithink.lt/en/it-support-services/infrastructure-management/)

---
Source: https://ithink.lt/en/cloud-migration/azure/
