Yazh (Yaal), our Integration Gateway, takes each renewing policy from your legacy system and delivers it to PolicyCenter with its current term and renewal term, so policies move one renewal at a time instead of in one cutover.
The Problem
Converting at Renewal Leaves Policies Split Across Two Systems
Many carriers convert policies as they renew, so legacy data reaches PolicyCenter in daily runs. Each run depends on legacy data matching the format PolicyCenter expects.
Legacy Data Doesn’t Match the Renewal Format
Guidewire exports daily renewals in predefined XML for PolicyCenter, requiring legacy coverage, rating and terms mapping while preserving renewal dates.
The Legacy System Stays Open
Endorsements remain in legacy systems until policies run off, delaying retirement by up to a year. Carriers pay to maintain both systems while teams service policies across them.
Every Upgrade Reopens the Build
Each connector depends on PolicyCenter and carrier APIs. Upgrades require rework and retesting, multiplied across every transaction-specific connector.
The Solution
How does InsOps Help?
How Yazh (Yaal) Moves Submissions Into PolicyCenter
Bring Your Legacy Data
Send policy data in the format your legacy system already produces.
LiLa-Suggested Mapping
LiLa maps each source field to PolicyCenter and lists the fields it could not match.
Review Every Mapping
A person edits, adds or removes mapped fields before the mapping goes live.
Active Policies Only
Conversion covers policies in force, one renewal at a time.
Current and Renewal Term Together
PolicyCenter receives the in-force term and the renewal term in one delivery.
Logged and Monitored
Every request is authenticated, validated and recorded, with audit entries on the dashboard.
FAQ