Contact Initial consultation

Knowledge transfer · automotive industry

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.

Discuss a similar projectAll case studies
  • 08/2024 - 06/2025
  • more than 190,000 employees
  • Knowledge transfer
Industry
Automotive industry
Company size
more than 190,000 employees
Scope
international
Period
08/2024 - 06/2025
My role
Design and creation of learning content and guides, consulting
Type
Knowledge transfer

175hrs.

design and creation over nine months (rounded)

4

learning modules with three levels each and a total of 122 learning items

122pages

handbook on developing an app with Power Apps

40

topics prepared for Q&A sessions

3

migration guides for flows, canvas apps, and SharePoint forms

01The situation

Where the project started.

In the IT unit of one of the group's divisions, an internal learning initiative was to make it easier for employees to get started with the Power Platform. What was needed were structured learning paths that bring together existing learning sources, as well as practical content on Power Automate and Power Apps, all in English. One focus was Power Automate for desktop within the existing licenses without premium.

In 2025, a move to a new Microsoft 365 tenant was planned. Employees were to be able to transfer their personal flows, canvas apps, and SharePoint forms customized with Power Apps themselves. This required clear step-by-step instructions, which were to be available by early June.

Goals

  • Structured learning paths for Power Platform fundamentals, Power Automate, Power Apps in the cloud, and Power Automate for desktop.
  • A practical handbook for the path from an idea to a finished app built with Power Apps.
  • Guides that let users migrate their own flows, apps, and SharePoint forms to a new tenant.

02Solution

What I designed and built.

Learning paths in four modules and three levels

I designed four learning modules, each with the levels Basic, Advanced, and Expert. Each learning item describes the content and key terms and refers to verified learning sources, mainly Microsoft Learn and selected videos. In several rounds with the contact person, I agreed on the modules, added material, and streamlined them.

  • Microsoft Power Platform Fundamentals with 21 learning items
  • Microsoft Power Apps with 35 learning items
  • Microsoft Power Automate cloud flows with 35 learning items
  • Microsoft Power Automate for desktop with 31 learning items
  • First versions in German and English, final versions in English with more than 200 references to learning sources

Topics for Q&A sessions

For short Q&A sessions of 15 to 30 minutes, I described 20 topics each on Power Automate and Power Apps in the cloud, from the interface to error handling and permissions.

  • Power Apps: variables and collections, galleries, Filter, LookUp, and Search, Patch, ForAll, and With, containers, components, loading screen, and roles and access
  • Power Automate cloud flows: flow types, variables, JSON, HTML emails, conditions and Switch, loops, approvals, trigger conditions, and error handling

Handbook: build an app with Power Apps from scratch

The English-language handbook guides readers through all phases of app development in eleven chapters, supplemented by a checklist and a troubleshooting guide. It comprises 122 pages with around 37,000 words and includes a sample project in the form of a learning app.

  • Planning with goals, target group, process diagrams, choice of devices, data sources, mockups, accessibility, and data field documentation
  • Internationalization with dynamic language selection, translations, fallback, right-to-left languages, and date and currency formats
  • Minimum viable product with prioritization, tests, and feedback loops
  • Implementation with UX, UI, navigation, Power Automate, Monitor, error handling, security, and versioning
  • Advanced topics on delegation, OnStart, Power Fx, lazy loading, components, and test automation
  • Deployment, metrics, ROI, ten do's and ten don'ts for beginners

Guides for migrating to a new tenant yourself

For the tenant move, I wrote three guides, each as a short version with screenshots and, for flows and apps, also as a one-page summary. For flows, there is also a 37-page long version that covers prerequisites, governance, and data loss prevention (DLP) policies in detail.

  • Identification of your own flows and apps with a provided identification app
  • Export as a package (ZIP) in the source tenant and import in the target tenant, including how to deal with errors
  • Re-create connections, check and enable triggers, and follow the required sequence for linked flows
  • SharePoint forms with Power Apps: rebuild or adjusted package import
  • Typical errors with solutions, plus contact and support channels
  • Excel migration templates for flows, apps, and SharePoint forms with sample entries

Hands-on testing of the migration paths

I recreated the described export and import procedures with test objects, including two canvas apps with Office 365 connectors, a SharePoint list form customized with Power Apps, and a scheduled flow. I documented the individual steps with screenshots.

03Tricky parts

Challenges and how I solved them.

Migration by users instead of centralized migration

Personal flows and apps cannot simply be moved centrally to another tenant. The guides enable the owners to identify their objects themselves, export them as a package, import them into the target tenant, and reconfigure connections, triggers, and data source links. For rare or complex cases, they refer to support.

Learning paths from existing sources

Instead of writing custom courses from scratch, the learning paths bring together verified sources in a sensible order and progression. This keeps maintenance effort low and makes updates easy.

04Approach

Step by step to the result.

  1. 1

    Start

    Framework agreement and individual project contract in September 2024, kickoff in October 2024.

  2. 2

    Learning paths

    Design, research, and alignment of the four learning modules in October and November 2024.

  3. 3

    Q&A and handbook

    Q&A topics in November 2024, handbook from November 2024 to February 2025.

  4. 4

    Regular meetings

    Weekly or otherwise regular coordination with the contact person at the group.

  5. 5

    Migration guides

    Effort estimate in May 2025, alignment and creation of the guides by mid-June 2025.

05Result

What works differently today.

  • Four learning modules with 122 learning items, Q&A topics, and a 122-page handbook in English.
  • Three migration guides with short and long versions, one-page summaries, and Excel templates, completed in June 2025.
  • Around 175 hours of effort in total, billed based on records of services performed.

Technologies

  • Microsoft Power Automate (cloud flows, desktop flows)
  • Microsoft Power Apps (canvas app)
  • Microsoft SharePoint Online (lists, forms with Power Apps)
  • Microsoft Teams
  • Microsoft Power BI
  • Power Platform environments
  • Microsoft Excel

Demonstrated skills

  • Designing English-language learning paths for the Power Platform
  • Technical writing of handbooks and guides
  • Cross-tenant migration of flows, canvas apps, and SharePoint forms
  • Governance and data loss prevention (DLP) in the context of the Power Platform

06Questions and answers

Frequently asked questions

How do you migrate Power Automate flows to another tenant?
Personal flows are exported as a package (ZIP) in the source tenant and created as new flows in the target tenant via package import. Connections have to be reassigned in the process; then triggers and data sources are checked and the flow is turned on.
Can SharePoint forms customized with Power Apps be migrated?
Yes, but with limitations. Either the form is rebuilt in the target tenant, or the exported package is adjusted and imported again. In both cases, the list, columns, and connections must exist in the target.
What belongs in a good Power Platform learning program?
A clear progression from fundamentals to expert knowledge, references to maintained sources such as Microsoft Learn, and complementary formats such as short Q&A sessions. A practical example developed throughout the program helps you apply what you have learned to your own apps.

07More case studies

More projects in detail.

Specialist retailer of fireplaces and stoves with delivery and installationsince 02/2022 Order processing for a stove retailer with Power Apps and SharePoint For almost five years, I developed the central order processing system for a fireplace and stove retailer with several companies and locations, based on SharePoint, Power Automate, and Power Apps, and I still support it today. Quotes with digital signatures, invoices and payment reminders via sevDesk, Planner tasks, customer surveys with Forms, Power BI, and a mobile installation report on tablets all work together. The solution gave rise to the industry platform FLAMOX365. more than 50 employees SharePoint Online (lists and libraries)Power Automate (cloud flows)Power Automate approvalsPower Apps (canvas apps)Forms (customer surveys) Read case study Industry06/2026 - 09/2026 Order approval in manufacturing with Power Automate and SharePoint For a manufacturing company, I implemented a multi-stage approval process for customer orders with Power Automate and SharePoint. Engineering, installation, order management, purchasing, and a second purchasing review handle approvals in sequence; rejections are routed back to the appropriate step with a required explanation. Nine flows, eight SharePoint lists, escalation, and an audit trail form the core system. Part of a group of companies with more than 12,000 employees Power Automate (cloud flows)Power Automate ApprovalsSharePoint Online (lists)Office 365 OutlookPower Platform solutions (managed and unmanaged) Read case study 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

A similar project? Let's talk.

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.

Book a free initial consultation Send an inquiry +49 160 125 01 75