From Manual Emails to Automated Workflows: Connecting Dynamics 365 Sales to the Shop Floor

Summary

1. A custom steel windows and doors manufacturer had complex shop floor stages tracked entirely by hand, with no system connecting the sales office to production.
2. CloudFronts developed a custom Order Fulfillment module within Dynamics 365 Sales and implemented trigger-based Power Automate flows to automate over 60 internal and external email communications across every stage of production.
3. Microsoft has deprecated classic workflows in Dynamics 365, making migration to modern Power Automate cloud flows the required path forward. These were fully migrated, restoring consistent and professional client communication.
4. The sales commitment now automatically extends into every production stage — from Preprocessing Order through Engineering & Calculations all the way to Scheduling Arrangements — without any manual follow-up from staff.

Table of Contents

• 1. Customer Scenario
• 2. The Real Problem
• 3. Solution Overview
• 4. Key Components of the Solution
• 5. How It Works: Technical Implementation
• 6. End-to-End Walkthrough
• 7. Architecture and Design Decisions
• 8. Business Impact
• 9. FAQs
• 10. Conclusion

A manufacturer of custom steel windows and doors uses Dynamics 365 Sales to manage its customer relationships and order pipeline. The business builds bespoke, high-specification products where every order is unique, every unit requires individual engineering, and every delivery carries a direct reputational commitment to the client.

The production journey for each order moves through a structured Business Process Flow (BPF) with the following discrete stages:

1. Preprocessing Order: Initial order intake, validation, and readiness checks before the order enters the formal workflow
2. Order Details: Full capture of specifications, dimensions, materials, and client requirements against the order record
3. Assign Project Manager: A project manager is designated and formally takes ownership of the order in Dynamics 365
4. Project Manager: The assigned PM reviews the order, aligns with the client if required, and confirms the production brief
5. Engineering & Calculations: Structural and thermal specifications are drawn up; shop drawings are prepared and sent for customer approval
6. Production Review: Internal sign-off before the order enters active fabrication
7. In Production: Active manufacturing — covering CNC machining, welding, painting, finishing, and quality control as sub-activities within this stage
8. Quality Control: Final inspection against specification before dispatch clearance is issued
9. Scheduling Arrangements: Protective packaging, carrier coordination, dispatch scheduling, and delivery confirmation

Each stage involves different teams, different external parties, and different communication requirements. All of this was being managed entirely by hand.

Figure 1: Business Process Flow (BPF) stages for a custom steel windows and doors order in Dynamics 365

The organisation’s CRM and manufacturing operations existed in two separate worlds. A deal won in the sales office would trigger a handoff to the shop floor, but from that point the CRM had no visibility into what happened next. Production moved forward, but the system of record did not.

This disconnect created three compounding problems:

1. Manual Tracking Across Nine BPF Stages

With nine distinct BPF stages per order — from Preprocessing Order through to Scheduling Arrangements — and dozens of active orders at any given time, tracking which orders were where and who needed to be notified was a full-time administrative burden. Teams relied on printouts, spreadsheets, and internal messaging. The risk of an order falling through the cracks was constant.

2. Over 60 Email Templates Managed by Hand

Customer-facing and internal communications spanned more than 60 distinct email templates covering stage transition notifications, drawing approvals, production confirmations, and dispatch alerts. Each one required a staff member to remember when to send it, select the right template, fill in the correct order details, and copy the right recipients. A missed email left a customer without an update. A wrong email required a correction and an apology.

3. Classic Workflows Deprecated by Microsoft

Some automation had been attempted through Dynamics 365’s classic workflow engine. However, Microsoft has deprecated classic workflows — they are no longer receiving investment or feature updates, and organisations are required to migrate to Power Automate cloud flows as the supported replacement. Beyond the deprecation, the legacy classic workflows had become fragile over time: triggering at the wrong time, failing silently, or firing duplicate emails when conditions were partially met. The team had lost confidence in the automation and was increasingly bypassing it, falling back to manual processes.

The system was not broken in any single dramatic way. It was failing in dozens of small ways, every day, and the cumulative cost showed up in staff time, customer experience, and operational risk.

Figure 2: The three core pain points driving the need for change

CloudFronts addressed each pain point with a targeted, interconnected solution built on the existing Dynamics 365 platform. No third-party systems, no new infrastructure, and no disruption to the tools the team already knew.

Custom Order Fulfillment Module in Dynamics 365  +  Trigger-Based Power Automate Cloud Flows  +  Full Migration from Deprecated Classic Workflows

For the Production Team:

1. Every order’s BPF stage — from Preprocessing Order to Scheduling Arrangements — is tracked directly within Dynamics 365, visible to sales, operations, and management in real time
2. Stage transitions automatically trigger the correct notification with no manual action required
3. Engineering & Calculations, Production Review, Quality Control, and Scheduling Arrangements are managed as structured fields rather than informal notes or emails

For the Sales Team:

1. The CRM record now follows the order all the way to delivery. The sale does not end at contract signature
2. Customer-facing communications are consistent, professionally formatted, and sent automatically
3. No more chasing production teams for status updates to relay to clients

For the Organisation:

1. A single source of truth for every order, from first contact through final dispatch
2. Reliable, Microsoft-supported Power Automate automation that can be trusted rather than worked around
3. A professional communication experience that reflects the quality of the product being delivered

The solution was delivered across three integrated components, each solving a distinct part of the problem.

1. Custom Order Fulfillment Module in Dynamics 365 Sales

A custom module was developed within Dynamics 365 Sales to extend the platform’s native capabilities into manufacturing territory. Rather than treating the CRM as a sales-only tool, the module makes it the authoritative record for the entire order lifecycle — across all nine BPF stages.

1. BPF Stage Tracking: Each order carries a clearly defined BPF stage field covering Preprocessing Order, Order Details, Assign Project Manager, Project Manager, Engineering & Calculations, Production Review, In Production, Quality Control, and Scheduling Arrangements, updated by the relevant team as work progresses
2. Engineering & Drawing Management: Shop drawings are tracked as structured records with version, approval status, and customer sign-off captured in Dataverse fields rather than email attachments
3. Production Review Records: Internal sign-offs and review notes are logged against the order, creating an auditable trail
4. Scheduling Arrangements Details: Packaging type, dispatch date, and carrier information are captured in the same record, eliminating the need for separate logistics emails

By extending Dynamics 365 rather than replacing it, the solution preserves all existing sales data, reporting, and user workflows while adding the production visibility the team was missing.

2. Trigger-Based Power Automate Cloud Flows

A suite of Power Automate cloud flows was built to monitor BPF stage changes on every order record and automatically fire the appropriate communication to the right recipient, with the right content, the moment a transition occurs.

1. Stage-specific triggers: Each BPF stage transition has its own flow trigger. When an order moves to “In Production,” the production-entry flow fires. When it moves to “Quality Control,” the QC flow fires, and so on across all nine stages
2. Dual audience notifications: Flows distinguish between customer-facing notifications (professionally formatted and client-ready) and internal team notifications (concise and action-oriented)
3. Dynamic content population: Order number, customer name, product specifications, expected timelines, and contact details are pulled directly from the Dataverse record with no manual data entry required in the email body
4. Conditional logic: Flows include branching logic to handle exceptions such as rush orders, partial completions, or stage reversals without breaking the standard notification sequence

Over 60 email templates, previously managed by hand, now fire automatically and accurately at exactly the right moment.

3. Migration from Deprecated Classic Workflows to Modern Cloud Flows

Microsoft has officially deprecated classic workflows in Dynamics 365. They are no longer receiving investment, feature updates, or long-term support. Migration to Power Automate cloud flows is the required path forward. The existing classic workflows were not simply replicated — each was reviewed, its logic was clarified, and it was rebuilt as a stateless, event-driven cloud flow.

1. Eliminated duplicate-fire errors: Classic workflows could fire multiple times under certain trigger conditions. Cloud flows with proper concurrency settings do not
2. Transparent failure handling: Failed cloud flows are logged and visible in Power Automate’s run history. Classic workflows failed silently
3. Maintainability: Cloud flows can be updated, cloned, and versioned without touching the CRM solution layer. Changes to email content or recipient lists take minutes rather than requiring a developer engagement
4. Future-proofed: Built on Microsoft’s actively supported automation platform with access to 1,000+ connectors and ongoing feature investment

1. The BPF Stage Field as the Trigger Source

The custom module introduces a BPF Stage option set field on the Order record in Dataverse, aligned to the nine-stage Business Process Flow. This single field is the heartbeat of the entire automation layer. Every cloud flow is triggered by a change to this field, meaning the moment a team member advances the BPF stage, the corresponding notifications fire automatically with no secondary action required.

2. Power Automate Flow Architecture

Each stage transition has a dedicated flow rather than one monolithic flow with complex branching. This design was deliberate for three reasons:

1. Individual flows are easier to test, debug, and maintain in isolation
2. A failure in one notification does not cascade to others
3. New stages can be added by creating a new flow with no modification to existing automation

Each flow follows a consistent pattern:

Trigger: BPF Stage field updated → Condition: New value = [Stage Name] → Get full order record → Compose email body with dynamic fields → Send to customer + Send to internal team

3. Email Template Management via Dataverse

Rather than hardcoding email content inside the flows, email templates are stored as Dataverse records. Each flow looks up the relevant template by stage and recipient type, merges in the dynamic order fields, and dispatches the result. This means:

1. Non-technical staff can update email copy without opening Power Automate
2. Templates can be tested independently of the flow logic
3. Multilingual variants can be supported by adding additional template records

4. Classic Workflow Migration Strategy

Because Microsoft has deprecated classic workflows, migration was not optional — it was a necessary modernisation. Each legacy classic workflow was documented before decommissioning. The migration followed a clear sequence: map the existing logic, rebuild as a cloud flow with corrected trigger conditions, run both in parallel for a defined period, then decommission the classic workflow once the cloud flow was confirmed stable. No automation was removed until its replacement had been validated in production.

Figure 3: End-to-end automation architecture from BPF stage update to notification dispatch

Here is what a production coordinator and a customer both experience once the system is live:

1. Preprocessing Order: The Dynamics 365 opportunity is closed and an Order record is created. The BPF advances to Preprocessing Order. An automated internal notification confirms order receipt and triggers the intake checklist for the operations team.
2. Order Details: The coordinator populates all specifications, dimensions, materials, and delivery requirements in the Order record. The BPF advances to Order Details. An automated confirmation email is sent to the customer summarising what has been captured.
3. Assign Project Manager: A project manager is selected and formally assigned to the order in Dynamics 365. The BPF advances and the designated PM receives an automated notification with full order context.
4. Project Manager: The assigned PM reviews the brief and aligns with the client as needed. The BPF stage is confirmed, triggering an internal notification that the order is ready for engineering. If client clarification is required, a templated email fires automatically.
5. Engineering & Calculations: The engineering team updates the Drawing Status field once shop drawings are complete. A Power Automate flow sends a professional email to the customer with drawings attached and instructions for approval. Upon customer approval, the BPF advances to Production Review.
6. Production Review: The internal team conducts sign-off. An automated notification confirms clearance for fabrication. The BPF advances to In Production.
7. In Production: Active manufacturing is underway. A customer-facing notification fires: “Your order is now in production. Expected completion: [date].” Internal sub-stage updates keep the PM informed throughout.
8. Quality Control: The BPF advances to Quality Control. The QC team receives an automated scheduling notification. Once inspection is passed, the customer receives confirmation that their order has cleared final inspection and is being prepared for dispatch.
9. Scheduling Arrangements: The BPF advances to its final stage. A dispatch email fires automatically to the customer with carrier details, tracking reference, and estimated delivery window — all pulled from the order record. The sales team is notified to follow up post-delivery.

BPF Stage Transition Notifications at a Glance

Components Involved

1. Dynamics 365 Sales: The core platform, extended with a custom Order Fulfillment module and nine-stage BPF tracking
2. Dataverse: Stores all order, BPF stage, drawing, and template records in a structured, queryable format
3. Power Automate Cloud Flows: Event-driven automation triggered by Dataverse BPF stage changes, replacing all deprecated classic workflows
4. Email Template Records: Dataverse-stored templates with dynamic field tokens, managed outside the flow layer for easy content updates

Classic Workflows vs. Modern Cloud Flows

1. Reduced manual intervention: Over 60 email templates previously triggered by hand are now fired automatically by Power Automate at every BPF stage transition, with zero manual action required from staff
2. Seamless sales-to-production handoff: The CRM record that previously closed at contract signature now tracks the full order lifecycle across all nine BPF stages, keeping sales and production aligned on a single record
3. Reliable, supported automation: Deprecated classic workflows prone to duplicate and missed fires have been replaced with Power Automate cloud flows — Microsoft’s supported platform — that carry a clean run history, error logging, and consistent execution behaviour
4. Professional client communications: Ad-hoc, manually assembled emails have been replaced with consistent, dynamically populated, professionally formatted notifications that reflect the quality of the product being delivered
5. Operational visibility: BPF stage progress that was previously tracked on paper and in spreadsheets is now visible in Dynamics 365 in real time, accessible to sales, operations, and management
6. Maintainability: Changes to email content or workflow logic that previously required developer involvement can now be made by trained staff directly in Dataverse and Power Automate

Figure 4: Before and after comparison across key operational dimensions

1. Why extend Dynamics 365 Sales rather than implement a dedicated MES (Manufacturing Execution System)?
A dedicated MES would have introduced a second system of record, a new integration layer, and significant training overhead. Because the existing Dynamics 365 environment already held the customer relationship, the order details, and the commercial data, extending it with a custom module and a nine-stage BPF gave the team a single, connected record without the cost or complexity of a separate platform.

2. How are the Power Automate flows triggered? Does someone need to initiate them?
No. The flows are triggered automatically by a change to the BPF Stage field on the Dataverse Order record. When a team member advances the BPF stage, the flow fires immediately. No secondary action, no manual email send, and no checklist to follow.

3. What happens if a flow fails? Does the customer miss their notification?
Power Automate cloud flows log every run in the portal, including failures, with full error detail. Failed flows can be resubmitted manually with one click once the issue is resolved. The team is also alerted to failures via a monitoring flow. This is a significant improvement over classic workflows, which failed silently with no recovery mechanism.

4. Can the email templates be updated without a developer?
Yes. Because templates are stored as Dataverse records rather than hardcoded inside the flows, authorised staff can update email copy, subject lines, and recipients directly in Dynamics 365 with no flow editing required. Changes take effect immediately on the next trigger.

5. Why was migration from classic workflows necessary?
Microsoft has deprecated classic workflows in Dynamics 365. They are no longer receiving feature investment or long-term support. Migration to Power Automate cloud flows is the required path forward for any organisation still running classic workflow automation. Beyond the deprecation, cloud flows offer superior reliability, full run history, maintainability, and access to over 1,000 connectors — making the migration a benefit in its own right, not just a compliance requirement.

6. Can this approach be applied to other manufacturing or production businesses?
Yes. Any business where a CRM manages customer relationships but production happens offline is a strong candidate. The pattern of extending Dynamics 365 with a custom BPF, triggering Power Automate flows on stage changes, and storing communication templates in Dataverse is reusable across construction, furniture, signage, industrial equipment, and any other bespoke manufacturing environment.

7. How was the migration from classic workflows handled?
The migration ran in parallel rather than as a cutover. Each classic workflow was rebuilt as a cloud flow, validated in production alongside the original, and then decommissioned once confirmed stable. This approach eliminated migration risk and gave the team confidence in each new flow before the old one was removed.

The gap between the sales office and the manufacturing floor is one of the most common and most underestimated operational risks in custom manufacturing. When those two worlds operate in isolation, the consequences show up in every direction: staff carry a heavy administrative burden, customers receive inconsistent communication, and the promises made at the point of sale drift away from the realities of production.

By extending Dynamics 365 Sales with a custom Order Fulfillment module, implementing a nine-stage Business Process Flow from Preprocessing Order to Scheduling Arrangements, deploying trigger-based Power Automate cloud flows across every BPF stage, and migrating away from Microsoft’s deprecated classic workflows, CloudFronts gave this manufacturer something genuinely valuable: a business that operates as one connected system from first contact to final delivery.

The automation does not replace the skilled people on the shop floor. It removes the friction that was slowing them down and gives their customers the visibility and communication experience they expect.

When the CRM and the shop floor share the same record — and when that record advances through a structured Business Process Flow rather than living in a spreadsheet — the sales commitment and the production reality stay aligned. That alignment is not just an operational improvement. It is the foundation of a reputation for reliability.

Sometimes the right answer is not to fight a platform limitation or rebuild from scratch — it is to extend what already works, and build something better around it.

Is your manufacturing operation still running on manual handoffs and deprecated automation?

Explore how CloudFronts can connect your sales platform to your shop floor and turn your production process into a competitive advantage.