Guidewire Cloud in Canada: what the migration really changes for your teams

A move to Guidewire Cloud is usually presented as an upgrade. In practice, it redistributes responsibility between the insurer, the integrator and the vendor. Teams that settle this at the framing stage avoid last-minute trade-offs at the end of the programme.

What changes in the code

Your extensions do not disappear: their status changes. Every customisation has to be justified against the data model and the capability offered by the target version.

• Inventory the business rules written in Gosu and separate the ones still required
• Identify the PCF screens replaced by standard screens
• List the extension points in use and check their compatibility with the target version

What changes in integrations

Exchanges with surrounding systems (billing, reinsurance, brokers, data warehouse) become the main source of complexity. An interface that worked in batch mode may need rework once the release cadence speeds up.

• Document every interface: source, target, frequency, data exchanged
• Check authentication mechanisms and rate limits
• Plan regression testing on critical flows before each update

What changes in data

Data conversion is not a copying exercise. Policy, claim and payment histories must stay consistent with the business rules of the target version, or the gaps get paid for in manual corrections for months.

The four questions to settle before starting

1. Who owns customisation governance: your team, the integrator, or a joint committee?
2. What update cadence can your operations absorb?
3. Which flows are critical enough that a few hours of downtime is unacceptable?
4. How is knowledge documented so your teams stay self-sufficient after the programme?

These are leadership questions, not development questions. They take a few weeks of framing, and they decide whether the programme ends in knowledge transfer or in extended dependency.