---
title: "Microsoft Bridge to Cloud 3 (BTC3): Is the 30% Discount Worth It?"
slug: microsoft-bridge-to-cloud-3-btc3-is-the-30-discount-worth-it
date: 2026-06-15
author: Raaj
categories: [General]
excerpt: "Microsoft's BTC3 offers 30% off D365 licenses for 3 years. We break down eligibility, real savings math, what the discount doesn't cover, and the migration costs that actually determine ROI."
tldr: "BTC3 saves ~30% on D365 licensing for 3 years, but implementation and data migration costs run 3–10× the license savings. Use it if you were already planning to move — don't let it rush a decade-long platform decision."
canonical: https://clonepartner.com/blog/microsoft-bridge-to-cloud-3-btc3-is-the-30-discount-worth-it/
---

# Microsoft Bridge to Cloud 3 (BTC3): Is the 30% Discount Worth It?


**Bridge to Cloud 3 (BTC3)** is Microsoft's 30% licensing discount for on-premise Dynamics customers moving to Dynamics 365 online. It runs from January 1, 2026 through December 31, 2027, locks you into a non-cancellable 3-year term, and does not cover a single dollar of your actual migration work. Whether the discount is worth it depends on whether you were already planning to move — and whether you understand the costs it does not touch.

If you are running Dynamics GP, NAV, SL, or AX, your Microsoft partner has likely emailed you about this already. The pitch is simple: commit to migrating, and Microsoft discounts your cloud licenses by 30% for three years. For CFOs staring at end-of-support deadlines, the savings look compelling on a spreadsheet. But licensing is typically 15–20% of Total Cost of Ownership for a new ERP deployment. A discount on monthly seats does not offset a botched data migration or the structural data translation problems inherent in moving from a 20-year-old on-premise SQL database to a modern cloud architecture.

This guide breaks down the concrete math of BTC3, the strict eligibility requirements, and the hidden implementation and data migration costs that determine whether this promotion actually improves your business case.

For broader context on Microsoft's on-premise sunset timeline, see [The Ultimate 2026 Guide to Dynamics 365 On-Premise End of Life](https://clonepartner.com/blog/blog/dynamics-365-on-premise-end-of-life-2026-guide/).

## What Is the Microsoft Bridge to Cloud 3 (BTC3) Promotion?

**Bridge to Cloud 3** is a structured Microsoft promotion providing a **30% discount on Dynamics 365 online licenses** for existing on-premise Dynamics customers who commit to a fixed, non-cancellable 3-year cloud subscription through a Cloud Solution Provider (CSP) partner. ([simplanova.com](https://simplanova.com/wp-content/uploads/2025/09/Bridge-to-Cloud-3-Promo-Policy-and-FAQ.pdf))

The core terms:

- **Discount:** 30% off standard commercial list prices for most Dynamics 365 online products
- **Term:** Fixed 3-year commitment (triennial), non-cancellable
- **Enrollment window:** January 1, 2026 through December 31, 2027
- **Eligible source systems:** Dynamics GP, NAV, SL, AX, and on-premise CRM
- **Eligible destinations:** Business Central Essentials/Premium, Team Members, D365 Finance, Finance Premium, Supply Chain Management, Human Resources, Project Operations, Commerce, and others
- **Billing frequency:** Monthly, annual, or triennial — the discount applies regardless of billing cadence

BTC3 is the third iteration of this program. BTC2 offered a 40% discount and expired December 31, 2025. The shrinking discount reflects Microsoft's increasing confidence that on-premise customers have fewer alternatives as end-of-life dates approach.

BTC3 is a commercial contract, not a technical migration plan. Signing it secures your pricing, but it obligates your organization to execute the transition. After the 3-year term, your subscription reverts to standard undiscounted pricing.

> [!NOTE]
> **BTC3 is not available to previous BTC1 or BTC2 participants.** Organizations that enrolled in a prior Bridge to Cloud promotion are generally ineligible. There is a narrow exception: if your peak number of paid Dynamics 365 online full users to date does not exceed 10% of the users you would license at BTC3 enrollment. ([simplanova.com](https://simplanova.com/wp-content/uploads/2025/09/Bridge-to-Cloud-3-Promo-Policy-and-FAQ.pdf))

## BTC3 Eligibility: Do You Qualify for the Discount?

The eligibility criteria are strict and non-negotiable:

1. **On-premise license purchase date:** Your Dynamics perpetual licenses (GP, NAV, SL, or AX) must have been purchased **before September 1, 2024**. ([simplanova.com](https://simplanova.com/wp-content/uploads/2025/09/Bridge-to-Cloud-3-Promo-Policy-and-FAQ.pdf))
2. **Active Enhancement Plan (EP):** Your EP, Advantage Plan, or Advantage Plus Plan must be active at enrollment. There is a 30-day grace period for recently lapsed plans. Customers with older lapses must pay back-dated EP fees (capped at three years) to re-enter eligibility. ([simplanova.com](https://simplanova.com/wp-content/uploads/2025/09/Bridge-to-Cloud-3-Promo-Policy-and-FAQ.pdf))
3. **Minimum CSP value:** The annualized value of your new Dynamics 365 cloud licenses must **equal or exceed** your current annual Enhancement Plan renewal amount. This is calculated on the CSP list price of the 3-year subscriptions with annual billing. You must maintain this minimum throughout the promo term. ([simplanova.com](https://simplanova.com/wp-content/uploads/2025/09/Bridge-to-Cloud-3-Promo-Policy-and-FAQ.pdf))
4. **Partner-led CSP/NCE:** The cloud purchase must be through a partner-led CSP New Commerce Experience channel on a triennial term. ([simplanova.com](https://simplanova.com/wp-content/uploads/2025/09/Bridge-to-Cloud-3-Promo-Policy-and-FAQ.pdf))
5. **No prior Bridge participation:** Organizations that used BTC1 or BTC2 are excluded (subject to the 10% exception above). ([simplanova.com](https://simplanova.com/wp-content/uploads/2025/09/Bridge-to-Cloud-3-Promo-Policy-and-FAQ.pdf))

That annualized CSP rule matters more than most partners acknowledge. BTC3 is not just 30% off whatever small cloud bundle you want to buy. Your discounted cloud subscription still has to clear a floor based on your on-prem support spend. For some companies, that changes the seat mix or whether the economics work at all.

If any of these conditions are not met, the promotion is off the table. Your CSP partner can verify eligibility, but do not assume qualification — check the EP purchase date and lapse history carefully.

> [!WARNING]
> **Watch your EP anniversary date.** Microsoft recommends enrolling on or before your EP renewal date, with only a 30-day grace period, to avoid paying another year of EP. If you already renewed, there is no refund for the unused portion. ([simplanova.com](https://simplanova.com/wp-content/uploads/2025/09/Bridge-to-Cloud-3-Promo-Policy-and-FAQ.pdf))

> [!NOTE]
> **Commercial eligibility is not technical readiness.** Microsoft's built-in Business Central cloud migration path supports **GP 2015+** and **SL 2015+** on **SQL Server 2016+** with **compatibility level 130+**. If you are on NAV, Microsoft requires that you first upgrade to **Business Central on-premises version 14 or later** and convert customizations to extensions before switching online. If you are running an older GP version, you may need to upgrade GP before you can use the standard cloud migration path — adding time and cost. ([learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/faq-migrate-data))

If you are unsure whether your business complexity warrants Business Central or the enterprise-grade Finance & Operations suite, review [Dynamics 365 Business Central vs F&O: The 2026 ERP Decision Guide](https://clonepartner.com/blog/blog/dynamics-365-business-central-vs-fo-the-2026-erp-decision-guide/) before signing a 3-year commitment.

## The Concrete Math: How Much Does BTC3 Actually Save?

The savings formula is straightforward: take the qualifying cloud license bill and reduce it by 30% for 36 months.

Using current 2026 US list pricing for **Dynamics 365 Business Central** — the most common BTC3 destination for GP and NAV customers ([microsoft.com](https://www.microsoft.com/en-us/dynamics-365/products/business-central/pricing)):

| License Tier | Standard Price | BTC3 Price (30% off) | Monthly Savings per User |
|---|---|---|---|
| **Essentials** | $80/user/month | $56/user/month | $24 |
| **Premium** | $110/user/month | $77/user/month | $33 |
| **Team Members** | $8/user/month | $5.60/user/month | $2.40 |

For Finance & Operations customers, the numbers are larger: **D365 Finance** lists at approximately **$210/user/month** ($147 under BTC3) and **Finance Premium** at **$300/user/month** ($210 under BTC3). ([microsoft.com](https://www.microsoft.com/en-us/dynamics-365/products/business-central/pricing))

### Scenario: A Typical GP Shop with 15 Essentials Users + 5 Team Members

| | Standard (monthly) | BTC3 (monthly) | Monthly Savings |
|---|---|---|---|
| 15 × Essentials | $1,200 | $840 | $360 |
| 5 × Team Members | $40 | $28 | $12 |
| **Total** | **$1,240** | **$868** | **$372** |

- **Annual licensing savings:** $4,464
- **3-year licensing savings:** $13,392

At larger scale:

- **25 Business Central Essentials users:** $600/month saved, **$21,600 over 36 months**
- **10 Business Central Premium users:** $330/month saved, **$11,880 over 36 months**
- **20 Dynamics 365 Finance users:** $1,260/month saved, **$45,360 over 36 months**

### Enhancement Plan Fee Waiver

The licensing discount is only half the financial equation. During the BTC3 term, Microsoft extends your on-premise Enhancement Plan at no additional cost. This waiver can be a larger benefit than the license discount itself.

GP Enhancement Plan rates have climbed from roughly 16% of Protected List Price in 2021 to 20% in 2026. On a $3,000/user GP license, that is $600/user/year you stop paying. For a 15-user scenario, that adds roughly **$9,000/year** in EP cost avoidance.

Combined, our 15-user example saves approximately **$13,400 in licensing** plus up to **$27,000 in waived EP fees** over the 3-year term — about **$40,000 in total software cost reduction**. From a pure procurement standpoint, the math is compelling.

Hold that number. We are about to compare it against the costs BTC3 does not touch.

## What BTC3 Does Not Cover: The Implementation Gap

This is where most BTC3 conversations go wrong. Partners lead with the 30% number. CFOs budget for the licensing delta. Nobody budgets for the other 60–80% of the actual project cost.

**BTC3 covers licensing. Period.** It does not cover:

- **Data extraction and migration** — moving GL history, AP/AR transactions, inventory, open orders, and custom ISV data from GP/NAV to Business Central
- **Implementation and configuration** — setting up Business Central, mapping workflows, configuring approval chains, rebuilding reports
- **Customization and ISV replacement** — replacing GP add-ons (Mekorma, Binary Stream, SalesPad, Nolan Business Solutions) with BC-native or AppSource equivalents
- **Training and change management** — retraining accounting staff, warehouse users, and operations teams on a fundamentally different interface
- **Integration rebuilds** — reconnecting EDI, ecommerce, CRM, and third-party systems to Business Central's API layer

Industry estimates for a standard Business Central implementation range from **$40,000 to $100,000+** depending on complexity, user count, and customization requirements. Complex implementations with multi-entity structures, heavy customizations, or significant integration work regularly exceed $150,000.

For reference, Forrester's Total Economic Impact study of a composite Business Central migration modeled **$82,000** in three-year Microsoft subscription fees versus **$118,000** in implementation, ongoing management, and training personnel costs — including a $45,000 partner fee, two internal FTEs spending 25% of their time over four months, and 15 hours of training per user. ([tei.forrester.com](https://tei.forrester.com/go/microsoft/Dynamics365BusinessCentral/docs/TheTEIOfAMigrationToMicrosoftDynamics365BusinessCentral.pdf))

Compare that to our 15-user BTC3 licensing savings of $13,392 over three years. The implementation cost can be **3–10× the licensing savings**.

A realistic budget framework for a 15-user GP-to-BC migration with BTC3:

| Cost Category | Estimated Range |
|---|---|
| D365 BC licensing (3 years, BTC3) | ~$31,000 |
| Implementation & configuration | $50,000–$120,000 |
| Data migration (historical GL, AP, AR, inventory) | $15,000–$40,000 |
| ISV replacement / AppSource add-ons | $5,000–$25,000 |
| Training & change management | $5,000–$15,000 |
| **Total 3-year cost** | **$106,000–$231,000** |

The BTC3 licensing savings of ~$13,400 over three years represents roughly **6–13%** of the total project cost. It helps. It is not the deciding factor.

> [!WARNING]
> **The "Lift and Shift" Trap.** Standard VARs often bundle the BTC3 discount with a cheap implementation package. They keep costs low by refusing to migrate historical data, offering only "opening balances" and master records. This leaves your finance team cut off from years of paid vendor invoices and reconciled bank lines. A 30% discount means nothing if your team cannot drill into last year's AP activity on day one.

> [!NOTE]
> **BTC3 and the Business Central Migration Voucher cannot be combined.** Microsoft offers a separate Migration Voucher that can help cover implementation costs for eligible on-prem-to-Business Central projects, but the policy explicitly states that BTC3 and the voucher cannot be used together. Price both paths before you commit. ([microsoftpartners.microsoft.com](https://microsoftpartners.microsoft.com/abs/Blog/?title=Business+Central+Migration%3A+Everything+you+need+to+know&utm_source=openai))

For a deeper breakdown of what drives ERP migration costs beyond licensing, see [The 2026 Dynamics 365 Migration Handbook: Tools, Costs, and Step-by-Step Roadmap](https://clonepartner.com/blog/blog/dynamics-365-cloud-migration-tools-costs-2026/).

## Dual Access Rights: Running On-Prem and Cloud in Parallel

One of BTC3's most underappreciated features is **Dual Access Rights**. During the promotional term, you maintain the right to continue using, expanding, and upgrading your legacy on-premise system alongside your new Dynamics 365 cloud deployment.

This eliminates the forced "hard cutover" — the single most dangerous moment in any ERP migration. With dual access:

- Your accounting team keeps closing months in GP while Business Central is being configured
- You can run parallel processing to validate that BC produces the same financial outputs
- You can migrate in phases — master data first, then open transactions, then historical data — without disrupting daily operations
- There is no artificial go-live deadline driven by licensing expiration

Microsoft also provides a **50% discount on additional on-premise user licenses** during the migration period (available until December 31, 2027), which helps businesses adding headcount during the transition. For GP and NAV customers migrating from concurrent-user licensing to Business Central's named-user model, Microsoft offers **additional "$0 users"** for up to two years when the annualized CSP value exceeds a threshold tied to EP cost.

**A practical caveat:** Microsoft's policy states that long-term on-prem use through Dual Use Rights is **not intended or recommended**, and cloud users licensed through BTC3 cannot be merged into the existing on-prem user pool. BTC3 buys transition time. It is not a permanent hybrid licensing model. ([simplanova.com](https://simplanova.com/wp-content/uploads/2025/09/Bridge-to-Cloud-3-Promo-Policy-and-FAQ.pdf))

During GP cloud migration specifically, Microsoft's documentation notes that the **on-premises solution remains the operative environment** until migration is complete. Once replication is underway, the Business Central online environment is largely **read-only** for non-SUPER users, and online changes can be overwritten by later replication runs. That is precisely why a planned parallel phase matters: it gives finance and ops teams time to test, reconcile, and train without a risky single-weekend cutover. ([learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-gp-overview))

This parallel-running model is how ERP migrations should work. The question is whether your migration partner can execute it — keeping both systems in sync, reconciled, and audit-ready throughout the transition.

## GP to Business Central Data Migration: Where Standard Tools Break

BTC3 gets you the licenses. It does not move your data.

Microsoft provides a **cloud migration tool** specifically for Dynamics GP. It works within narrow constraints. Here is what it actually does — and where it stops.

### The Dimension Mapping Problem

Dynamics GP uses a **segmented Chart of Accounts**. A typical account string looks like `01-5000-00` (Department – Main Account – Subaccount). Dynamics 365 Business Central does not use segments; it uses a **dimensional model**. You have a Main Account, and everything else is tagged with Dimensions (Department, Cost Center, Region).

Microsoft's migration tool handles this by mapping the **main account segment** from GP to the Business Central account number. You choose which two remaining GP segments become Global Dimension 1 and Global Dimension 2. The rest are automatically set up as **shortcut dimensions 3 through 8**. ([learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-dynamics-gp))

This rigid logic breaks complex financial reporting. If your GP instance uses 4+ segments with complex segment-to-department-to-project relationships, the automatic dimension mapping will destroy your historical reporting hierarchy. The tool has no concept of how your CFO actually reads the financials — it just dumps segments into shortcut slots.

If you need to consolidate, split, or rename segments during the move, the standard tool cannot handle it.

### Historical Data Lands in Extension Tables

The migration tool can bring over GL detail, receivables, payables, sales order processing, purchase order receipts, and inventory transactions — but it migrates them into **GP Historical Snapshot extension tables** in Business Central, not native BC tables. This data is accessible via Power BI or Power Apps for reporting and external analysis, but it does not behave like native Business Central transactions. ([learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-dynamics-gp))

For finance teams that expect deep in-app drill-back on historical activity, this is a critical limitation. Open receivables and payables are recreated based on the **remaining balance**, but the full transactional detail behind them lives in a separate reporting layer.

GP fiscal periods come over as accounting periods. Historical years from GP arrive as open years that must be manually closed in Business Central.

### Edge Cases the Standard Tool Misses

- **GP version requirement:** The cloud migration tool requires **GP 2015 or newer** on **SQL Server 2016+** with **compatibility level 130+**. If you are running an older version, you need to upgrade GP first — adding time and cost. ([learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/faq-migrate-data))
- **Unit of Measure Schedules** in GP do not have a direct equivalent in Business Central. ([learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-dynamics-gp))
- **Posted cash receipts that were not deposited before migration are not migrated.** ([learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-dynamics-gp))
- **Data cleanliness assumptions:** The tool assumes clean master data. Inactive vendors, orphaned customer records, and duplicate items all migrate unless you clean them first.
- **Custom ISV table data:** Third-party tables from add-ons like Mekorma checks, Binary Stream multi-entity, or SalesPad are completely ignored. This data either stays behind or requires custom extraction.

If internal IT teams try to solve the custom data problem by building SSIS packages or using tools like KingswaySoft, they quickly drown in the complexity of Business Central's API rate limits and relational dependencies. Moving a custom table is not just copying rows; it requires maintaining exact primary/foreign key relationships so that historical invoices still tie back to the correct customer ledger entries.

### NAV Customers Face a Different Version of the Same Problem

NAV customers cannot migrate directly to Business Central online. Microsoft requires upgrading to **Business Central on-premises version 14 or later**, converting application customizations to **extensions**, and then migrating to the cloud. Data from tables with code customizations in NAV cannot be carried forward as-is. ([learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-nav))

Microsoft's cloud migration pipeline uses **Azure Data Factory** with a **self-hosted integration runtime**, and the GP tooling includes validation for entities like G/L accounts, customers, vendors, items, purchase orders, and vendor 1099 data. These are useful guardrails, but they do not replace target-state design, custom mapping, or decisions about what history needs to live natively in Business Central versus an archive or reporting layer. ([learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/faq-migrate-data))

For GP customers facing these data layer challenges, see [Dynamics GP to Business Central: Migrating 20 Years of History](https://clonepartner.com/blog/blog/dynamics-gp-to-business-central-migrating-20-years-of-history/). For NAV customers, see [Dynamics NAV 2016 End of Support and the Future of F&O](https://clonepartner.com/blog/blog/dynamics-nav-2016-end-of-support-business-central-migration/).

### How ClonePartner Solves the Data Layer

At ClonePartner, we treat ERP data migration as an engineering discipline, not an afterthought. We bypass the limitations of standard tools:

- **Custom Dimension Mapping:** We extract your legacy GP/NAV segments and map them exactly how your CFO wants them in Business Central — not how a generic script dictates.
- **Full Historical Context:** We do not stop at opening balances. We migrate full GL detail, AP/AR history, and custom ISV tables, ensuring complete audit compliance and in-app drill-back.
- **Zero Downtime:** Leveraging BTC3's Dual Access Rights, we stream your data into the cloud while your on-premise system remains live, with no operational disruption.

We work alongside your implementation partner. They configure Business Central. We handle the data extraction, transformation, rehearsal, and rollback planning.

## The 3-Year Lock-In: What Happens After BTC3 Ends?

The 30% discount is fixed for three years. After the term expires, your subscription reverts to **standard, undiscounted Microsoft pricing**.

What that means in practice:

- If you enroll in January 2026, your discounted pricing ends January 2029
- Your monthly cost jumps by roughly **43% overnight** (from 70% of list back to 100% of list)
- There is no guarantee of a BTC4 — and each iteration has offered a smaller discount (BTC2 was 40%, BTC3 is 30%)
- Microsoft has been raising Business Central list prices (Essentials went from $70 to $80/user/month in November 2025) and may raise them again during or after your BTC3 term

Factor the post-BTC3 price jump into your **5-year and 10-year TCO models**. The discount makes years 1–3 look attractive, but your steady-state cost will be at full list price — or higher, if Microsoft raises prices during that window. Budget accordingly.

## The Decision Matrix: When BTC3 Is (and Isn't) Worth It

The BTC3 enrollment window closes December 31, 2027. Given that a proper ERP migration takes 6–18 months to plan, map, test, and execute, organizations need to initiate their projects in 2026 to safely meet the deadline.

**BTC3 is worth it if:**

- You were already planning a Dynamics 365 migration and the timeline aligns with the enrollment window
- You have validated that Business Central (or D365 Finance/SCM for AX customers) is the right platform — not just the discounted one
- Your implementation partner has scoped the full project cost, and the licensing savings meaningfully reduce your total investment
- Your historical data, integrations, and customization scope are understood — not a black box
- You can realistically start the migration in 2026 and go live within the BTC3 term to capture the full benefit of dual access

**BTC3 is probably not worth it if:**

- The 30% discount is the primary reason you are considering Dynamics 365 — do not let a 3-year promotion dictate a decade-long platform choice
- You have not determined whether Business Central or D365 Finance & Operations is the right fit (see [Business Central vs F&O: The 2026 ERP Decision Guide](https://clonepartner.com/blog/blog/dynamics-365-business-central-vs-fo-the-2026-erp-decision-guide/))
- Your GP or NAV system has extensive customizations, ISV add-ons, or complex multi-entity structures that need 12+ months of discovery before you can begin migration
- The discount makes the license line work, but you still have no budget for execution or training
- You are planning to wait until late 2027 to start

> [!TIP]
> **Timeline reality check:** Most GP-to-BC migrations take 6–18 months from kickoff to go-live. Companies that want to enroll in BTC3 and actually use the system during the promotional term need to **start planning in 2026** — not 2027. The enrollment deadline is December 31, 2027, but the migration itself does not happen overnight.

## Use BTC3 as an Accelerator, Not a Justification

The smartest way to use BTC3 is to treat the licensing savings as a contribution toward your migration cost — not as the reason to migrate.

If you were already heading to Dynamics 365, BTC3 improves the business case. If the discount is the only reason the project looks attractive, you probably have not modeled the real cost yet. A three-year promo should not choose a ten-year ERP for you.

Look beyond the licensing. Secure your data strategy first.

> Planning a GP or NAV migration and want to understand your data migration scope before committing to BTC3? ClonePartner can assess your historical data complexity, map your Chart of Accounts to Business Central dimensions, and give you a fixed-cost migration estimate — so you know the full picture before you sign a 3-year contract.
>
> [Talk to us](https://cal.com/clonepartner/meet?duration=30)

## Frequently asked questions

### What is Bridge to Cloud 3?

Bridge to Cloud 3 (BTC3) is a Microsoft promotion offering existing Dynamics on-premise customers (GP, NAV, SL, AX) a 30% discount on Dynamics 365 online licenses for a fixed, non-cancellable 3-year term through a CSP partner. The enrollment window runs from January 1, 2026 through December 31, 2027.

### How much does BTC3 save?

Savings depend on user count and license tier. A 15-user Business Central Essentials deployment saves roughly $4,464/year or $13,392 over 3 years on licensing alone. Waived Enhancement Plan fees during the term can add significant further savings. However, implementation and data migration costs — which BTC3 does not cover — typically run 3–10× the licensing savings.

### When does BTC3 expire?

The enrollment window closes December 31, 2027. Once enrolled, the 30% discount lasts for your full 3-year term. After the term ends, subscriptions revert to standard undiscounted Microsoft pricing. Because ERP migrations take 6–18 months, companies should start planning in 2026.

### Can I use BTC3 for D365 Finance?

Yes. BTC3 applies to most Dynamics 365 online products, including D365 Finance, Finance Premium, and Supply Chain Management. AX customers migrating to the cloud version of their ERP qualify under the same eligibility rules as GP or NAV customers moving to Business Central.

### Does BTC3 cover implementation or data migration?

No. BTC3 is strictly a license promotion. Implementation, data migration, custom development, ISV replacement, training, and change management are separate costs. BTC3 also cannot be combined with Microsoft's Business Central Migration Voucher.