Yazh (Yaal), our Integration Gateway, sends policies from your legacy system to PolicyCenter in batches you size, so you can move a region or a line of business without waiting for the whole book to be ready.
The Problem
Moving the Whole Book at Once Is Rarely an Option
Carriers rarely want to move every policy on the same day. They need a way to move policies in batches while the rest of the book stays where it is.
An All-at-Once Load Needs Everything Ready
Big-Bang migration requires cleansing all historical and in-force data upfront, increasing risks, delays, and costs while preventing regional rollouts until the entire book is ready.
One at a Time Does Not Scale
Regional migration requires individually mapping, validating, and logging each policy, burdening the small team already maintaining the legacy system.
Unmoved Policies Keep the Old System Open
The legacy and new systems must run concurrently until all batches migrate and legacy connections are removed, increasing costs with each delayed batch.
The Solution
How does InsOps Help?
How Yazh (Yaal) Moves Submissions Into PolicyCenter
Bring the Term From Legacy or Archive
Send the policy term in the format your legacy system or archive already holds it.
LiLa-Suggested Mapping
LiLa maps each source field to PolicyCenter. You set the mapping once for a line of business and reuse it for every policy you send.
Review Every Mapping
A person edits, adds or removes mapped fields before the mapping goes live.
You Build the Batch
Build a batch by region, line of business or size, and send the next one when you are ready.
Self-Service
Your team sends each batch, with no InsOps step inside each send.
Logged and Monitored
Every request is authenticated, validated and recorded, with audit entries on the dashboard.
FAQ