{
  "id": 15719963,
  "title": "On-Prem to Cloud Migration: Running the Systems That Can't Move Yet",
  "url": "https://urgent.news/2026/10/20/on-prem-to-cloud-migration-running-the-systems-that-cant-move-yet",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-20T08:28:53.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/geminate_solutions_9b6035/on-prem-to-cloud-migration-running-the-systems-that-cant-move-yet-20nf"
  },
  "original_language": "en",
  "account": "Most on-prem to cloud migration plans assume a single clean cut over, but the reality is hybrid setups that persist for months or years. Deciding how to connect the systems that remain on-prem with those in the cloud, managing user authentication, and anticipating failures between the two environments are critical to a successful migration. Factors like network connectivity, shared identity, latency, and ownership of issues across the boundary significantly impact the stability of the hybrid period.\n\nSeveral systems stay behind due to contractual obligations, regulatory requirements, or support agreements tied to specific hardware or locations. Others are left behind because their inner workings are unclear, such as applications with hard-coded IP addresses or shared databases accessed by multiple tools. Bridging these lingering systems safely often requires untangling them, which takes longer than anticipated.\n\nThe hybrid setup does not indicate a failed plan; rather, it is a common outcome of migration. Mistakes in this stage often lead to prolonged, confusing incidents rather than an immediate outage. Mistakes may include slow, confusing incidents caused by oversized VPN tunnels, multiple logins for different domains, and unresolved gaps in system ownership. These issues can degrade performance, confuse users, and obstruct critical operations between the on-prem and cloud systems.\n\nWhen migrating, the approach differs based on the volume of traffic crossing the boundary and its impact. For customer-facing operations or applications with frequent calls, a dedicated link such as AWS Direct Connect or Azure ExpressRoute is preferable, despite the longer setup time. For lighter traffic like admin tools or nightly batch jobs, standard VPN tunnels are sufficient. Measuring cross-boundary traffic over a couple of weeks can help determine the appropriate connection type.\n\nUsing a single identity system is recommended to provide consistent user access to both old and new systems. Active Directory on-prem can serve as the master list of users and sync with cloud directories like Microsoft Entra ID or Okta to ensure seamless user login and role management. Similarly, managing system-to-system logins requires similar care to ensure consistent access controls and credential management.\n\nAddressing latency between the old and new systems is crucial. Treat every cross-boundary call as slower and less reliable than internal calls. Strategies include keeping frequently communicating systems together, batching and caching data transfers, and employing message queues for asynchronous operations. These strategies help reduce the impact of latency and improve overall system performance during the transition period.\n\nProper planning and early identification of critical components are essential. Addressing overlapping IP address ranges and DNS configurations upfront can prevent future complications. Planning for one identity system and consistent management of system-to-system logins are key to maintaining a seamless user experience. With careful consideration of network, identity, latency, and ownership, the transition from on-prem to cloud can be managed efficiently, minimizing disruptions and ensuring a smooth hybrid operation.",
  "summary": "If your on-prem to cloud migration plan assumes one clean cutover, expect that plan to change. Most migrations run hybrid for months or years. The real work is deciding how the systems left behind connect to the ones that moved, how people sign in to both, and who answers when something breaks in between. You probably know the situation. The customer portal and the new APIs already run in AWS or…",
  "key_points": [
    "Hybrid on-prem to cloud setups persist for months or years.",
    "Hybrid period requires careful connection of systems, user authentication, and failure management.",
    "Proper planning addresses IP ranges, DNS, and identity systems for seamless transition."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}