Yazh (Yaal), our Integration Gateway, moves policies from your legacy system into your new policy system in batches you choose, so you can migrate a region or line of business without waiting for the full book.
The Problem
Moving the Whole Book at Once Is Rarely an Option
Carriers rarely want to migrate every policy on the same day. They need to move policies in batches while the rest of the book stays in place.
An All-at-Once Load Needs Everything Ready
A big-bang migration needs all historical and in-force data cleansed up front. That adds risk, delay, and cost, and it holds back regional rollouts until everything is ready.
One at a Time Does Not Scale
Migrating region by region means mapping, validating, and logging each policy individually. That overloads the small team that maintains the legacy system.
Unmoved Policies Keep the Old System Open
The legacy and new systems must run side by side until every batch has moved. Each delayed batch adds to the cost.
The Solution
How does InsOps Help?
How Yazh (Yaal) Moves Policies Into Your New Policy System
Bring the Term From Legacy or Archive
Send policy terms in the format your legacy system or archive already uses.
LiLa-Suggested Mapping
LiLa maps each source field to your new policy system. You set the mapping once per line of business and reuse it for every policy.
Review Every Mapping
A team member can edit, add, or remove mapped fields before the mapping goes live.
You Build the Batch
Group policies by region, line of business, or size, and send each batch when you choose.
Self-Service
Your team sends each batch without InsOps involved in every send.
Logged and Monitored
Every request is authenticated, validated, and recorded, with audit entries on the dashboard.
FAQ
What is batch policy migration?
How is this different from the other ways to bring policies in?
How big is a batch?
Can we reuse the mapping across batches?
Who reviews the mapping?
Where does it run?