Replacing Access and Excel
Access databases and Excel files with macros become apps with a real data foundation - supporting multiple users, mobile use, and access controls.
Migration · modernization
Replace legacy systems. Step by step.
Many companies work with solutions that were once good: Access databases, InfoPath forms, Nintex or SharePoint workflows, and Excel files with macros. I move them step by step to Power Automate, Power Apps, and SharePoint Online - with clean data migration and agreed cutover dates.
- Step by step with agreed cutover dates
- Data migration checked and cleaned
- Tenant migration moving apps and flows
01Use cases
What I replace and modernize
Replacing InfoPath forms
Support for InfoPath 2013 ended in July 2026, and InfoPath forms no longer run in SharePoint Online. I rebuild forms in Power Apps, with validation rules, attachments, and approval via a flow.
Nintex and SharePoint workflows
I rebuild SharePoint workflows retired by Microsoft and Nintex workflows in Power Automate - the opportunity to simplify processes at the same time.
On-premises SharePoint to SharePoint Online
Move sites, lists, libraries, and the applications on them to the cloud in an orderly way, with a new structure instead of a 1:1 copy.
Tenant migration
Transfer flows, apps, and SharePoint forms to a new Microsoft 365 tenant - centrally or with guides for self-migration.
Overhauling existing solutions
Slow apps, error-prone flows, missing documentation: I analyze, clean up, and put the solution on a solid foundation.
02Approach
From the first conversation to a solution in production.
Consulting and implementation from a single source: whoever writes the concept also builds it - with no friction between consultant and developer.
-
Initial consultation
Free and without obligation via Microsoft Teams: What is the challenge, what is the goal, and which licenses do you already have? Afterward, you will know whether and how the Power Platform fits your needs.
-
Process analysis
Together with the people who run the process every day: How does it work today, and where do manual handoffs between systems or media, delays, and errors occur?
-
Solution concept
Data model, screens, flows, permissions, and licensing - in writing, easy to understand, and with a clear effort estimate.
-
Implementation in stages
Short iterations, each with a working interim result. You see early on what is being built and can adjust course.
-
Rollout and handover
Acceptance, deployment to production, documentation, and handover to your team - so the solution does not depend on me.
-
Further development
If you wish, I will continue to support the solution afterward: enhancements, new requirements, and updates from Microsoft.
03Toolbox
Technologies in this area
- Power Automate
- Power Apps
- SharePoint Online
- Dataverse
- Microsoft Access
- InfoPath
- Nintex
- SharePoint Migration Tool
- Package export and import
- Excel
04Real-world projects
Projects in this area. No names, real substance.
As a rule, I do not name clients - their industry, size, and project requirements say enough.
Energy and cable industry12/2025 - 09/2026
SharePoint migration, Power Apps, and Azure in the cable industry
For an international group in the energy and cable industry, I supported the migration of SharePoint and Power Platform applications. I developed the security and Azure architecture concept for a QHSE application and rebuilt three Power Apps for hazardous substance management, replacing an on-premises SharePoint solution with Nintex workflows.
more than 10,000 employees
Power Automate (cloud flows)Power Apps (canvas apps)SharePoint OnlineOn-premises SharePoint (source system)SharePoint REST API
Read case study
Automotive industry08/2024 - 06/2025
Power Platform learning paths, handbook, and migration guides, automotive
For an international automotive group, I created English-language learning paths, Q&A formats, and a 122-page handbook on developing Power Apps, working through a partner. This was later followed by guides that enabled employees to migrate their apps, flows, and SharePoint forms to a new Microsoft 365 tenant themselves.
more than 190,000 employees
Power Automate (cloud flows, desktop flows)Power Apps (canvas app)SharePoint Online (lists, forms with Power Apps)TeamsPower BI
Read case study
05Questions and answers
Frequently asked questions
Do we have to switch everything at once?
No. I recommend a step-by-step replacement: first the applications with the greatest risk or benefit, then the rest. Old and new run in parallel until the new solution has been accepted.
What happens to our data from Access or Excel?
It is cleaned up, transferred to the new data foundation according to agreed criteria, and checked. A trial run that compares counts and totals helps detect transfer errors before the switchover.
Can Nintex workflows be transferred automatically?
Only partially. There are tools for the analysis, but I rebuild the logic in Power Automate. This is usually the opportunity to simplify processes and add error handling.
Your process. My solution.
Tell me where things get stuck today - in a free, no-obligation initial consultation via Microsoft Teams, we will clarify what the Power Platform can do for your process and what a sensible first step looks like.