AppSheet to Power Apps Migration
Budget: $25 – $50 AUD
I have a fully-functional business app built in AppSheet that relies on Google Sheets as its single source of truth. The next step is to rebuild the exact experience in Microsoft Power Apps and then keep it healthy as our processes evolve.
Core functions that must move across without regression are the underlying database management logic, solid user authentication, and the real-time analytics our team depends on every day. Three permission levels need to be preserved—Admin, Standard User, and Guest—each seeing only the screens, data and actions that belong to them.
During the migration you can start from the existing AppSheet spec, UX flows, and Google Sheet data model. I am open to shifting the back-end to Dataverse, SQL or another Microsoft-friendly store if that simplifies security and performance, but phase one can reference the current Google Sheets data through Power Apps connectors if that is faster.
Deliverables
• A like-for-like Power Apps canvas or model-driven app that matches the current AppSheet behaviour
• Role-based access configured for Admin, Standard User and Guest accounts
• Embedded or connected real-time analytics (Power BI is fine, or native Power Apps charts)
• A short hand-off document that covers data sources, environment variables and how to push future changes
• Ongoing support and incremental improvements after the initial release, arranged through milestone extensions or a support retainer
Acceptance criteria: every workflow in the original app executes successfully inside Power Apps, data writes back to the chosen data store without error, and each role only accesses its authorised features.
If this sounds like the sort of project you can own from first build to long-term maintenance, I’m ready to share the existing AppSheet definition and walk through the current user stories.
Core functions that must move across without regression are the underlying database management logic, solid user authentication, and the real-time analytics our team depends on every day. Three permission levels need to be preserved—Admin, Standard User, and Guest—each seeing only the screens, data and actions that belong to them.
During the migration you can start from the existing AppSheet spec, UX flows, and Google Sheet data model. I am open to shifting the back-end to Dataverse, SQL or another Microsoft-friendly store if that simplifies security and performance, but phase one can reference the current Google Sheets data through Power Apps connectors if that is faster.
Deliverables
• A like-for-like Power Apps canvas or model-driven app that matches the current AppSheet behaviour
• Role-based access configured for Admin, Standard User and Guest accounts
• Embedded or connected real-time analytics (Power BI is fine, or native Power Apps charts)
• A short hand-off document that covers data sources, environment variables and how to push future changes
• Ongoing support and incremental improvements after the initial release, arranged through milestone extensions or a support retainer
Acceptance criteria: every workflow in the original app executes successfully inside Power Apps, data writes back to the chosen data store without error, and each role only accesses its authorised features.
If this sounds like the sort of project you can own from first build to long-term maintenance, I’m ready to share the existing AppSheet definition and walk through the current user stories.