Contractor Management App Rebuilt in Microsoft Power Apps
Global insurance and financial services group
In short
How do you replace a third-party form tool with Power Apps during a tenant migration?
When the client acquired a US risk services business, one business-critical application could not simply move across. It ran on a third-party form tool that the client did not want to carry into its main Microsoft tenant, and the team that served contractors every day depended on it. We rebuilt it in Power Apps, with every function intact, inside the migration deadline.
Results in numbers
- items in the largest list
- 2,000+
At a glance
- Third-party form tool replaced
- All existing functions recreated
- Delivered on the agreed date
The client
The client is a global insurance and financial services firm that grows through acquisition. Its newly acquired risk services business in the US ran its contractor insurance operations on Microsoft 365 and SharePoint, including programmes for trucking associations.
What it was costing them
- Vendor dependency: a core application sat on a third-party tool that had no place in the target tenant.
- Migration risk: the rest of the tenant move could not close while this application was unresolved.
- Operational exposure: daily work on contractors, drivers, equipment, coverages and receivables all ran through it.
- Performance limits: several SharePoint lists held more than 2,000 items, which simple forms handle poorly.
What we built
We recreated the old contractor application as a custom Power Apps SharePoint form, matching the old application so users had nothing new to learn.
- No retraining for users: styling and theming matched the application they already knew.
- One view of each contractor: a shared header component keeps contractor data visible on every tab.
- Faster screens on large data: up to 5 lists of over 2,000 items load into memory at start-up as dictionaries.
- Complete records in one place: dedicated tabs for details, emails, phones, attachments, letters and drivers.
- Direct document handling: files upload to SharePoint through the Microsoft Graph API.
- Reporting kept intact: accounting receivables, notes and prospect reports stay reachable from the app.
- Sensitive data protected: bank account and routing numbers are hidden from the standard view.
- Fast fixes during testing: issues raised by business users were resolved in short cycles up to go-live.
Results
- Project delivered on the agreed date, confirmed by the project manager.
- All existing functions of the old application recreated, with small improvements to forms and tables.
- Third-party form dependency removed from the migration.
The risk most teams miss
A like-for-like rebuild on SharePoint is fast, but delegation limits, permissions at list level and connections owned by one person are what break it in month three. We kept large lists in memory to protect performance, and the next step is to move the data to Dataverse before volumes grow further.
What we would add today
Improvements we would add on top of what is live.
- Move the data from SharePoint lists to Dataverse, with row-level security by role and office.
- Replace hidden fields with field-level security and masking for bank details.
- Convert the form to a model-driven app with audit history on every contractor record.
- Add a Copilot Studio agent so staff can look up a contractor, coverage or balance in plain language.
- Deploy through Power Platform pipelines with service-account connections.
Technology
Power Apps (custom SharePoint forms), SharePoint Online, Microsoft Graph API, Power Automate, Microsoft 365.
Tell us which third-party tool your team cannot leave behind, and we will tell you what it takes to rebuild it in Power Platform.
Products and capabilities
- Power Apps
- SharePoint
- Microsoft Graph
- Power Automate
- custom SharePoint form
- tenant migration
- app rebuild
The service behind this work
Power Platform developmentThe service behind this work
Power Platform governanceMore on this industry
Banking and finance
Related use cases
Operations and field workID and Passport Data Extraction AI Model
Typing customer identity data by hand slows onboarding at a bank and puts errors into fields that compliance depends on. We built an AI model that reads ID cards and passports and returns structured fields for staff to check. Accuracy is measured on documents the model has never seen.
Power Automate Desktop Response to a Municipal RPA Market Consultation
A municipality that wants to buy robotic process automation must choose between tools and decide how to tender them, with little time. The municipality ran a request for information to learn what the market offers. We answered it for Power Automate Desktop.
Document Management with Approvals for Emailed and Posted PDFs
When closing documents arrive as PDFs by email and by post, each one has to be found, checked, approved, completed, sent and chased by hand. A missed reply or an unsigned page stalls a closing. We built a SharePoint and Power Automate process that files each document, routes it to a paralegal, produces the outgoing PDF and keeps reminding until the reply arrives.
- 15 min
- saved per document
- 20 hrs
- saved per 30 properties
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.