Enabling Cloud Transition and Migration
Trexin helped a specialty healthcare provider prepare for cloud adoption to support extended business growth.
Partnering with physicians and hospitals to develop, acquire, and operate outpatient treatment centers and provide patients with a full range of in‐center and at‐home specialty services, our Client had recently accepted a private equity investment to drive further growth. But after 20 years of business already serving 25,000 patients in over 300 facilities across 30 states, the infrastructure and IT support model in place did not have the scalability to support the projected growth. Recognizing a cloud adoption strategy to be a compelling remedy, leadership started down the cloud migration planning path but suspended efforts because they did not feel comfortable with prospective cloud vendor’s proposed approaches. To mitigate their concerns and re‐start the effort, the CIO asked Trexin to develop a cloud migration strategy, including a cloud technology architecture and a cloud support model.
Trexin adopted a phased approach, which in Phase 1 included: Stakeholder interviews; documentation of success criteria and business drivers; business process and application mapping; and an inventory of infrastructure, databases, applications, and security. In Phase 2 Trexin then developed an application dependency matrix, analyzed application cloud fitness, created a high‐level target architecture, itemized cloud support model options, and defined security compliance requirements and resilience patterns.
Excited by Trexin’s progress and eager to proceed, our Client asked us to then expand our Phase 3 project scope to cloud transition and migration enablement planning. This included: Standing‐up cloud migration oversight; establishing a cloud migration office; developing a detailed timeline for initial application migration; onboarding the migration team; negotiating contracts with 3rd party vendors; managing project interdependencies; completing a virtual desktop and file server POC; defining a hardware/tool rationalization and disposition plan; refining data classification, security policies, and data governance; and piloting application cloud migration based on move groups, as well as the setup of the landing zone on Azure.
Trexin laid the groundwork and outlined the foundational elements and architecture to enable a successful cloud migration, reduce the legacy data footprint, and adopt a support model to manage the future cloud environment. Dubbed a “Minimal Viable Cloud (MVC)” plan, this defined a set of essential production‐ready, cloud‐based services, capabilities, and processes that provided development, deployment, and management solutions to migrate and manage applications in a cloudbased environment. This effort answered key questions such as “What cloud provider is best for us?”, “What applications cannot move to the cloud?”, and “What are our cloud security requirements and implications?”