El Hajj Consulting Book a call →
02 · Method

The ERP project lifecycle

Every D365 F&O implementation follows the same arc, even when it goes by different names. Ten phases, from requirement gathering to hypercare. Select one from the left to read its article.

Phase 1 of 10

Requirement gathering

Discovering what the business actually needs, from declared requirements down to the unspoken ones.

Source. The framework below is based on the Business Process Workshops released by Microsoft as part of the Dynamics 365 implementation guidance. Microsoft publishes a "scenario board" workshop and a set of deep-dive discovery workshops for each of the 14 end-to-end business processes. The content here distills those workshops down to what is most useful for a consultant running discovery, the structure, the stakeholders, the questions that actually move the conversation, and the traps to avoid. Process-specific scope and questions are summarized per workshop further down.

Requirement gathering is not an interview. It is a structured process of mapping the customer's intended end-to-end flow, ranking the scenarios in scope, identifying the gaps against standard D365 F&O, and producing a written record everyone agrees to. Microsoft's Business Process Workshops give you a repeatable scaffolding for that, use them, but don't be a slave to them.

MethodHow a Microsoft Business Process Workshop runs

Every Microsoft BPW follows the same shape. Knowing the shape lets you walk into any of the 14 process workshops with the same playbook, only the process-specific questions change.

Workshop Hierarchy

flowchart TD A[Scenario Board Workshop\nBreadth pass: 90-120 mins] --> B{Deep-Dive Workshops\nDepth pass per L2 Area} B --> C[L2: Develop procurement strategy] B --> D[L2: Manage supplier relationships] B --> E[L2: Procure goods and services] C --> F((Requirements Log & Gap List)) D --> F E --> F style A fill:#e0f2fe,stroke:#0284c7,stroke-width:2px,color:#0369a1 style B fill:#f1f5f9,stroke:#64748b,stroke-width:2px,color:#334155 style C fill:#f8fafc,stroke:#94a3b8,color:#475569 style D fill:#f8fafc,stroke:#94a3b8,color:#475569 style E fill:#f8fafc,stroke:#94a3b8,color:#475569 style F fill:#dcfce7,stroke:#16a34a,stroke-width:2px,color:#166534

Two layers of workshop per process

  • Scenario board discovery workshop, the breadth pass. One workshop per process. The output is an agreed scope: which scenarios are in, which are out, which are gaps. Roughly 90–120 minutes.
  • Deep-dive discovery workshops, the depth pass. One per L2 process area inside the process (e.g. 75.40 Procure Goods and Services inside Source to pay). Held after the scenario board, with a narrower stakeholder group.

Standard agenda (every workshop)

  1. Introduction and objectives (10–15 min)
  2. Overview of the process, walk the scenario board left-to-right (15–20 min)
  3. Detailed discussion on key scenarios (45 min, the longest block)
  4. Interactive Q&A (20–30 min)
  5. Wrap-up, decisions, action items, next steps (10 min)

The three objectives, every time

  1. Understand the customer's process, their as-is flow, their pain points, where it bends.
  2. Identify key scenarios & requirements, what's most critical for them and what is a deal-breaker.
  3. Document agreed business scope, leave the room with a written, signed-off list of in-scope scenarios.

The scenario board

Scenario Board Example (Source to Pay)

L2 Areas are columns. Scenarios are marked as In Scope, Out of Scope, or Gap.

flowchart TD subgraph S2P [Complete Source to Pay Scenario Board] subgraph L2A [75.10 Develop strategy] A1[75.10.010 Policies]:::inScope A2[75.10.020 Catalogs]:::inScope A3[75.10.030 Spend analysis]:::gap end subgraph L2B [75.30 Manage supplier relations] B1[75.30.010 Supplier onboarding]:::inScope B2[75.30.020 Supplier performance]:::outScope B3[75.30.030 Supplier collaboration]:::inScope end subgraph L2C [75.35 Source & contract] C1[75.35.010 Manage RFQs]:::inScope C2[75.35.020 Purchase agreements]:::inScope C3[75.35.030 Contract compliance]:::gap end subgraph L2D [75.40 Procure goods/services] D1[75.40.010 Purchase requisitions]:::inScope D2[75.40.020 Purchase orders]:::inScope D3[75.40.030 Receiving]:::inScope D4[75.40.040 Quality inspection]:::outScope end subgraph L2E [75.50 Manage accounts payable] E1[75.50.010 Invoice processing]:::inScope E2[75.50.020 Invoice matching]:::inScope E3[75.50.030 Payment runs]:::inScope E4[75.50.040 Expense reports]:::gap end end classDef inScope fill:#dcfce7,stroke:#16a34a,color:#166534 classDef outScope fill:#fee2e2,stroke:#dc2626,color:#991b1b,text-decoration:line-through classDef gap fill:#fef9c3,stroke:#eab308,color:#854d0e

The scenario board is a one-page flowchart that runs across the top of the room. Each L2 area is a column; under each column are the scenarios and policy decisions to discuss. Run it left to right. As scenarios are discussed: highlight what's in scope, strike through what's out, add any missing ones as gaps. The marked-up board is the artifact you walk out with, photograph it before anyone leaves.

VisualizationAnatomy of a Microsoft Process Flow

During the deep-dive discovery workshops, the focus shifts from the high-level scenario board to the detailed process flows (L3 level). Microsoft provides Visio flows and Excel data for every process, mapping the specific tasks, roles, and decisions.

Anatomy of a Process Flow

This is an exact replication of the Microsoft Business Process Flow for a complete end-to-end Procure-to-Pay flow, demonstrating the standard shapes (Events, Tasks, Decisions).

flowchart LR Start((Start)) --> Req[Create Requisition] Req --> App1{Manager Approval?} App1 -- No --> Stop1((End)) App1 -- Yes --> PO[Generate PO] PO --> Send[Send to Vendor] Send --> Wait((Wait for Goods)) Wait --> Rec[Receive Goods] Rec --> Inv[Receive Invoice] Inv --> Match{3-Way Match?} Match -- No --> Res[Resolve Discrepancy] Res --> Match Match -- Yes --> Post[Post Invoice] Post --> Pay[Generate Payment] Pay --> End((End)) classDef event fill:#f8fafc,stroke:#94a3b8,stroke-width:2px,color:#334155; classDef task fill:#eff6ff,stroke:#3b82f6,stroke-width:1px,color:#1e3a8a; classDef decision fill:#fefce8,stroke:#eab308,stroke-width:1px,color:#854d0e; class Start,Stop1,Wait,End event; class Req,PO,Send,Rec,Inv,Res,Post,Pay task; class App1,Match decision;
PeopleStakeholders to bring

Workshops with the wrong room produce the wrong answers. The right room has process owners (people who do the work daily), decision-makers (people who can say yes), and at least one technical voice. Avoid the room being only managers, they tell you the policy, not the reality.

The standing group, bring to every workshop

  • IT department, implementation and integration ownership.
  • Finance department, every process touches the GL eventually.
  • Operations, alignment with day-to-day execution.
  • Legal & compliance, regulatory constraints (data privacy, anti-corruption, tax, labor, contract).
  • Executive leadership, alignment with strategic goals; needed at minimum for kickoff and wrap-up of the scenario board workshop.

Process-specific additions

  • Source to pay: Procurement managers, supplier relationship managers, contract managers, AP managers.
  • Order to cash: Sales managers, AR managers, credit & collections managers.
  • Hire to retire: HR managers, the HR department itself.
  • Record to report: CFO, controllers, accounting managers, treasury, budget & planning analysts, AP/AR leads, audit & compliance officers.
  • Acquire to dispose: Asset managers, maintenance dept, procurement, HR (for users operating the assets).
  • Plan to produce: Production planners, plant managers, quality, shop-floor supervisors.
  • Inventory to deliver: Warehouse managers, transportation/logistics, quality.
  • Project to profit: Project managers, PMO, project accountants, resource managers.
  • Prospect to quote: Sales leadership, sales operations, marketing.
  • Concept to market: Marketing, product management, R&D.
  • Design to retire: Product management, engineering, supply chain.
  • Forecast to plan: S&OP leads, demand planners, FP&A.
  • Service to deliver: Service operations, dispatch, field technicians.
  • Case to resolution: Customer service ops, knowledge managers, contact center supervisors.
QuestionsCross-cutting questions every workshop asks

Every BPW opens and closes with the same set of cross-cutting questions. Memorize these, they are the spine you can rely on while improvising on the process-specific questions.

Introduction & objectives

  • What are your main objectives for implementing Dynamics 365 for this process?
  • What are the key challenges you are currently facing in this process?
  • Are there key differences between legal entities, business units, or departments that need to be considered?

Process scope (during scenario-board walk-through)

  • What are the key scenarios in your process? Which is the primary one for the next phase?
  • Are there scenarios that should not be on this diagram? (Out of scope.)
  • Are there scenarios missing from the diagram? (Potential gaps.)
  • What key differences do you see between your current process and this standard process? (Document for change management.)
  • What are the key pain points or bottlenecks today?

Detailed scenarios

  • Are there policies that need to be reviewed or adjusted as part of this project?
  • What are the most critical scenarios you encounter?
  • Volume question (always reframed for the process, "How many POs / sales orders / employees / assets / projects / cases do you manage today?").
  • What systems or tools are you using today?
  • How do you ensure regulatory compliance in this process?
  • What improvements or changes would you most like to see?

Data migration (every workshop)

  • What data needs to be migrated to the new system?
  • How is data currently managed and stored?
  • Are there known data quality issues that must be addressed before migration?
  • What challenges do you anticipate during migration?
  • How will you validate and verify the migrated data?

Integrations (every workshop)

  • What systems need to integrate with the new system?
  • How is data currently exchanged between systems? (Frequency, volume.)
  • Are there specific integration requirements or protocols (SFTP, API, EDI, real-time vs. batch)?
  • What challenges do you anticipate during the integration build?
  • How will integrations be tested and validated?
CatalogThe 14 workshops

The 14 end-to-end processes Microsoft documents in the BPW set. For each, the process-specific scope (the L2 areas covered) and the questions that matter most for a D365 F&O consultant. Cross-cutting questions (data migration, integrations, intro objectives) are not repeated here, refer to the previous section.

Source to pay (75), procurement & AP

Scope: from defining procurement strategy through paying the supplier. The AP-side bookend of the supply chain.

L2 areas covered

  • 75.10 Develop procurement and sourcing strategy
  • 75.30 Manage supplier relationships
  • 75.35 Source and contract goods and services
  • 75.40 Procure goods and services
  • 75.50 Manage accounts payable
  • 75.80 Analyze procurement and sourcing

Process-specific questions that matter

  • How are POs placed today, manual, EDI, requisition, planned PO, RFQ, purchase agreement?
  • Are products single- or multi-sourced? Is there a multi-sourcing strategy?
  • Are pricing rules complex? Tiered? Blanket / standing POs?
  • Will purchase requisitions be used? For both direct and indirect spend?
  • Are there spending and signing limits per requisition / PO?
  • Workflows on requisitions and POs, yes or no?
  • Intercompany ordering requirements?
  • Invoice intake, manual, OCR, EDI, vendor portal? Two-way or three-way match?
  • Process for resolving PO-invoice matching exceptions?
  • Vendor payment techniques, checks, ACH, wire, virtual cards, P-card?
  • Prepayments vs. prepayment invoices, does the team know the difference?
  • Vendor self-service / collaboration in scope?
  • Consignment inventory in scope?
  • Same vendor in multiple legal entities, how is creation/edit controlled?
Order to cash (65), sales & AR

Scope: from sales policy and order capture through customer payment and collection. The AR-side bookend.

L2 areas covered

  • 65.05 Develop sales policies
  • 65.20 Manage sales orders
  • 65.30 Manage accounts receivable
  • 65.50 Manage credit and collections
  • 65.60 Analyze sales performance

Process-specific questions that matter

  • What sales channels exist, POS, B2B / B2C eCommerce, call center, traditional, EDI? Which are in scope for D365?
  • Pricing strategies, list, tiered, customer-specific, contract pricing?
  • Discount and promotion policies, line, total, mix & match, threshold?
  • Trade allowances, bill back, off-invoice, lump sum, rebates?
  • Order types, standard SO, blanket order, return order, subscription/recurring?
  • Order on behalf of / call center / e-commerce specifics?
  • Sales tax, multi-jurisdiction? Tax engine integration (Avalara, Vertex)?
  • Credit limit rules, when to block, who can override?
  • AR settlement automation, auto-apply, lockbox, customer portal payments?
  • Collections, aging buckets, dunning letters, agent assignments, write-off rules?
Record to report (90), finance & close

Scope: the entire financial management lifecycle, chart of accounts through period close and analysis. Multi-entity, multi-currency, corporate and operational finance.

L2 areas covered

  • 90.10 Define accounting policies
  • 90.25 Manage cash
  • 90.30 Manage budget
  • 90.50 Record financial transactions
  • 90.60 Close financial periods
  • 90.70 Analyze financial performance

Process-specific questions that matter

  • What accounting standards apply, GAAP, IFRS, local? Multiple in parallel?
  • Chart of accounts and financial dimension structure, how many dimensions, how many accounts?
  • How many legal entities, currencies, fiscal calendars?
  • Multi-entity / shared services / centralized accounting model?
  • Intercompany accounting setup, auto-balancing, due-to / due-from accounts?
  • Cash management, daily cash positioning, forecasting, treasury operations?
  • Bank reconciliation, manual, advanced, statement formats (BAI2, MT940, ISO20022)?
  • Budgeting approach, basic register entries vs. full budget plans? Budget control on what documents?
  • Journal automation, recurring, allocation rules, accruals?
  • Subledger-to-GL integration, auto post or batched?
  • Month-end and year-end close process, current pain points, time to close?
  • Consolidation, online, import, or external tool?
  • Reporting tools today, Financial Reporter, Power BI, third-party? Which scenarios?
Acquire to dispose (10), asset lifecycle

Scope: end-to-end asset management, from sourcing the asset to retiring it, covering both fixed asset accounting and physical asset maintenance.

L2 areas covered

  • 10.05 Define asset strategy and policies
  • 10.20 Acquire assets
  • 10.30 Manage active assets
  • 10.50 Maintain and repair assets
  • 10.60 Retire and dispose of assets
  • 10.70 Analyze assets

Process-specific questions that matter

  • Build vs. buy vs. lease, which scenarios are in scope?
  • Lease accounting, ASC 842 / IFRS 16 in play? In scope or out?
  • Capitalization threshold? Depreciation methods used?
  • Acquisition paths, manual, PO, requisition, project (CIP), P-card?
  • Asset types, tangible high/low value, intellectual property, trademarks, land?
  • Active asset events, depreciation, revaluation, write-up/down, transfer?
  • Maintenance, planned (preventive) and unplanned, internal vs. third-party?
  • Disposal scenarios, sale, scrap, decommission?
  • How many active assets today? How often are they retired?
Hire to retire (55), HR lifecycle

Scope: end-to-end HR, from people strategy through offboarding and analysis.

L2 areas covered

  • 55.05 Develop people strategy
  • 55.10 Recruit and onboard talent
  • 55.30 Manage workplace compliance
  • 55.40 Manage performance and growth
  • 55.50 Manage time and attendance (incl. travel and expense)
  • 55.70 Manage compensation and benefits
  • 55.80 Offboard talent
  • 55.90 Analyze HR

Process-specific questions that matter

  • Organizational structure, how many legal entities, business units, departments?
  • Planned organizational changes during the project window?
  • Recruiting sources, postings, agencies, referrals, campus?
  • Worker types, full-time, part-time, intern, contractor, all in scope?
  • Position management used today? Budgeted positions vs. unbudgeted?
  • Compliance topics, labor laws, EEO, GDPR, country-specific?
  • Performance review cycle, annual, quarterly, 360, continuous?
  • Time and attendance system today? Clock-in scenarios?
  • Travel & expense, credit card import, per diems, mileage, mobile capture?
  • Compensation plans, fixed, variable, equity? Cycle frequency?
  • Benefit plans in scope?
  • Payroll, F&O native (US), partner / outsourced? Integration model?
  • Offboarding, voluntary, retirement, termination, distinct flows?
Plan to produce (70), manufacturing execution

Scope: production strategies, planning, execution, quality, and analysis. Covers discrete, process, and lean manufacturing.

L2 areas covered

  • 70.10 Develop production strategies
  • 70.20 Plan production operations
  • 70.30 Run production operations
  • 70.60 Control production quality
  • 70.70 Analyze production operations

Process-specific questions that matter

  • Manufacturing model, discrete, process, lean, or mixed? Per site?
  • Make-to-stock, make-to-order, assemble-to-order, engineer-to-order, which apply?
  • MPS / MRP / capacity planning, current tooling and pain?
  • Production order types, production orders, batch orders, kanbans?
  • BOMs, single-level, multi-level, multi-site? Versioning?
  • Formulas, co-products, by-products, scalable, step consumption?
  • Routes / operations / resources / resource groups?
  • Quality control checkpoints, incoming, in-process, outgoing?
  • Production KPIs, OEE, scrap, downtime, schedule adherence?
  • Shop-floor execution, paper, MES, F&O production floor execution interface?
  • Co-products, by-products, rework, handled how today?
  • Seasonality / demand fluctuation impact?
Inventory to deliver (60), warehouse & transportation

Scope: warehouse operations, inventory management, inbound/outbound flows, quality, and freight.

L2 areas covered

  • 60.10 Manage warehouse operations
  • 60.20 Maintain inventory levels
  • 60.30 Process inbound goods
  • 60.40 Process outbound goods
  • 60.50 Manage inventory quality
  • 60.60 Manage freight and transportation
  • 60.80 Analyze warehouse operations

Process-specific questions that matter

  • How is on-hand inventory managed today? High transaction volume?
  • Will inventory journals be used for the initial on-hand load?
  • Will counting journals be used for cycle counts? Block on count?
  • Intracompany site / warehouse transfers in scope?
  • Quality management requirements?
  • Advanced WMS or basic warehousing?
  • Distribution network and warehouse layout document available?
  • Virtual warehouses or virtual locations needed?
  • Tracking dimensions, batch, serial, required?
  • Product variants in scope?
  • Physical dimensions on items? Volumetric capacity constraints?
  • Cycle count frequency? Order release process? Wave templates?
  • Warehouse mobile app, handheld scanners? Credential model?
  • Label printing requirements?
  • Catch weight functionality required?
  • Transportation Management, load planning, rate engines, freight reconciliation in scope?
  • Hazardous goods?
  • WHS cleanup jobs scheduled?
Forecast to plan (50), strategic & S&OP

Scope: strategic and operational planning, business strategy, financial planning, S&OP, execution, and analysis.

L2 areas covered

  • 50.15 Develop business strategy
  • 50.55 Conduct financial planning
  • 50.35 Conduct sales and operations planning
  • 50.45 Execute sales and operations
  • 50.65 Analyze business performance

Process-specific questions that matter

  • Strategic planning cycle, annual, rolling, scenario-based?
  • Forecasting types, budget, revenue, expense, cash flow, demand?
  • S&OP scenario, make-to-stock, make-to-order, project-centric, product-centric?
  • Demand planning tooling today (Excel, dedicated tool, none)?
  • Capacity / supply planning integration with demand?
  • ESG / sustainability requirements feeding strategy?
  • Investment planning and risk assessment in scope?
Project to profit (80), project lifecycle

Scope: project management and accounting, internal and external projects, contracts, delivery, financials, and analysis.

L2 areas covered

  • 80.10 Develop project strategy (internal and external)
  • 80.20 Manage project contracts
  • 80.30 Plan projects
  • 80.40 Manage project delivery
  • 80.50 Manage project financials
  • 80.60 Analyze project performance

Process-specific questions that matter

  • Project types, internal, customer-funded, capital, R&D, grant-funded, MRO?
  • Differentiation by project type in governance, financials, reporting?
  • Contract structures, T&M, fixed price, cost-plus, milestone, subcontractor?
  • Change order management, scope, pricing changes?
  • WBS, resource planning, scheduling methodology (Agile, Waterfall)?
  • Resource assignment, internal employees, contractors, mix?
  • Time tracking, system, integration with HR?
  • Revenue recognition, POC, completed contract, milestone? ASC 606 / IFRS 15 application?
  • Internal cost capitalization rules?
  • Project KPIs, margin, utilization, earned value?
  • Integration with HR (employee master, absence, time), payroll, learning system (skills/levels)?
Prospect to quote (85), pre-sales

Scope: the front of the sales funnel, relationships, leads, opportunities, and quoting. Heavy overlap with Dataverse-based D365 Sales.

L2 areas covered

  • 85.15 Manage customer relationships
  • 85.25 Identify and qualify sales
  • 85.35 Define sales strategy and policies (incl. channels)
  • 85.45 Pursue opportunities
  • 85.55 Estimate and quote sales
  • 85.65 Analyze sales

Process-specific questions that matter

  • Lead generation sources, campaigns, referrals, web forms, inbound, outbound?
  • Lead scoring and qualification framework, BANT, MEDDIC, custom?
  • Marketing-to-sales handoff process?
  • Sales channels, direct, partner, digital, brick-and-mortar, call center, online?
  • Quote pricing models, standard, tiered, negotiated?
  • Discount / approval thresholds and workflow?
  • Quote delivery, PDF, portal, email?
  • Where does the system live, F&O Sales & Marketing or Dataverse-based D365 Sales? Integration model?
Concept to market (30), marketing

Scope: marketing strategy, offering development, campaigns, and analysis. Often delivered with Dynamics 365 Customer Insights, Journeys / Data.

L2 areas covered

  • 30.05 Develop marketing strategy
  • 30.15 Research and develop offerings
  • 30.25 Manage service offerings
  • 30.35 Prepare marketing campaigns
  • 30.45 Manage marketing campaigns
  • 30.55 Analyze marketing operations

Process-specific questions that matter

  • Marketing goals and KPIs, engagement, conversion, ROI?
  • Customer segmentation and targeting tools today?
  • Customer data, single source or fragmented? Enrichment process?
  • R&D collaboration tools? VoC programs?
  • Service / offering catalog, how maintained? Bundles, subscription, usage-based?
  • Campaign channels, email, social, advertising, events?
  • Compliance, GDPR, CCPA, consent management, accessibility?
  • Integration with Sales, Commerce, Supply Chain, real-time or batch?
Design to retire (40), product lifecycle

Scope: product information management, strategy, introduction, active management, and retirement. Owns the master that feeds everything else.

L2 areas covered

  • 40.10 Develop product strategy
  • 40.20 Introduce products
  • 40.50 Manage active products
  • 40.60 Retire products
  • 40.90 Analyze product performance

Process-specific questions that matter

  • Product types, tangible, service, intangible? BOM, formula, configurable?
  • Product dimensions, size, color, style, configuration? Variant generation strategy?
  • Categorization hierarchy, procurement, sales, retail?
  • Stocking policies, batch, serial, allocation, reservation?
  • Costing methodology and policies?
  • BOM / formula complexity, single-level, multi-level, multi-site, scalable, step consumption?
  • Co-products / by-products?
  • Catalogs, internal, external/vendor, punch-out?
  • POS-relevant attributes, assortments?
  • Total active products today? Retirement frequency?
  • Product release process across legal entities?
Service to deliver (95), field service

Scope: service strategy, planning, execution, delivery, and analysis. Often delivered with Dynamics 365 Field Service.

L2 areas covered

  • 95.05 Develop service strategy
  • 95.15 Plan service work
  • 95.25 Manage service work
  • 95.35 Deliver services
  • 95.45 Analyze service performance

Process-specific questions that matter

  • Service types, break/fix, preventive, predictive (IoT), warranty, contract, depot, field?
  • Scheduling, manual, assisted, Resource Scheduling Optimization (RSO), territory, skill, crew?
  • Resource model, internal, third-party contractors, mixed?
  • Planning inputs, IoT alerts, customer requests, preventive plans, case escalations?
  • Work order creation, from case, IoT, schedule, manual, sales/project?
  • Entitlement & SLA validation, warranty, contract, response time?
  • Inventory and parts, issue, transfer, return?
  • Billing model, flat rate, T&M, contract?
  • Customer communication and documentation?
  • Performance, SLA compliance, first-time-fix rate?
  • Integration with Finance, Supply Chain, Customer Service?
Case to resolution (20), customer service

Scope: customer-service operations, knowledge, intake, working cases, and analysis.

L2 areas covered

  • 20.10 Establish a knowledge base
  • 20.20 Define customer and employee service operations
  • 20.30 Intake cases
  • 20.40 Manage and work on cases
  • 20.60 Analyze case performance

Process-specific questions that matter

  • Knowledge base structure, internal, external (self-service), AI-suggested?
  • Approval and publishing workflow for articles? Translation needs?
  • Internal employee service vs. external customer service, both in scope?
  • Case intake channels, email, portal, phone, chat, social, IoT?
  • Tiered support model, L1, L2, L3? Follow-the-sun?
  • Routing and prioritization rules? Workload balancing?
  • Escalation and SLA policies?
  • Field service escalation handoff?
  • Customer feedback / CSAT capture?
  • Telephony / contact center integration, CTI, omnichannel?
  • Use of Copilot or AI for resolution and authoring?
CraftRunning discovery well, consultant tips

The BPWs give you the structure, but the value of discovery comes from how you run the room. The notes below are not in the Microsoft docs, they're the things experienced consultants learn the hard way.

Before the workshop

  • Send the scenario board in advance. Ask the customer to read it. Do not let people see it for the first time in the room, you'll spend the first 30 minutes explaining the diagram instead of running the workshop.
  • Confirm the right people are coming. If the AP manager is double-booked for the Source to pay workshop, reschedule. A workshop without the process owner is a meeting, not a workshop.
  • Pre-read their existing process docs. Show up knowing what their flow looks like. Asking "tell me how you do AP today" from a blank slate signals the wrong kind of consultant.
  • Have a neutral scribe. The lead consultant cannot run the room and capture cleanly at the same time. Use a second consultant or BA.

In the room

  • Walk the scenario board left to right. Don't let the conversation jump around. The board is a discipline, use it.
  • Mark up the board live. In/Out/Gap on every column. If you leave the room without ink on the board, you didn't run a workshop.
  • Get to the “volume” question early. "How many POs / orders / employees / assets per month?" reframes everything that follows. Manual processes that work at 200/month break at 20,000.
  • Push past policy answers. When someone says "We do three-way match, " ask "What's your exception rate? What does an exception cost in time?" Policy is the answer they tell auditors. Reality is what you need.
  • Capture pain points verbatim. "It takes 3 days to resolve a PO mismatch" is a usable requirement. "We have AP issues" is not.
  • Defer the deep dive. When someone wants to debate a single field's setup in the scenario board workshop, write it down and move on. The deep-dive workshop is where that lives.
  • Document decisions, not just discussion. "In scope: X, Y, Z. Out of scope: A. Gaps: B." Send it the same day.

Common traps

  • "Just like the legacy system." Beware of requirements that copy the old ERP's quirks. Ask "If you were starting fresh, would you still want it this way?"
  • Blue-sky requirements. "We'd like the system to predict the future." Park them in a wishlist, but make clear they are not project scope.
  • The loud voice. One outspoken stakeholder dominating. Round-robin specific questions to others by name.
  • The silent room. If no one is pushing back on the scenario board, you have not earned trust. Ask provocative questions ("This standard process treats X as out of scope, is that right for you?") to start a real conversation.
  • Skipping change management. If the standard D365 flow is materially different from theirs, flag it for change management at the moment of discovery, not three months later.
  • Closing without next steps. Every workshop should end with: who, does what, by when. Otherwise momentum dies.

The output

From a scenario board workshop you should walk out with: the marked-up board (photo), a one-page meeting note (decisions, in/out/gap, action items), the deep-dive schedule, and confirmed parking-lot items. The deep-dive workshops then feed the requirement log that becomes the input to fit-gap analysis (the next phase).

Phase 2 of 10

Fit-gap analysis

Mapping each requirement against standard D365 F&O capability, and deciding what to do with the gaps.

Fit-gap analysis is the process of comparing the requirements gathered in Phase 1 against the standard, out-of-the-box capabilities of Dynamics 365 Finance & Operations. According to Microsoft's Success by Design framework, identifying gaps early is critical to preventing architectural debt and scope creep later in the project.

Classification of Requirements

  • Fit: The requirement is natively supported by D365 F&O. This might require standard configuration (e.g., setting up a specific posting profile or workflow), but no code changes.
  • Partial Fit: The system meets the core need, but a small tweak is required. This often results in a minor customization, a Power Automate flow, or a localized reporting change.
  • Gap: The system cannot fulfill the requirement. This is where architectural decisions must be made.

The Hierarchy of Resolving Gaps

When a true gap is identified, a seasoned D365 consultant will address it in the following order of preference:

  1. Change the Business Process: Can the business adapt to how D365 works? This is always the cheapest and most upgrade-safe option.
  2. Leverage the Power Platform: Can a Power App or Power Automate flow solve the issue without altering the core ERP?
  3. Use an ISV Solution: Is there a certified Independent Software Vendor (ISV) on AppSource that already solves this problem (e.g., advanced tax calculation, specific manufacturing execution)?
  4. Customize (X++): As a last resort, write custom X++ code. Every customization adds technical debt and maintenance overhead during Microsoft's mandatory One Version updates.
Phase 3 of 10

Documentation: FRD and FDDs

Turning agreements into binding documents, Functional Requirement Documents and Functional Design Documents.

Once the fit-gap analysis is signed off, the team moves into formal documentation. In D365 implementations, this is typically tracked within Azure DevOps (ADO), where business requirements become Epics and Features, and customizations become User Stories and Tasks.

The Functional Requirement Document (FRD)

The FRD is the business view. It outlines what the system must do. It contains the agreed-upon business processes, the scope boundaries, required integrations, and reporting needs. A well-written FRD speaks the language of the business and serves as the baseline for user sign-off.

The Functional Design Document (FDD)

For every "Gap" that requires customization, a Functional Design Document (FDD) must be written. The FDD translates the business requirement into a technical blueprint. A robust FDD for D365 F&O includes:

  • Data Model Impact: Which standard tables are being extended? Are new tables required?
  • User Interface (UI): Mockups of form changes. Where will the new button live? What fields are added to the grid?
  • Business Logic: The specific conditions and validations the X++ developer needs to write.
  • Security: Which roles, duties, and privileges will have access to this new feature?
  • Data Entities: If a new table is created, does it need a data entity for data migration (DMF) or OData integration?
Phase 4 of 10

Data templates & client data workshops

Defining what the client must hand over, and walking them through it before they start filling it.

Data migration is consistently one of the highest-risk areas in any ERP implementation. In D365 F&O, data is imported using the Data Management Framework (DMF), which utilizes Data Entities to validate and load data into the normalized SQL tables.

The Data Templates

Consultants provide the client with Excel-based data templates generated directly from D365 data entities. These templates cover:

  • Setup Data: Chart of Accounts, Financial Dimensions, Customer Groups, Payment Terms.
  • Master Data: Customers, Vendors, Products, Employees, Fixed Assets.
  • Opening Balances: Open AP/AR invoices, inventory on-hand, GL balances.

The Data Workshops

Handing a client an Excel template with 150 columns (like the CustCustomerV3Entity) and saying "fill this out" is a recipe for failure. During data workshops, the consultant walks the client through the template, identifying which fields are mandatory, which fields dictate business logic (e.g., linking a customer to a tax group), and how to map legacy data into the new structure.

Sequencing matters

Data must be loaded in a strict dependency order. You cannot load a Vendor if their associated Vendor Group hasn't been created. A "Gold Build" environment is typically maintained to practice and time these data loads, ensuring the final cutover weekend is predictable.

Phase 5 of 10

Conference Room Pilots (CRPs)

Showing the configured system back to the business, with their data and their flows, early and often.

A Conference Room Pilot (CRP) is an iterative "show and tell" session. Unlike traditional waterfall projects where the client waits months to see the system, CRPs put the configured D365 environment in front of the business as early as possible.

CRP 1: The Standard Show

CRP 1 usually happens shortly after requirements gathering. The consultant demonstrates the standard, out-of-the-box D365 flow using generic data (e.g., the Contoso demo data). The goal is to visually anchor the business to how standard D365 operates and to validate the fit-gap assumptions.

CRP 2: The Client Context

CRP 2 is much deeper. The environment is loaded with a slice of the client's actual master data (their items, their customers), and the consultant runs through the specific, end-to-end scenarios identified in Phase 1. This is where the business begins to see their actual daily life modeled in the new system. It is common to identify new gaps or refine requirements during CRP 2.

The outcome of a successful CRP is a finalized design, paving the way for development to finish and for the business to begin writing their UAT test scripts.

Phase 6 of 10

UAT 1 & user / super user training

The first formal test, business users execute scripted scenarios in a near-final environment, and learn the system as they go.

User Acceptance Testing (UAT) is the formal phase where the business users take the keyboard. The goal is to prove that the system can handle daily operations and that customizations function exactly as designed in the FDDs.

Execution and Tools

During UAT 1, users follow heavily scripted scenarios. In the D365 ecosystem, this is greatly aided by the Task Recorder, a tool that records a user's clicks and automatically generates step-by-step Word documents or interactive on-screen guides.

For organizations implementing CI/CD (Continuous Integration/Continuous Deployment), these Task Recordings are loaded into the Regression Suite Automation Tool (RSAT). RSAT converts the recordings into automated tests that can be run against every new Microsoft update, ensuring custom code doesn't break when Microsoft releases a new version of F&O.

The Role of Super Users

UAT is often combined with "Train the Trainer." Super users (SMEs from the business) are trained by the consultants. These super users then execute UAT, inherently learning the system deeply. When go-live arrives, these super users become the first line of support for the wider end-user base, significantly increasing user adoption and confidence.

Phase 7 of 10

UAT 2 / parallel run with updated setup

A second pass with the fixes from UAT 1, often a parallel run against the legacy system to validate end-of-period numbers.

UAT 2 serves as the final proving ground. While UAT 1 focuses on functional correctness, UAT 2 often incorporates performance testing, security role validation, and the critical Mock Cutover.

The Mock Cutover

A mock cutover is a dress rehearsal for the go-live weekend. The technical team executes the complete data migration plan extracting from legacy, transforming, and loading into a fresh D365 Tier-2+ environment while timing every step. This ensures that the actual go-live window (typically 48 hours over a weekend) is achievable.

The Parallel Run

For highly complex or risk-averse organizations, UAT 2 may include a parallel run. For a defined period (e.g., one month), the business processes transactions in both the legacy system and D365 F&O simultaneously. At month-end, the financial reports are compared. If the Trial Balance, AP Aging, and AR Aging match, the system is financially reconciled and ready for production.

Phase 8 of 10

Production environment

Standing up the real environment, LCS, security, data migration, and the cut-over plan.

Standing up the Production environment in D365 F&O is tightly controlled by Microsoft. Unlike lower-tier development (Tier 1) or UAT (Tier 2+) sandbox environments, the Production environment is managed entirely through Dynamics Lifecycle Services (LCS) and requires Microsoft approval to deploy.

The FastTrack Go-Live Readiness Review

Before Microsoft provisions the Production environment, the project team must pass the Success by Design Go-Live Readiness Review. This is a comprehensive audit where the Microsoft FastTrack team verifies:

  • UAT has been formally signed off by the business.
  • Performance testing is complete and successful.
  • The cutover plan is documented and timed.
  • A support plan (Hypercare) is in place.
  • Security roles are finalized, and no users have "System Administrator" access for daily work.

Once approved, Microsoft deploys the environment, and the team applies the "Golden Configuration" (the final, approved setup data) via the Data Management Framework.

Phase 9 of 10

Go-live

The switch from old to new, typically a long weekend, with a war room, a checklist, and clear rollback criteria.

Go-live is the climax of the project. It is typically executed over a weekend (the "dark hours") to minimize business disruption. It follows a highly choreographed, hour-by-hour runbook.

The Cutover Weekend

  1. System Freeze: The legacy system is locked down. No new transactions are allowed.
  2. Data Extraction: Final open transactions and master data are extracted from the legacy database.
  3. Data Load: The DMF is used to load the final data into the D365 F&O Production environment.
  4. Financial Reconciliation: The finance team verifies that the opening balances in D365 match the closing balances of the legacy system to the penny.
  5. Go/No-Go Decision: Project leadership meets to review the cutover status. If critical failures occurred, the fallback plan is initiated. If successful, the system is opened to users.

On Monday morning, users log into D365 F&O for the first time. The golden rule of the cutover period: No new features. If it wasn't tested in UAT, it does not go into Production.

Phase 10 of 10

Hypercare & post-go-live support

The first 4–8 weeks after go-live, when consultant presence is highest and small problems can become big ones if missed.

The moment the system goes live, the project enters Hypercare. This is a 4 to 8-week stabilization period characterized by intense, hands-on support from the consulting team.

Triage and Stabilization

During the first few weeks, the volume of support tickets will spike. A significant portion of these will be "how-to" questions or minor security role adjustments, not system defects. The consulting team runs daily triage meetings to separate user training issues from actual bugs.

The true test of Hypercare is the first month-end close. Consultants sit side-by-side with the finance team to ensure that depreciation runs, foreign currency revaluations, and financial consolidations execute flawlessly in the live system.

Transition to BAU

As the ticket volume drops and the system stabilizes, the implementation team begins a formal handover. Documentation is finalized, open issues are transferred to the client's internal IT team or a Managed Services provider, and the project officially transitions into Business As Usual (BAU).