Cloud Migration Services
We plan and run Azure migrations for Swedish enterprises and public agencies. Portfolio assessment first, then wave-based cutovers with tested rollback plans, then cost tuning once you are running in the cloud.
- Minimal Downtime
- Cost Optimized
- Azure Certified
Why Migrate to Azure Cloud?
Pay for What You Use, Not for Peak Capacity
On-premise means buying for peak load and refreshing hardware every few years. In Azure you pay for actual usage, and most of the savings come from three mechanisms: reserved capacity on steady workloads, autoscaling, and shutting down idle environments. We set all three up as part of the migration.
- No hardware refresh cycles to fund
- Consumption pricing instead of capacity you sized years ago
- Autoscaling and auto-shutdown for dev and test environments
- Reserved instances and Azure Hybrid Benefit on steady workloads
Shorter Path from Idea to Production
In Azure a new environment is a Bicep or Terraform deployment, not a purchase order. Managed databases, queues, AI APIs and analytics services are available when a project needs them, without racking servers first.
- Provision full environments in minutes with Bicep or Terraform
- EU regions available, including Sweden Central for data residency
- CI/CD with GitHub Actions or Azure DevOps
- Managed AI, data and analytics services on the same platform
Migration Strategies (The 7 Rs)
Rehost (Lift & Shift)
Move servers to Azure VMs as they are, using Azure Migrate. No code changes. You get current hardware, snapshots and off-site backup from day one, and can modernize later.
Replatform
Move web apps to App Service and databases to Azure SQL with small configuration changes. Fewer servers to patch and operate than raw VMs, usually for a few weeks of extra work.
Refactor (Cloud-Native)
Rebuild the parts that change often as containers or functions. The most work of the three, and the payoff is real scale-out and lower run cost where the load actually is.
Repurchase (SaaS)
Where a standard product fits, replace the self-hosted system with SaaS such as Microsoft 365 or Dynamics 365. Nothing left for you to operate.
Examples: Email → Exchange Online, CRM → Dynamics 365
Retire
Most portfolios contain systems nobody uses anymore. The assessment finds them, and switching them off is the cheapest migration there is.
Typical: Unused applications turn up in almost every assessment
Retain (Revisit)
Some systems should stay on-premise for now: a compliance constraint, a hardware dependency, or a license that has not run out. We document the reason and set a review date.
Reasons: Compliance, dependencies, contract terms
Our Cloud Migration Services
Assessment & Planning
- Application portfolio inventory
- Dependency mapping between apps, servers and databases
- TCO comparison against your current running costs
- Migration strategy per application (7 Rs)
- Risk assessment with mitigations
- Timeline and resource plan
- Business case you can put in front of the board
Infrastructure Migration
- VM migration with Azure Migrate
- Network design, VPN or ExpressRoute to on-premise
- Active Directory and Entra ID integration
- Load balancing and traffic management
- Disaster recovery with Azure Site Recovery
- Backup and retention policies
- Reserved instances and right-sizing from the start
Database Migration
- SQL Server to Azure SQL or SQL Managed Instance
- PostgreSQL and MySQL to managed Azure services
- Oracle migration paths, including schema conversion
- Continuous data sync so cutover is a switch, not a copy
- Schema and compatibility analysis before the move
- Performance tuning after migration
- Cutovers planned inside short, agreed windows
Application Modernization
- App Service and Container Apps for web workloads
- Containerization with Docker and AKS
- Splitting monoliths where the seams make sense
- API Management as the front door
- Azure Functions for event-driven and scheduled work
- Queues and events instead of nightly batch jobs
- CI/CD pipelines so deploys are routine, not events
Security & Compliance
- Microsoft Defender for Cloud from day one
- Identity and access with Entra ID and RBAC
- Network segmentation with NSGs and private endpoints
- Key Vault for secrets, keys and certificates
- GDPR requirements and ISO 27001-aligned controls
- Threat detection and alerting in place before go-live
- Penetration testing of the migrated environment
Optimization & Support
- Cost analysis: where the bill actually comes from
- Monitoring and alerting with Azure Monitor
- Autoscaling rules tuned to your traffic pattern
- Review against the Well-Architected Framework
- Landing zone with policy and governance built in
- Training so your team runs the platform themselves
- Managed operations if you would rather we run it
Our 5-Phase Migration Process
Assess & Discover (Week 1-3)
3 weeksFull inventory of applications, servers, databases and the dependencies between them, using Azure Migrate and your CMDB. The output is a per-application strategy, a cost comparison and a wave plan, not a slide deck.
Tools:
- Azure Migrate
- Azure TCO Calculator
- ServiceNow / CMDB
Deliverables:
- Application inventory
- Migration strategy per app
- TCO & business case
Output:
- Migration roadmap
- Risk register
- Cost estimates
Design & Pilot (Week 4-6)
3 weeksWe deploy the landing zone, connect networking and identity, and then migrate one or two low-risk applications for real. The pilot proves the approach and the runbooks before anything important moves.
Activities:
- Landing zone deployment
- VPN/ExpressRoute setup
- Pilot migration
Deliverables:
- Azure architecture
- Network topology
- Runbooks & procedures
Success Criteria:
- Pilot apps running in production
- Team trained on the runbooks
- Approach validated
Migrate (Wave-Based) (Week 7-20)
14 weeksApplications move in waves, lowest risk first. Each wave gets the same treatment: migrate, test, cut over inside an agreed window, then two weeks of hypercare while the dust settles.
Wave Structure:
- Wave 1: Dev/Test (low risk)
- Wave 2-3: Production apps
- Wave 4: Mission-critical
Per Wave:
- Migrate & configure
- UAT & cutover
- 2 weeks hypercare
Guardrails:
- Rollback plan tested before each cutover
- Data verified before the switch
- Cutover inside an agreed window
Optimize (Week 21-24)
4 weeksThe first bill after a migration is rarely the right one. We right-size VMs, buy reserved capacity for steady workloads, shut down idle environments on a schedule, and harden security now that the shape of the load is known.
Cost Optimization:
- Right-size VMs
- Reserved Instances
- Auto-shutdown dev/test
Performance:
- Database tuning
- CDN setup
- Caching strategies
Security:
- Defender enablement
- Just-in-time access
- Compliance validation
Operate & Improve (Ongoing)
ContinuousAfter go-live we keep costs, capacity and incidents under regular review, and maintain a modernization backlog so replatforming work happens where it pays off, not everywhere at once.
Operations:
- Continuous monitoring
- Incident response
- Patch management
Governance:
- Cost reviews (monthly)
- Compliance audits
- Capacity planning
Innovation:
- Modernization backlog
- New service adoption
- Architecture reviews
Ready to Migrate to Azure?
Start with a free cloud readiness assessment. We inventory your servers and applications and come back with a migration plan, a cost estimate and a timeline you can hold us to.