Yazh (Yaal), our Integration Gateway, creates a single policy in your new policy system from your legacy system or archive when a claim or request needs it, so old history stays out until it is required.
The Problem
Old Policy Terms Are Missing When Someone Needs Them
Most carriers load only current terms at go-live. Older terms stay behind, and the need for them appears one request at a time.
A Claim Arrives on a Term That Is Not There
Claims on old terms require manual retrieval and recreation, which delays claim creation and keeps the legacy system running.
Loading All History Slows the New System
Loading every historical term requires heavy data cleansing and may hurt performance, even though most records are rarely accessed.
Every Upgrade Reopens the Build
Each connector depends on your policy system's and the carrier's APIs, so every upgrade triggers rework and retesting.
The Solution
How does InsOps Help?
How Yazh (Yaal) Brings Old Policies Over on Demand
Bring the Term From Legacy or Archive
Send the term in the format your legacy system or archive already uses.
LiLa-Suggested Mapping
LiLa maps each source field to your policy system. You set the mapping once per line of business and reuse it.
Review Every Mapping
A team member can edit, add, or remove mapped fields before the mapping goes live.
Policy First, Then the Claim
Your policy system receives the policy, and the claim is then created against it.
Self-Service
Your team sends a policy whenever it is needed, with no InsOps step in each transaction.
Logged and Monitored
Every request is authenticated, validated, and recorded, with audit entries on the dashboard.
FAQ
What is on-demand policy migration?
How is this different from converting at renewal or a full migration?
Can we reuse the mapping?
Who reviews the mapping?