Dynamics CRM On-Premises to Dynamics 365: OP2OL Migration, FastTrack Limits and Cutover Checklist

One caveat up front: this is a Microsoft customer story, which is marketing material. The executive quotes and reported benefits below are Bright Horizons' and Microsoft's own account. Nobody has independently audited them, and the story gives no hard before-and-after numbers.

Who Bright Horizons is and what was broken​

Microsoft says Bright Horizons Family Solutions was founded in 1986. It provides employer-sponsored childcare, early education, backup care, family support and education advisory services. It works with thousands of employers and serves millions of families in the United States and elsewhere, Microsoft among them. Its services include tutoring, college advising and continuing education for adults.

As the business grew, its on-premises Dynamics CRM system became a constraint. According to the story, the system was "stable and familiar." The trouble was that every new capability needed custom work, and data integration kept getting harder. Sales, service and marketing also ran on separate systems, so no one had a complete view of a customer.

Nidhi Taneja, Bright Horizons' vice president of enterprise product management, said the goal was "consumer centricity," and that unifying those customer views meant moving to the cloud.

Summary: The old CRM still worked. The problems were the cost of adding anything new and the split between sales, service and marketing systems.

The migration: lift-and-modernize, not rebuild​

Bright Horizons started by moving its on-premises CRM to Dynamics 365 Sales and Dynamics 365 Customer Service using Microsoft's OP2OL migration services through FastTrack. The project kept core functionality in place and also:

• Refactored integrations
• Moved reporting to Power BI
• Moved users to the Unified Client Interface
• Put sales, service and customer data in one environment on a shared Dataverse

The new system went live in May 2025 and serves about 250 internal users across sales and service. Vish Chawla, group vice president of engineering, said OP2OL was one of the selling points for migrating. He said building from scratch can take "months or quarters." That is an executive's estimate, not a measured comparison.

Kara Conley, strategic operations executive, called it the company's most complex migration and also its smoothest. She said that when it went live, teams found it "no different from the day before." Bright Horizons also used Power Platform to extend Dynamics 365 without heavy custom development, though the story doesn't say which apps or automations it built.

What OP2OL actually involves​

The customer story calls OP2OL "a helpful tool" and leaves it there. Microsoft's own documentation and partner guidance fill in more detail, which matters for any admin still running Dynamics CRM in a server room.

Version requirements. Microsoft's FastTrack guidance on Microsoft Learn says the OP2OL migration services currently support Dynamics CRM V9.0 (on-premises) and later versions. Older installs need an upgrade path first. Engineered Code, a partner, notes that the older multi-hop upgrade sequence (2011 to 2013 to 2015 to 2016) and that the FastTrack process automates the process of performing the upgrades to the servers. That account predates the current V9.0 floor, so check today's requirements before you plan.

Getting in. Microsoft says partners and customers can nominate for the migration services for on-premises to online (OP2OL) through the self-serve tool. A guidance summary based on Microsoft's documentation adds that customers must procure Dynamics 365 online licenses before initiating the migration process.

The tooling. A Microsoft Dynamics Community post explains that regardless of the FastTrack engagement model, the migration leverages Lifecycle Services (LCS), to automate platform level operations, allowing full control of its progress and reducing the need to install software or run scripts.

What FastTrack won't do. The same post is blunt: this is not a professional services engagement, hence there is no hands-on keyboard work performed by the FastTrack team to remediate any issues that are a result of customization, unsupported configurations or to make changes to your code base. That explains why the customer story mentions working with "partners and Microsoft FastTrack experts." Partners do the remediation work. FastTrack advises.

The cutover catch. Engineered Code warns that if you are not able to take your existing Dynamics instance offline during the process, then you have to figure out your own way to determine what changes occurred during the migration to your on-premise instance, since the FastTrack program is based on the database backup taken at one specific instance in time. It also notes that if you have an incredibly large database, the migration process can take hours.

A practical OP2OL checklist​

Based on the guidance above (this is a summary, not an official Microsoft runbook):

1. Confirm your version. You need Dynamics CRM V9.0 on-premises or later. Plan upgrades if you're behind.
2. Buy licenses first. Make sure the target tenant has the right Dynamics 365 online licenses and capacity.
3. Nominate. Use Microsoft's self-serve OP2OL nomination tool yourself or through a partner.
4. Inventory customizations. Unsupported configurations and custom code are your job or your partner's, not FastTrack's.
5. Plan the cutover window. The migration runs from a point-in-time backup, so either freeze the source system or have a way to catch up on changes made during the move.
6. Rework the edges. As Bright Horizons did, expect to refactor integrations, rebuild reporting (often in Power BI), and retrain users on the Unified Client Interface.

Summary: OP2OL moves your existing database rather than rebuilding it. Microsoft provides the tooling and guidance, and fixing custom code is up to you or your partner.

After the move: Customer Insights and a two-vendor marketing setup​

In parallel with the migration, Bright Horizons deployed Dynamics 365 Customer Insights – Data, which pulls information from multiple sources into unified customer profiles. The company says it now manages millions of profiles. Microsoft Learn describes Customer Insights – Data as Microsoft's customer data platform for unifying transactional, behavioral and demographic data.

CIO Ryan Scott said that with sales, service and marketing data in one place, the company can "start scoring relevance, understanding usage patterns, and driving next-best actions." Note the word "start." The concrete gain the story cites is better routing and prioritization for enrollment managers. Chief Digital and Transformation Officer Priya Krishnan said sales teams are beginning to build operational dashboards, while on the service side "it's early days."

Marketing is the most candid part of the story. Bright Horizons is rolling out Customer Insights – Journeys in phases, and Salesforce Marketing Cloud is still in use for top-of-funnel and some employer-driven B2B communications. Microsoft tools handle engagement after a consumer registers or expresses interest. Customer Insights helps build audiences even when the campaigns still go out through Salesforce. Many consumer-facing improvements, including the "segment-of-one" personalization Krishnan described, are explicitly still on the roadmap.

AI: the stated reason, but early in practice​

Executives said Microsoft's AI investment helped seal the decision. They also said the bigger draw was getting data and workflows into one place first. Krishnan said Microsoft felt like "the right organization to hitch our wagon to."

The actual AI work is labeled exploratory:

• Copilot with Outlook to draft replies to customer emails
• Copilot in Dynamics 365 Sales to support contact-center representatives
• Microsoft Copilot Studio to build agents for process automation

The story gives no production-scale figures, accuracy data or labor savings. Next steps include deeper Power Platform automation and more self-service.

The WindowsForum take​

The marketing pitch says AI made the choice. The more convincing explanation is that a working but rigid system was costing more effort with each change, and Microsoft offered a supported way to move the existing database instead of rebuilding it.

It's fair to ask about lock-in. Scott said that when the company evaluates a new capability, it first asks "what's the Microsoft solution we already have for this?" Fewer vendors and simpler integration are real benefits. That approach also concentrates negotiating leverage with one supplier, and the fact that Salesforce is still running shows a full consolidation isn't finished.

For admins still running Dynamics CRM on-premises, the main takeaway is that OP2OL is a well-documented route with known limits: the V9.0 minimum, licenses before migration, a point-in-time cutover, and no help from FastTrack with your custom code. Bright Horizons' 250-user, "business as usual" go-live is encouraging, but it's the company's own account. Run your own pilot before you take anyone's word for it.