Replacing a 25-year-old Access database without losing a case
A US insurance-claims investigation firm ran every case from an Access database about 25 years old. We moved it to Power Platform without breaking the case number its evidence folders hang from.
- ClientAtlantic Security International Investigations
- SystemCase management
- Delivered2026, Access retired
- StackPower Apps · Dataverse
Five minutes to open became about 35 seconds
About 40,000 records moved across with their relationships intact and none lost.
5 min → 35 s
Time to open the system~40,000
Records migrated0
Records lost206
Bad dates listed for the client
Project snapshot
- Client
- Atlantic Security International Investigations, Inc.
- Domain
- Security, Investigations & Public Safety
- Engagement
- Modernization
- Platform
- Model-driven Power Apps on Dataverse
- Users
- Six
- Applications
- Two: insurance and general business
What we built, and the link we could not break
Atlantic Security International Investigations, Inc. is a US firm that investigates insurance claims: surveillance, activity checks, online and background research. Aditi IT Software Solutions rebuilt the firm’s case system, completing an Access database to Power Apps migration for a database that had run for about 25 years. Two Power Platform applications replaced it, one for the insurance business and one for its separate general business.
The Access database held the client and claimant records and generated the five-digit case number that every file in the firm hangs from. Six people used it. The evidence itself, meaning reports, video, photographs and email, lived on network storage in a case folder named after that number and the claimant.
ConstraintThe network storage could not move. Its folder convention, I<number> Lastname, Firstname under a year, was the firm’s working model, and the case number was the only link between the database and the files. Existing numbers had to survive and the sequence had to continue.
Billing lived in a separate system that the owner wanted kept apart, so the new database had to stay out of it. The cutover had to fit a four-hour window, because staff added records at all hours and the old system could not run alongside the new one during migration.
The old data was the third constraint. It had no enforced relationships, so a migration applying strict rules on day one would have rejected real cases or invented values to satisfy them.
DecisionAditi recommended Power Platform over a custom web application. Both were proposed to the client. Power Platform was quicker to build, cheaper and simpler to maintain, and it ran inside the Microsoft 365 tenant the firm already had.
The decision that mattered was in the data model. In Access, a client carried a company. When an adjuster changed employers, updating the person rewrote every old file. Atlantic needed the opposite: history that could not be rewritten. Aditi made the case the hub. Clients and claimants connect only through a case, and the company sits on that relationship, so the same adjuster can appear against several companies across several files without touching any of them. Each record also carries an internal identifier alongside the visible case number, so two records can be merged without breaking anything that points at them.
The alternative, one company per client as Access had it, was the simpler build. It was rejected after the first demo showed how often the real workflow broke it.
BuildModel-driven Power Apps on Dataverse, deployed into the client’s Microsoft 365 tenant, with Power Automate flows for migration lookups and for writing case and investigator PDFs to the user’s OneDrive. Two separate applications share one design: the insurance system, linked to the insurance drive, and the general-business system, with its own tables and interface. Aditi advised against merging them because every query would then need filtering by business.
What Access could not do was added: an audit history recording who changed which field, the old and new values and when, visible only to a manager role; four roles, none of which lets a client user delete; duplicate detection at entry on name, company and date of birth; global and keyword search across case notes; Excel export on every grid; and open, closed and on-hold case reports. About ten legacy tables, with no new entries since dates between 2003 and 2013, were not given screens. Their data was kept.
Data was migrated in two passes: import first, validate second. Aditi held the source files only for the migration, keeps no copy, and its own user was disabled after deployment. Records with impossible dates of birth or loss, 206 of them, were carried over with those fields cleared and listed for Atlantic to correct.
What it is built on
- Microsoft Power Apps
- Microsoft Dataverse
- Power Automate
- Microsoft 365
- OneDrive
What changed
Atlantic retired Access after the February 2026 migration. The application now opens in about 35 seconds, where Access took up to five minutes in the morning. About 40,000 records moved across with their relationships intact and none lost.
Several people can work in the system at once, which Access handled badly. Case numbers are issued on save, so two people creating cases at the same moment each receive their own. Global search covers clients, companies and employees, and case notes can be searched by keyword. Every edit is traceable to a user and a time. After the April 2026 release the client has reported no further issues and asked for no enhancements.
Named where the client has given written permission, described by sector where they have not.
