Guidewire InsuranceSuite self-managed to Guidewire Cloud
Cohash moves self-managed Guidewire InsuranceSuite (PolicyCenter, BillingCenter and ClaimCenter) to Guidewire Cloud Platform. We inventory Gosu code, plugins, UI changes and integrations, decide what goes back to base product, rebuild integrations for the cloud model and rehearse data conversion with premium, billing and reserve reconciliation. Then we set a plan for taking Guidewire's named cloud releases so the next upgrade stays small.
- 01Customization and integration inventory
- 02Target design and line-of-business order
- 03Build on the cloud delivery model
- 04Conversion rehearsals
- 05Cut-over by line of business
- 06Release adoption plan
The story
Told without the client's name or anything that could identify them.
A property and casualty carrier's core systems team ran self-managed PolicyCenter, BillingCenter and ClaimCenter several releases behind, and every upgrade estimate came back longer than the last. Guidewire Cloud had been approved, but nobody had sorted the Gosu code, plugins and point-to-point integrations that made those upgrades so slow. We started with an inventory that gave each customization and integration a keep, replace or drop decision. Then we set up the cloud build pipeline and rehearsed conversion until premium, billing balances and open reserves reconciled. The carrier moved one line of business at a time and now plans its Guidewire Cloud releases on a calendar.
why it was urgentGuidewire Cloud Platform gets several named releases a year. Olos shipped in December 2025 and Palisades in April 2026. Then Qusar, in August 2026, made the Agentic Framework generally available, with developer assistants for Gosu and integrations and for Jutro. On a self-managed install you only get that by running your own upgrade.
- openSeveral InsuranceSuite releases behind, and every upgrade estimate comes back longer than a year.
- recurringThe team runs more custom Gosu rating, rules and plugins than configuration anyone can explain.
- blockedIntegrations reach PolicyCenter through point-to-point code, and nobody has a list of them.
- openGuidewire Cloud is approved, but your team has never worked in its build and release model.
- recurringUnderwriters keep asking for the AI features in recent Guidewire Cloud releases. IT has no way to offer them.
The estate, before and after
Before: self-managed InsuranceSuite with custom code and point-to-point feeds
Portals and partners called PolicyCenter directly, and the rating logic was custom Gosu baked into the app. Finance got billing and claims data through extracts and database links that never left the data center.
After: InsuranceSuite on Guidewire Cloud with a managed release path
Channels and partners reach Guidewire Cloud through APIs and events now, not direct code. We moved the rating that fit into the rating engine, and each release is promoted by a cloud build pipeline with a regression pack.
How we run it, phase by phase.
6 phases take you from Guidewire InsuranceSuite (self-managed) to Guidewire Cloud Platform. Each one ends with something you can check before the next starts. As you scroll, the blocks show the estate moving across.
- phase 01
Customization and integration inventory
Gosu classes, rules, PCF changes, custom entities, plugins and integration endpoints all get exported. We tag each with the line of business that uses it and decide whether it goes back to base product, gets rebuilt for cloud, or retires.
- phase 02
Target design and line-of-business order
Agree the base-product gaps you will accept, the integration pattern for cloud (APIs, events, the integration framework) and which product line moves first.
- phase 03
Build on the cloud delivery model
Set up the cloud build, test and promotion pipeline, rebuild the kept customizations against the current release, and move rating that sits in Gosu into the rating engine where it fits.
- phase 04
Conversion rehearsals
We convert policy, billing and claims data again and again in rehearsal. Each run reconciles written premium, billing balances and open reserves against the legacy system, line of business by line of business.
- phase 05
Cut-over by line of business
We move one line at a time, each with a rollback point and, where finance or regulators need it, a parallel period. Then that line's self-managed servers and database are retired.
- phase 06
Release adoption plan
Agree which Guidewire Cloud releases you will take and when, with a regression pack sized so each release fits a normal change window.
What the client got
What changed for the client once the work was done. Described, not scored: we don't publish client figures.
- result 01
Every customization has a recorded decision
Every Gosu class, rule, PCF change, custom entity and plugin has a keep, replace or drop decision and the line of business that uses it. Nothing went to the cloud by default.
- result 02
Integrations run on cloud-supported patterns
We swapped the database links, file drops and direct data-center calls for APIs, events or the integration framework, and gave every feed in the catalog a named owner.
- result 03
Finance signed off conversion by line of business
Written premium, billing balances and open reserves reconciled against the legacy system in rehearsal before any line cut over, with agreed sign-off owners.
- result 04
Self-managed servers retired line by line
Lines of business moved one at a time, each with a rollback point. As each went live on Guidewire Cloud, we switched off its self-managed servers and database.
- result 05
Cloud releases fit a normal change window
We built a regression pack for the product model, rating and the main integrations, and a calendar for adopting releases. So each named Guidewire Cloud release arrives as a planned change. Nobody has to stand up a project for it.
Risks we plan for
-
Rebuilding every customization
Moving all Gosu code as-is recreates the upgrade problem in the cloud. Each item needs a keep, replace or drop decision before build starts.
-
Conversion numbers finance won't accept
If premium, billing or reserves don't reconcile, cut-over stalls. Reconciliation rules and sign-off owners are agreed before the first rehearsal.
-
Integrations built for the old network
Integrations on a self-managed install tend to use database links, file drops or direct calls inside the data center. Each needs a cloud-supported pattern, and some partners will need time to change their side.
-
Falling behind on cloud releases
Skip releases for too long and the big upgrade comes back. A regression pack and a release calendar belong in the migration plan from the start.
Where AI helps, and where it needs guardrails
With Qusar, Guidewire made the Agentic Framework generally available and added developer assistants for Gosu, integrations and Jutro. Agentic FNOL went into restricted access. We don't pilot any of it until the base configuration is clean. Any AI agent or MCP server reading policy or claim data has its own service identity, begins with read-only scopes, and logs what it does for claims and compliance to review.
forward deployed engineers →What you're left with
We write these for your setup, and they're working documents. Your team should be able to keep things running from them long after we've gone.
- inventory01
Customization inventory with a keep, replace or drop decision per item
yours to keep - inventory02
Integration catalog with the cloud pattern and owner for each feed
yours to keep - inventory03
Conversion mapping and reconciliation reports per line of business
yours to keep - tests04
Regression pack for product model, rating and key integrations
yours to keep - runbook05
Cut-over runbook with a rollback point per line of business
yours to keep - plan06
Release adoption calendar for future Guidewire Cloud releases
yours to keep
Platforms and services on this move
Learn the background
Terms from this page in plain English. If you want the why, the field note behind it is right there.
- 01Rules
- The JavaScript snippets Auth0 used to run at login. Someone would write one to add a role to the token or block a sign-in, and each one ran after the last.in context →
- 02Base
- The appliance's own operating software. Every Remote Support or PRA release needs a minimum Base, so you often update Base first.in context →
- 03self-managed
- GitLab's name for an instance you install and run yourself, as opposed to GitLab.com or GitLab Dedicated, which GitLab runs for you.in context →
- 04Rollback
- Going back to the version you ran before an upgrade, using the backups and the untouched old install you kept for that.in context →
Certified engineers, wherever you need them.
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
Onsite
Engineers at your sites in the US
Nearshore
Overlapping hours with US teams
Offshore
Overnight progress on your backlog
All time zones
Coverage handed over across time zones
01How long does a move to Guidewire Cloud take?
It depends on how many products and lines of business you run, how much Gosu code and how many integrations you carry, and how much history you convert. We give an estimate after the customization and integration inventory, not before.
02Do we have to move all three InsuranceSuite products at once?
No. Plenty of carriers move by product or by line of business. The order depends on the integration dependencies between PolicyCenter, BillingCenter and ClaimCenter, and the inventory shows those.
03What happens to our custom rating?
Rating that lives in Gosu is reviewed routine by routine. Where the rating engine can express it, we rebuild it there and compare results against real production quotes. The rest stays as custom code with an owner.
04Can you staff Guidewire developers for our own team?
We do. That includes Guidewire configuration and integration developers as well as upgrade leads, onsite in the US or nearshore or offshore. Terms can be contract, contract-to-hire or permanent.
Often on the same roadmap
On-premises Active Directory to cloud-first Microsoft Entra ID
We shrink on-premises Active Directory one application at a time, moving groups, users and app authentication to Microsoft Entra ID as each app is ready.
read the case studyAD FS federation to Entra ID authentication
Converting federated domains from AD FS to Entra ID cloud authentication, moving relying parties app by app and retiring the AD FS farm.
read the case study
Apache Airflow 2 to Airflow 3
Upgrading self-managed Apache Airflow 2, now past end of life, to Airflow 3, and fixing removed features, auth and scheduling changes before DAGs move.
read the case study879cb6fe - 01Book a 30-minute working sessionsenior engineer
- 02Talk to an engineer about your setupreply within 24 hours
- 03See how similar projects wentcase studies
Planning this move?
A 30-minute working session with a senior engineer. No slides.
- The platform and the version you're on
- Where you need to get to, and by when
- What's custom: rules, plugins, integrations
- Any audit finding or deadline driving it