Your existing core and ledger stay in place. VInsure works alongside them — with read-only access to legacy data where needed — and each area moves across when you decide, not before.
Start with the area that hurts most — often motor sales or claims. Each module is a complete, working part of the platform on day one, and every module you add shares the same data.
Pricing tables, plans, approval limits, document checks, routing rules and reminders are settings your teams control. Going live is mostly configuration and training, not a development project.
No. VInsure goes live module by module. Many insurers start with motor sales or claims and add areas from there. Each module is complete on its own and shares one database with the rest.
Yes. VInsure can post entries alongside your existing books while finance compares the two, and the switch-over happens lane by lane, on your schedule.
Customers, policies and open claims are imported and checked before go-live, and legacy data stays readable where it needs to be. Your team signs off on the result.
Your underwriters and managers. Plans, rate matrices, approval limits, document checks and deadlines are settings with a full change history — no developer in the loop.
No. Partners log into browser portals under your brand and see only their own work. Training them is part of the rollout.
Yes. Methaq Takaful runs its daily business on it: sales, claims, garages, finance, brokers, an app in both stores and the public website. Read the case study →
English and Arabic run throughout the platform, right to left where it matters: the app, the website, documents and partner portals.
Configuration covers most requests. When it doesn't, VIONEX builds it as part of the platform rather than a bolt-on. See services →