Yazh (Yaal), our Integration Gateway, takes each renewing policy from your legacy system and delivers it with both its current and renewal terms, so policies move one renewal at a time instead of in a single cutover.
The Problem
Converting at Renewal Leaves Policies Split Across Two Systems
Many carriers convert at renewal, so legacy data reaches the new system in daily runs. Each run depends on legacy data matching the format the new system expects.
Legacy Data Does Not Match the Renewal Format
Legacy coverage, rating and terms need field mapping before loading, even though renewal dates stay the same.
The Legacy System Stays Open
Endorsements stay in the legacy system until policies run off, which can delay retirement by up to a year. Carriers pay to maintain both systems while servicing policies across them.
Every Upgrade Reopens the Build
Each connector depends on your policy system's and the carrier's APIs, so upgrades require rework and retesting across every transaction-specific connector.
The Solution
How does InsOps Help?
How Yazh (Yaal) Converts Policies at Renewal
Bring Your Legacy Data
Send policy data in the format your legacy system already produces.
LiLa-Suggested Mapping
LiLa maps each source field to your policy system and lists the fields it could not match.
Review Every Mapping
A team member can edit, add, or remove mapped fields before the mapping goes live.
Active Policies Only
Conversion covers in-force policies, one renewal at a time.
Current and Renewal Term Together
Your policy system receives both terms in one delivery.
Logged and Monitored
Every request is authenticated, validated, and recorded, with audit entries on the dashboard.
FAQ
What does converting at renewal mean?
Which policies convert?
Is this the same as a migration?
Who reviews the mapping?