Utilization, Billing, and Realization: Why Firms on Dynamics SL Are Migrating to D365 Project Operations

SL Was Great — Until the Walls Closed In

Dynamics SL was the go-to ERP for project-based services firms for over a decade.

Engineering firms, IT consultancies, architecture practices, environmental services companies — if you billed by the hour and tracked profitability by project, SL understood your business in ways that GP and NAV never did. It handled timesheets, project billing, job costing, and revenue recognition with a depth that made it the obvious choice for professional services organizations in the mid-market.

But SL's architecture is aging in ways that matter. The client-server design that worked perfectly in 2010 doesn't support remote workforces, mobile time entry, or the real-time analytics that firm leadership now expects. The support window is closing, and the ecosystem of consultants and ISVs who built around SL is thinning rapidly. Most critically, the firms that built their operations on SL are discovering that the system they relied on for years is now the bottleneck preventing them from scaling — not because SL broke, but because the demands of running a modern services firm outgrew what SL was designed to handle.

If your firm's growth strategy depends on better resource utilization, faster billing cycles, more accurate project profitability, and real-time visibility into firm performance, the conversation about SL's replacement isn't premature. It's overdue.

Where Does Dynamics SL Fall Short for Services Firms in 2026?

The limitations that drive services firms off SL typically cluster around four operational areas that directly impact profitability:

• Utilization tracking is retrospective, not proactive: In SL, you see last month's utilization rates after the month-end close — sometimes a week or more into the following month. By then, it's too late to rebalance resources, accelerate stalled projects, or redeploy underutilized consultants. You're managing utilization through the rearview mirror. Firms that compete on utilization need to see it in real time — daily or even hourly — to make the staffing adjustments that protect margins.

• Resource planning is tribal knowledge: Assigning the right people to projects in SL means someone — usually a practice lead or resource manager — maintaining a mental model of who's available, who's qualified, who's wrapping up a project next week, and who's been on the bench too long. That model lives in spreadsheets, email threads, and hallway conversations. It works when you have 30 billable staff. At 100+, it breaks — and the breakage shows up as misassigned resources, bench time that could have been avoided, and projects that start late because the right person wasn't identified in time.

• Mixed billing complexity exceeds SL's design: Most growing services firms operate with multiple billing models simultaneously — time and materials for some clients, fixed-fee for others, milestone-based for projects, retainer for ongoing relationships. In SL, each billing model requires a different project configuration, and the complexity compounds when a single client engagement includes multiple billing types. Revenue recognition across these models requires manual calculation and journal entries that consume accounting hours and introduce error risk.

• Realization analysis requires Excel: Understanding the gap between billed revenue, collected revenue, and earned revenue — the realization metrics that determine whether your firm is actually profitable or just busy — requires exporting data from SL to Excel and building the analysis manually. By the time the analysis is complete, the numbers are already stale, and the opportunity to address collection issues or billing gaps in the current period has passed.

  
  

What Does D365 Project Operations Deliver for Services Firms?

D365 Project Operations was designed specifically for the project-based services model — from opportunity through delivery through billing through revenue recognition — as an integrated end-to-end platform:

• Real-time utilization dashboards: See billable versus non-billable hours across the entire firm as time entries are submitted — not after month-end processing. Practice leads can see which consultants are underutilized today and take action today, not three weeks later. Utilization targets by role, practice area, and individual update continuously, giving management the visibility to make staffing decisions that protect margin in real time.

• AI-assisted resource scheduling: The resource scheduling engine matches people to project requirements based on skills, certifications, availability, location, and cost rate. When a new project needs a senior consultant with healthcare industry experience and Power BI skills, available starting next Monday, the system identifies candidates — ranked by fit — without anyone searching a spreadsheet or sending emails asking "who's available?"

• Unified billing engine: Time and materials, fixed-fee, milestone, retainer, and expense billing run through a single billing engine with configurable invoice formats. A single client engagement can include multiple billing types, and the system generates the correct invoice with the correct revenue recognition treatment for each. No more separate project configurations for different billing models — it's all handled in one project structure.

• Project profitability at the task level: Actual versus budget tracking updates as time entries and expenses are submitted. Project managers see current margin in real time and can identify cost overruns at the task level before they erode the overall project margin. Forecasting adjusts automatically as actuals come in — if a phase is running 20% over budget at the 50% completion mark, the system projects the impact on total project profitability and alerts the project manager.

• Integrated opportunity-to-delivery pipeline: Project Operations connects to D365 Sales, so the pipeline from opportunity through proposal through SOW through project creation is a continuous workflow. The estimated hours and revenue from the proposal flow directly into the project plan — no re-keying, no disconnected spreadsheet handoff between sales and delivery.

  
  

What Does the Migration Path from SL to Project Operations Look Like?

SL firms typically migrate in a structured sequence that minimizes disruption to active client engagements. Project masters, client records, employee records, rate tables, and open projects migrate to D365 Project Operations through a planned cutover. Active projects continue in SL until a natural breakpoint (phase completion, billing cycle, or calendar boundary), then transition to the new system.

Historical project data — completed projects, archived timesheets, past billing records — archives to Power BI for continuity. Firm leadership retains access to historical utilization, realization, and profitability metrics without the data volume slowing down the new system. The transition is measured in months, not years — typical implementations for mid-market services firms run 4–6 months from kickoff to go-live.

The Firm's Growth Depends on Visibility — Not Just Effort

The services firms that grow sustainably past $10M, $25M, $50M in revenue share a common characteristic: they make resource and pricing decisions based on real-time data rather than retrospective reports and gut feel. They know which practice areas are profitable and which are subsidized. They know which clients generate margin and which consume it. They know which consultants are underutilized before the month ends, not after.

If your firm's growth is constrained by the limits of Dynamics SL — the retrospective visibility, the manual resource planning, the billing complexity, the Excel-dependent analytics — the path forward is clear.

Take Turnkey's free Dynamics 365 Suitability Assessment to see what D365 Project Operations would look like for your specific practice — and what your team could accomplish with real-time visibility into the metrics that drive firm profitability.