Yazh (Yaal), our Integration Gateway, sends legacy claims into ClaimCenter in batches. You move history in steps instead of one cutover.
The Problem
Moving Legacy Claims in One Piece Is Risky and Slow
Insurers have to decide how to get years of claims out of the legacy system and into ClaimCenter. Each option Guidewire describes carries its own cost.
A Single Cutover Puts Everything at Risk
Guidewire warns that Big Bang migrations carry higher risks, as poor legacy data can require extra cleansing cycles, increasing delays and costs.
Phased Migration Runs Two Systems at Once
Guidewire’s phased approach migrates segments gradually, with each using ClaimCenter after migration while the rest remain on the legacy system.
Mapping Repeats by Hand
Teams rely on spreadsheets, scripts and consultants to map fields and business rules by hand. That work repeats every time the data changes shape.
The Solution
How does InsOps Help?
Yazh (Yaal) Moves Legacy Claims Into ClaimCenter a Batch at a Time
Send claims in batches
Your system sends a set of legacy claims together, instead of one at a time or all at once.
Mapped once, confirmed by a person
LiLa suggests the mapping the first time a payload arrives. A person confirms it, and later payload changes are edited in the portal.
Value translation
Yazh (Yaal) translates your legacy codes into the values ClaimCenter expects.
Alerts when ClaimCenter adds a required field
Your team gets an alert, and a default value is sent in the meantime so a batch does not break.
Test calls and secured requests
Test the route before any batch goes. Every request passes a firewall, authentication, authorization and validation.
Every batch on one dashboard
Your team sees how many requests were sent, the status of each, and any errors.
FAQ