Migrating enterprise systems from Guidewire on-premises to Guidewire Cloud Platform (GWCP) is a significant transformation. For CIOs, engineers, and other stakeholders, understanding the platform’s technical capabilities and new features helps save time, reduce risk, and ease adoption. Based on real migration projects and case studies, here are six practical lessons to de-risk the move and support your transition, with clear explanations for everyone involved.
1. Start with a Reality Check for SaaS on Guidewire Cloud and Out-of-the-Box (OOTB) Conformance Guardrails
Begin your migration by locking in the target state that aligns with Guidewire out-of-the-box (OOTB) capabilities on Guidewire Cloud. Explicitly identify what needs redesigning because the cloud deployment behaves differently from on-premises installations. For example, InsuranceSuite batch processes that previously ran on-premises and wrote files to an SFTP path should now be configured to use S3 Buckets on Guidewire Cloud.
Early inception workshops help map existing functionality and customisation hotspots, converting them into a cloud-fit backlog on Guidewire Cloud.For a prominent UK insurer, our approach involved proactively resolving the issues highlighted in the CUE report within the on-premises codebase itself—such as the use of JDBC, implementation of multithreading, and explicit commits in runWithNewBundle—prior to commencing the Guidewire Cloud migration. By addressing these concerns ahead of the migration, we enabled the client to mitigate risks and shorten the overall migration timeline.
Treat the Guidewire Cloud Standards as core design inputs, not late-stage surprises—such as moving from client reflection to post on-change in PCF files when necessary. For product modelling, if APD is unused or only on-premises APD is used, consider migrating to the APD app for Guidewire Cloud. This will decrease digital and configuration workload, as the APD app automatically generates PCF and Jutro screens.
2. Use the "Technical Upgrade Handover" as Your Baseline for Validation and Refinement
After a technical upgrade, assume that handover artifacts are incomplete, since as part of the technical upgrade Guidewire only provides a standalone application without integrations. Plan for a dedicated validation and remediation sprint. Handover documents often list known issues, but these may miss additional UI/UX challenges like screen alignment or dropdown inconsistencies. Implement a post-upgrade triage backlog to validate UI parity, layout shifts, and behavioural differences before starting feature work. Define remediation as fixed, regression-tested, and documented in a deviation log.
In a Guidewire Cloud migration project executed by TCS, the team encountered additional issues that were not captured within the handover documentation. As a result, the project experienced an extended timeline as well as several defects during the stabilisation phase. Allocating a dedicated sprint to validate these differences can help mitigate the issue.
3. Engineer the Data Migration Path First—Database Snapshot and Change Data Capture (CDC) Can Dominate the Schedule
Database movement—snapshot uploads, CDC, and cutover rehearsals—should be on your critical path from day one. In previous migrations, snapshot uploads of large databases took weeks, and CDC processes ran for hours. This is a technical detail that directly impacts your programme plan and business-as-usual (BAU) delivery. Carry out several dry runs using measurable runbooks grounded in the Surepath methodology, along with fallback plans, to enhance migration resilience.
For a leading UK insurer, the on-premises database exceeded 20 terabytes in size. To ensure an efficient migration, we collaborated closely with Guidewire, conducting multiple dry runs to optimise the database migration timeline and minimise the overall production roll-out duration. Through these iterative dry runs, we meticulously refined the extraction steps for the insurer and the migration procedures from the Guidewire side. This approach enabled us to pinpoint and address the most time-consuming aspects of the data migration process. As a result, we successfully reduced the total migration time from 45 hours to just 17 hours, significantly accelerating the production roll-out.
4. Re-enable and Re-validate Integrations Deliberately
Don’t assume integrations are ready post-upgrade. Message queues and cross-centre integrations are often disabled during the technical upgrade; you must re-enable and validate their behaviour. Institute “integration readiness gates” for connectivity, authentication patterns, schema compatibility, performance, and error handling. Explicitly check items not upgraded automatically, such as Edge APIs and Admin Data Loader.
During the TCS-led migration project, we encountered an integration challenge with the Payment Gateway previously utilised in the on-premises environment. The legacy solution relied on a callback servlet, which is not supported on Guidewire Cloud. To address this, we re-engineered the entire payment process using the Guidewire documentation on implementing the payment gateway silent post servlet, thereby ensuring a seamless payment integration pattern in the new environment.
Similarly, for the Admin Data Loader, the original process allowed business users to upload Excel files to SharePoint, after which an Admin Data Loader batch process would onboard users. However, in the Guidewire Cloud landscape, direct file uploads from Guidewire to the S3 inbound folder were not feasible. Consequently, we redefined the business process, instructing the BAU team to leverage the S3 browser for uploading files directly to the S3 inbound folder, ensuring continuity and compliance with the new operational model.
5. Automation-First Delivery with Disciplined Engineering
Use automation and repeatable accelerators to reduce the cloud remediation backlog and reach stability faster. Leverage tools such as Guidewire SurePath and TCS migration workbenches to automate fixes, enforce code standards, and track progress across categories like deprecated APIs, UI parity, and integration authentication.
Additionally, consider Guidewire Autopilot tools for business process automation and the Guidewire Agentic Framework to develop AI-driven agents that integrate with core applications, improving operational efficiency and enabling innovation.
6. Keep Business-as-Usual (BAU) Alive via Frequent Production Code Merges
Plan for frequent production code merges to avoid divergence between BAU and migration streams. Maintain a merge calendar and conflict-resolution playbook, clearly define what can change during freeze windows, and address stakeholder concerns about minimising freeze and maintaining ongoing business operations. Merging each on-prem production release into the Guidewire Cloud development codebase minimized merge conflicts and ensured all on-prem features were available in the cloud environment.
For a leading UK insurer's migration project, TCS moved Guidewire InsuranceSuite onto Guidewire Cloud and consistently merged each BAU release from on-premises into the cloud codebase. During BAU merges, previously identified issues like hidden package references from the CUE report occasionally reappeared due to new references added in the on-premises code. These are flagged in the Automated Cloud Assurance report in Bitbucket, making it essential to review every build for new issues. Local checks using the Cloud Assurance Plugin in InsuranceSuite allowed early issue detection and resolution before Bitbucket builds, helping maintain code quality and smooth integration between environments.
Conclusion
Migrating to Guidewire Cloud requires careful planning, teamwork, and disciplined engineering. Key strategies include using repeated dry runs to optimize database migration, manually validating integrations not upgraded automatically, prioritizing automation tools like SurePath and Autopilot, and regularly merging production code to maintain operations and address issues early. Clear communication of freeze periods, merge schedules, and conflict resolution is essential. Applying these practices helps insurers minimize risks, ensure smooth transitions, and leverage the benefits of the Guidewire Cloud for long-term growth.