Cloud Migration Architect | Azure Cloud Migration
Save this job and keep your search organized
Create a free account to save jobs, create alerts and return to this listing from your dashboard.
By continuing, you agree to our Terms & Privacy Policy.
Job Title – Cloud Migration Architect | Azure Cloud Migration
Location - Remote (United States)
Experience - 12+ years in IT infrastructure or application architecture, including 5+ years on Azure and 3+ large-scale migrations
Employment Type – contract
Duration – thru Feb 2028
CitiusTech is a leading digital and enterprise AI company for healthcare and life sciences organizations. We enable 140+ enterprises to build a human-first ecosystem that is efficient, effective, and equitable. Leveraging deep domain expertise and next-generation technologies including AI, Cloud, Data, and Intelligent Automation, we assist our clients to realize their vision, accelerate transformation, and achieve business outcomes. With 7,700+ healthcare technology professionals worldwide, CitiusTech powers digital innovation, business transformation, and industry-wide convergence through next-generation technologies, solutions, and products.
Why CitiusTech
Healthcare isn't just another industry for us. It's our singular focus. For 21+ years, we have combined technology and domain expertise to shape better healthcare outcomes. As part of CitiusTech, you will build future-ready skills while becoming an expert in a domain where innovation creates real human impact.
Here's an opportunity to be part of that journey.
Position Summary
We are hiring a Cloud Migration Architect to own the technical end-to-end migration of in-scope data center applications to Microsoft Azure. The architect leads every application through planning, design, migration, cutover, and hypercare, while being the single technical authority for migration decisions. Cloud Migration Architect will be a team leader and must be able to delegate and empower engineers. A successful architect will also serve as one of the primary client-facing roles, capable of both leading workstreams and communicating decision points with leadership.
Engagement: CitiusTech is delivering a multi-wave data center migration (DCM) for a US health payer whose members are federal employees, retirees and their families. The workload mix covers security and identity platforms (privileged access, PKI and certificate management), infrastructure tooling, GRC and enterprise content applications, with their databases and integrations. Program operates in a regulated healthcare environment under HIPAA, HITECH, and HITRUST.
Key Responsibilities
1. Plan
- Validate discovery data for each application: servers, databases, dependencies, integrations, certificates, service accounts and firewall flows.
- Choose the migration pattern for each application (rehost, replatform, refactor, rebuild or retire) and its database approach.
- Group applications into move groups and waves with the PMO, applying change blackouts, contract end dates and dependencies.
- Build and maintain the application migration playbooks, runbooks and rollback plans.
2. Design
- Produce the target-state design for each application on Azure: landing zone placement, compute, storage, networking, identity, backup and DR.
- Align designs with the Azure landing zone, hub-and-spoke network and governance policies.
- Define security controls for HIPAA, HITRUST and federal program requirements, covering encryption, privileged access, logging and data residency.
- Present designs at architecture reviews and take them through the client's Cloud Governance Committee for approval.
3. Migrate
- Direct build of target environments using infrastructure as code (Bicep, ARM or Terraform) and Azure DevOps pipelines.
- Lead server, application and database migration using Azure Migrate, Azure Site Recovery, Azure Database Migration Service and native tools.
- Own the pre-production test approach with QA: functional, integration, performance, security and failover testing.
- Resolve technical blockers and make design trade-offs in time to hold the wave schedule.
4. Cutover
- Plan each cutover minute by minute, with go/no-go criteria,