New: Odoo and Dynamics 365 cost calculators.Estimate your costs

ERP support models, pricing, and what to put in the SLA

ERP support keeps a live Dynamics 365 or Odoo system usable after go-live. Vendor plans cover break-fix on the standard product.

FlecticUpdated 30 min read

ERP support keeps a live Dynamics 365 or Odoo system usable after go-live. Vendor plans cover break-fix on the standard product. Configuration, training, custom code, integrations, and data repair are a partner cost on top of the subscription. As of October 2026, Professional Direct lists at USD 9 per user per month in the United States and CAD 12.20 in Canada, paid yearly, minimum 20 users, and it excludes Business Central. A paid Microsoft plan does not replace that partner.

The same split shows up on Odoo. Standard and Custom plans include unlimited email support on standard features, and they exclude implementation and maintenance of custom code. For a company of about 20 to 100 people, the buying decision is which partner model sits beside the vendor plan (block hours, a monthly retainer, a managed service, or an in-house admin who escalates), and which severity, hours, and exit terms you write down before you sign.

What ERP support includes after go-live

ERP support is the operating work that starts when transactions carry live money: someone answers users, someone fixes defects in the product, and someone changes configuration when the process was wrong. Those three jobs are easy to buy as one line called post-go-live support. They are not the same contract.

Vendor support, from Microsoft or from Odoo, is the product layer. Microsoft defines Business Central technical support as break-fix. On Business Central, how-to questions and advisory training are outside the support plans. If the cause is custom code, partner or ISV software, or anything outside core Microsoft code, Microsoft provides evidence and the customer or partner continues the investigation. Microsoft also does not correct damaged Business Central data, and states it has no legal obligation under the SPLA to change or correct data corrupted because of malfunctioning software. Odoo's Enterprise terms commit Odoo to start handling bug submissions within 2 business days. Unlimited free tickets cover bugs and guidance on standard features and Covered Extra Modules. Development and customization questions need a separate service agreement.

Partner support, or a managed service you staff yourself, is the application layer. It is who fixes a posting setup, retrains a buyer, repairs an integration file, and quotes the work when a module you own breaks after an upgrade. Microsoft's own support page asks, "Does having a paid support plan replace partner support?" The page answers that a paid plan does not replace it. Odoo's pricing FAQ puts the same boundary in one line: "What's not included in these plans: implementation service and maintenance of custom code".

If you remember one test, use this. A ticket that would still exist on a clean, unmodified install of the product can go to the vendor. A ticket that exists because of your chart of accounts, your warehouse rules, your connector, or a module someone wrote for you belongs on the partner scope, with a price and a definition of done.

What Microsoft charges, and what it still leaves open

As of October 2026, Dynamics 365 has three support offers on the public page. Standard is included with a Dynamics 365 purchase and is technical break-fix. Professional Direct is the paid per-user plan. Unified Enterprise is a custom quote with no public list price in the United States or Canada. Microsoft describes Standard as "Best for businesses operating a simple environment or using a full-service partner". The included plan still assumes someone else owns the application.

  • Standard (United States, as of October 2026: Included (USD 0) · Canada, as of October 2026: Included · What it is: Technical break-fix with the subscription)
  • Professional Direct (United States, as of October 2026: USD 9 per user per month, paid yearly, minimum 20 users · Canada, as of October 2026: CAD 12.20 per user per month, paid yearly, minimum 20 users · What it is: Faster initial response and advisory hours. Does not cover Business Central)
  • Unified Enterprise (United States, as of October 2026: Custom quote · Canada, as of October 2026: Custom quote · What it is: Paid plan. No public list price)

Sources for the rows: Dynamics 365 support, United States and Dynamics 365 support, Canada. The Canada page does not add a separate tax line on the CAD 12.20 figure.

Only the paid plans, Professional Direct and Unified, include advisory support. Standard stays technical break-fix. Opening a request requires an active plan: Subscription (Standard), Professional Direct, or Unified, as Microsoft documents for the Power Platform admin center.

A 25-user check on Professional Direct

Assume 25 users on Dynamics 365 apps that Professional Direct covers, all of them counted toward the plan, paid yearly. The minimum is 20 users, so 25 qualifies. At USD 9 per user per month the list is USD 225 per month, or USD 2,700 for the year. At the Canada list of CAD 12.20 the same headcount is CAD 305 per month, or CAD 3,660 for the year, before any tax your invoice adds. That spend buys Microsoft response targets and, on the paid plans, advisory time. It does not buy configuration, training, custom code, or a person who will repair your data. And if those 25 people are Business Central users, the line does not apply at all: Professional Direct does not cover Business Central.

License price is a different bill, and mixing the two is how budgets go quiet. Business Central Essentials lists at USD 80 per user per month in the United States and CAD 108.50 in Canada, Premium at USD 110 and CAD 149.20, Team Members at USD 8 and CAD 10.90. All are per user per month, paid yearly. Canada prices are plus applicable tax. Assume 8 Essentials users and 17 Team Members. United States licenses are 8 times USD 80 plus 17 times USD 8, which is USD 640 plus USD 136, or USD 776 per month. Canada licenses on the same mix are 8 times CAD 108.50 plus 17 times CAD 10.90, which is CAD 868 plus CAD 185.30, or CAD 1,053.30 per month plus tax. None of that CAD or USD figure is a support retainer. Ask each bidder to price hypercare, monthly support, and custom-code care as separate lines from these licenses.

Business Central: your admin cannot open the Microsoft case

For Business Central online, the reselling partner is the front line of technical support. The internal administrator cannot contact Microsoft directly and must contact the partner. Microsoft's support page says it in buyer language: "Business Central customers should contact their reselling partner to get help with technical problems". To submit a case to Microsoft on your behalf, the partner must be a delegated admin, and the partner company must have an Advanced or Premier support plan.

Put that path in the contract. If your contract ends and delegated admin is still in place, the old partner remains on the path to Microsoft. If you cancel a paid subscription, you contact the reselling partner, and the partner cancels it in Partner Center. An internal administrator can remove a trial subscription directly. The steps live in Microsoft's tenant administration guide.

Initial response on other Dynamics 365 apps

For Power Platform and Dynamics 365 apps, Microsoft publishes initial response, which is the first engagement, not a promise that the process is fixed. As of October 2026, Standard is under 1 hour for Severity A, under 4 hours for Severity B, and under 8 hours for Severity C. Professional Direct and Unified are under 1 hour, under 2 hours, and under 4 hours for A, B, and C. Severity A requires the customer to stay engaged 24x7 until resolution, or Microsoft may drop the severity.

In North America, business hours for this model are 6:00 AM to 6:00 PM Pacific time, Monday to Friday, excluding holidays. Severity A and B coverage at all hours is in English. French and Spanish support runs during local business hours. A team in Toronto or Chicago that needs French or Spanish at 9:00 PM local time is outside that window even when English Severity A coverage is open.

There is a hard stop on effort. Microsoft Dynamics support invests up to four hours on a break-fix case for performance issues, or for issues that cannot be reproduced on a standard unmodified install. If the case is still open, Microsoft closes the incident and points the customer to a partner or to community forums. Premier and Unified customers may continue as an advisory case. Technical support does not produce a root-cause analysis. Budget the partner for anything that will not reproduce on a clean install, and for any write-up your auditor will ask to see.

Microsoft's name for the weeks after go-live is not a support SKU. In Success by Design, Prepare includes the support model, the cutover plan, and go/no-go criteria. Operate is stabilization after go-live, then enhancements. The support model is supposed to exist before the switch is thrown.

What Odoo support includes, and what a Success Pack buys

As of October 2026, Odoo Standard shows a discounted first-year list of USD 31.10 per user per month, with USD 38.90 as the undiscounted comparison. Custom shows USD 61.00 against USD 76.20. The discount is valid for 12 months for the initial users ordered. A Light User lists at USD 8.90, with the price confirmed by an Odoo advisor. These are subscription prices in USD on Odoo's pricing page. They include vendor email support. They are not a partner hour balance. Odoo.sh hosting is not included on the Custom plan. The same page says plans include unlimited email support Monday to Friday, 24/5, in English, French, Spanish, or Dutch, plus free eLearning and upgrades.

Assume 25 users on Standard at the discounted USD 31.10. The subscription list is USD 777.50 per month for those initial users during the discount window. At the undiscounted USD 38.90 comparison, the same 25 users are USD 972.50 per month. Either figure includes the vendor mailbox. It does not include a consultant sitting with your warehouse lead, and it does not include maintenance of extra modules. If you buy in Canada, have the subscription and any Success Pack written in CAD on the order before you compare them with a partner quote in CAD.

Odoo describes companies under 50 employees as usually buying Success Packs from Odoo, and companies over 50 employees as usually using a partner. The public hour bundles, for returning customers, are on the Success Packs page:

  • Starter (Hours: 4 · Returning customer: USD 580 · First pack for a new customer (15 percent off, once): USD 493)
  • Basic (Hours: 25 · Returning customer: USD 3,600 · First pack for a new customer (15 percent off, once): USD 3,060)
  • Standard (Hours: 50 · Returning customer: USD 7,000 · First pack for a new customer (15 percent off, once): USD 5,950)
  • Custom (Hours: 100 · Returning customer: USD 12,500 · First pack for a new customer (15 percent off, once): USD 10,625)
  • Pro (Hours: 200 · Returning customer: USD 25,000 · First pack for a new customer (15 percent off, once): USD 21,250)

Travel time and expenses are extra. Extra monthly charges apply for maintenance of extra modules or lines of code. Performance work requires a pack of at least 50 hours, so a Starter or Basic pack cannot be the vehicle for that work. Dividing the returning-customer price by the hours gives USD 145 for Starter, USD 144 for Basic, USD 140 for Standard, and USD 125 for Custom and for Pro. Those rates are the pack price divided by the hours in the pack. A monthly retainer is a separate quote from a bidder. Odoo says 80 percent of projects in the estimator's example scope go to production in 200 hours or less, and cites a 98 percent implementation success rate with a Success Pack versus 65 percent without. Both figures are Odoo's own, on that packs page, and they describe implementation of an example scope. Year-two support is a separate quote.

The Odoo FAQ asks, "Where can I get implementation services, and how much does it cost?" The practical answer for a firm over 50 people is a partner statement of work, because the packs exclude the ongoing care of custom code. Our Odoo support note goes further on what to ask that partner to own. For the rollout around it, see how an Odoo implementation is phased.

Uptime, backups, and the maintenance line that is not on the price page

Odoo's Cloud SLA sets a 99.9 percent monthly uptime target, which Odoo equates to a maximum of 45 minutes of unplanned downtime per month, excluding planned maintenance. Odoo states these uptime and recovery objectives are not legally binding commitments. Planned maintenance is typically less than 1 hour, outside regional business hours, about once every couple of months. Read that as a hosting target for Odoo Cloud, then put your own process targets (can you ship, can you invoice) in the partner SLA.

Backups, as of October 2026 on the Cloud SLA: 14 full backups kept at least 3 months, daily for 7 days, weekly for 4 weeks, monthly for 3 or more months, replicated to at least 3 machines in Europe and Canada, plus an immutable cold copy. Customers cannot choose or restrict backup regions. Single-server disaster objectives are an RPO of 24 hours (near zero for Odoo SaaS) and an RTO of 6 hours. Full data-center disaster objectives are an RPO of 24 hours and an RTO of 24 hours. If a 24-hour data loss on a bad day is too much for your order book, say so in the contract and ask what the partner will do inside that window. The platform objective will not shrink because the SLA hoped it would.

Covered Extra Module maintenance is a monthly fee per 100 lines of code, counted with cloc, and the rate is set in the customer's order, not on the public pricing page. If a module lacked maintenance for the prior 12 months, Odoo may charge a one-time fee for each missing month at upgrade. Renewal charges can rise by up to 7 percent per year of the previous term if the prior price is below current list. Ask for the per-100-line rate and the renewal cap as numbers on the order, in the currency you pay.

How long ERP hypercare should last

Hypercare is the short period after a major operational change when support for users is heavier than it will be later. Wiktionary defines it as a period after a major operational change during which an especially intensive effort supports users through the transition. Salesforce, writing for service leaders, says hypercare typically lasts one to four weeks and should end when case volume and system performance stabilize. A date on the calendar is only a backstop. Supportbench, a help-desk vendor, describes hypercare as usually 2 to 6 weeks and says complex ERP-style implementations can justify 8 to 12 weeks. Those ranges are publisher guidance. Microsoft and Odoo publish a different clock: Prepare and Operate on the Microsoft side, and a 2-business-day start on Odoo bugs. Use the publisher ranges to set a planning band, then exit on measurements you agreed before go-live.

For a 20 to 100 person distributor or light manufacturer, a useful planning band is 2 to 6 weeks of named coverage, with room to extend toward the longer ERP-style window if cutover includes several sites, a messy item master, or a close that cannot slip. Microsoft's Operate phase is the same window under a different name: stabilization first, enhancements after. The support roster belongs in Prepare, next to the cutover plan and the go/no-go call.

What the hypercare roster does each day

Staff it as a short command cycle with a named owner on every ticket. Four seats cover a company this size if the names are real and the hours are blocked:

  1. An incident lead triages what users log, assigns a severity from the business impact, and is the only person who talks to the vendor when a product defect is in play.
  2. A functional lead reproduces the issue on a transaction, decides whether it is training, configuration, data, or code, and either fixes it or writes the change request.
  3. An adoption lead runs office hours for the roles that went live (order entry, receiving, accounts payable) and turns repeat questions into a one-page correction the next user can follow.
  4. An executive sponsor reads a daily note: open criticals, orders or invoices blocked, and whether exit criteria moved. That person can stop a workaround from becoming the new process.

Name those four seats in the statement of work. Supportbench's hypercare page is where teams go looking when the owner was never picked. On Business Central, the incident lead's path to Microsoft runs through the partner, so the partner's delegated admin has to be awake in the same window. On Odoo, bugs in standard features can go to Odoo under the 2-business-day start, and anything in your modules stays on the pack or the partner.

The ERP hypercare guide covers the first phase on its own. This page is the handoff from that phase into a model you can afford in month four.

Exit criteria you can score

Salesforce's point is the right one: end when volume and performance settle. The calendar date is only a backstop. Supportbench publishes a stricter template and labels it as that vendor's editorial default: hold the exit criteria for five consecutive business days, with volume at or below 120 percent of the projected baseline, no open severity-1 items, and customer sign-off. Treat the 120 percent and the five-day hold as a starting proposal you can write into the contract. Add two checks that match ERP work:

  • A defined close task has completed once on the new system (a bank rec, a receiving put-away, or a customer invoice run) without a spreadsheet beside it.
  • No severity-1 item is being carried by a named hero who will go on leave next week. The workaround is either retired or written into the steady-state runbook with an owner.

If those are green, step down. Staying on hypercare rates after the criteria are met is how a six-week spike becomes a vague retainer. The build phase comes before this support window, and Flectic's written proposal sets its timeline and fixed price before work starts. Hypercare still ends when the exit test is met.

"What are the most common metrics used to track hypercare success?" Volume against the baseline you projected, open criticals, and time to first response are the three worth a daily line. A fourth, time to a workaround that unblocks cash or shipping, matters more than a cosmetic fix on a report header. Publish the baseline before go-live. A baseline written on day ten will follow the backlog you already have.

Four ways to buy the partner layer

Microsoft and Odoo price pages do not list a monthly retainer for application support. The only published hour bundles are the Odoo Success Packs above. Every other dollar figure should arrive as a line from the bidder. The shapes, though, are stable, and they fit different sizes.

Block hours, or time and materials against a pack. You buy a balance, burn it on fixes and small changes, and stop when it is gone. Odoo's packs are the clear public version: 4, 25, 50, 100, or 200 hours, with performance work starting at 50. This fits a company under 50 employees, which is the segment Odoo itself points at Success Packs, or a larger team with a quiet system and a list of small changes. The failure mode is a go-live week that eats the pack, after which how-to questions have no funded home. If you use a pack for hypercare, buy the hypercare hours as their own pack and keep a second balance for the quarter after exit.

Monthly retainer. You pay a fixed fee for a named scope: a baseline of hours, a person who already knows the database, release checks, and a severity-1 path. Demand has to be steady enough that a quiet month and a heavy month both feel fair. The contract has to say what is inside the fee and what is a project. A retainer that uses one vague label, then argues about a two-day pricing change, will disappoint both sides. For 20 to 100 people with one entity, a retainer plus a written overflow rate is usually the cleanest steady state once hypercare has exited.

Managed service. The partner runs monitoring, incident handling above your internal desk, release management, and a small enhancement queue. You still own the business rules and the data. This is the model when you do not have a second analyst to hire, and when Business Central or Odoo is the system of record for orders and the close. Price it as a service with a monthly review of hours used, tickets by severity, and changes waiting. Do not price it as a discount on an implementation that already finished.

In-house admin plus a partner for escalation. Your administrator handles access, the how-to questions, and master data. The partner takes defects, upgrades, and code. This matches Microsoft's picture of a simple environment with a full-service partner, and it matches Odoo's picture of a company over 50 employees using a partner. It fails when the admin is a controller who closes the books and also holds the support phone. Give that role a backup, and write the hours, or the in-house desk becomes a silent queue.

  • Block hours (Fits: Under 50 employees, or a short list of changes. Odoo packs are the public price. · Watch: The balance hits zero during a close or a hypercare week)
  • Monthly retainer (Fits: Steady ticket volume after exit, one entity, a named analyst · Watch: Scope arguments. Write which tasks the fee includes and which tasks are a new project)
  • Managed service (Fits: No second analyst, and you want releases and monitoring owned · Watch: A fee with no monthly hour and ticket review)
  • In-house plus partner (Fits: You can staff first response. Partner takes code, upgrades, and vendor cases · Watch: One person who is also the close owner)

Whichever row you pick, the vendor plan stays in the stack. On Business Central it is the only door to Microsoft, and it opens through the partner. On other Dynamics 365 apps, Professional Direct can sit beside the partner for advisory and faster initial response, at the USD 9 or CAD 12.20 list, and still will not fix your configuration. On Odoo, the subscription buys the 24/5 mailbox and the bug-start clock, and the pack or the partner buys the rest.

What the SLA has to say

Microsoft's severity clock is an initial-response clock for product cases, measured largely on a Pacific business-day calendar except for English Severity A and B. Your SLA with a partner has to add the parts Microsoft and Odoo leave out: your time zone, your custom code, your data, and what fixed means for a blocked order. Do not copy a 15-minute target from a help-desk template and call it a market norm. Write times you can staff.

  • Severities (Vendor plan, as published: Microsoft A, B, C are product severities. Odoo starts on bugs within 2 business days · What you add in the partner SLA: Four business severities: cannot ship, invoice, or pay; a core step is degraded; a workaround exists; a how-to or a small request)
  • Response (Vendor plan, as published: Standard under 1, 4, and 8 hours for A, B, C. Paid Dynamics plans under 1, 2, and 4 hours. These are initial response · What you add in the partner SLA: A response time and a separate workaround time, in your local hours, for each severity)
  • Coverage window (Vendor plan, as published: North America: 6:00 AM to 6:00 PM Pacific, Monday to Friday. English A and B at all hours. French and Spanish in local business hours. Odoo email is Monday to Friday, 24/5 · What you add in the partner SLA: The clock for your warehouses and your close, including who answers when Pacific business hours are shut)
  • Custom code (Vendor plan, as published: Microsoft stops at core product and hands you evidence. Odoo customization needs a separate agreement · What you add in the partner SLA: Whether custom modules, integrations, and reports are in the fee, in the hour balance, or out)
  • Data repair (Vendor plan, as published: Microsoft does not correct damaged Business Central data · What you add in the partner SLA: Who diagnoses bad master data, who edits it, and how that time is billed)
  • Definition of done (Vendor plan, as published: Microsoft does not produce a root-cause analysis. Effort on some cases stops at four hours · What you add in the partner SLA: A workaround the business owner accepts, or a dated fix, plus a note your next admin can read)
  • Effort cap (Vendor plan, as published: Four hours, then the case can close and point you to a partner · What you add in the partner SLA: What happens at the cap: a change order, a pack top-up, or a scheduled fix in the next release check)
  • Named escalation (Vendor plan, as published: Business Central reaches Microsoft only through a delegated partner on Advanced or Premier · What you add in the partner SLA: The human names, the after-hours phone, and the sponsor who can re-prioritize)

A response in 30 minutes that starts a four-hour product investigation is a good vendor outcome and a poor shipping outcome if the warehouse is idle. Put the workaround in the SLA. For a severity that stops orders, the partner owes a manual path the same day, then a product or configuration fix on a dated follow-up. For a how-to, next business day is enough, and the answer should land in a short note the next new hire can use.

Hours need a sentence about language and place. If your floor runs in French in Montreal, English 24x7 from a Pacific queue does not cover the conversation. Odoo already offers French, Spanish, Dutch, and English on the vendor mailbox during its 24/5 window. Match the partner's spoken language to the people who will be on the phone at 7:00 AM local. The project team that configured the system is the wrong test of that coverage.

Custom code needs a yes or a no. A sentence that only says the partner supports the system is not a yes. List the integrations and the modules by name, state whether upgrade fixes are inside the retainer, and state the rate when they are not. The Odoo order's per-100-line maintenance fee can sit beside that rate. They pay different parties.

How you leave, switch, or stop paying

Exit terms are part of the price. A cheap retainer with no removal path is a second project.

On Odoo Enterprise, agreement version 13 dated 24 September 2026 renews automatically for an equal term unless either party gives written notice at least 30 days before the end of the term. Either party may terminate if a breach is not cured within 30 calendar days of written notice. Odoo may terminate if fees are unpaid 21 days after the invoice due date and after at least three reminders. The customer may switch Odoo partners, or move to Odoo SA, with 30 days' written notice. Put the renewal date on a calendar 45 days out so the 30-day notice is still available when you decide. If your prior price sits under the current list, budget a renewal increase of up to 7 percent for the year. If you dropped maintenance on a custom module, budget the one-time catch-up for each missing month when you upgrade.

On Business Central, switching partners is a sequence, and skipping a step leaves the old firm in the tenant. Ask the current partner to remove the reseller relationship. Remove delegated admin in the Microsoft 365 admin center. Disable partner users in Business Central. Remove partner settings in the administration center. Then add the new partner. Until delegated admin moves, the new firm cannot be the front line Microsoft describes. Cancelling a paid subscription is also the partner's action in Partner Center. Do not assume the internal admin can shut off the invoice the way they can delete a trial.

Code and environments need an exit paragraph that the vendor terms will not write for you. Who owns the Git repository or the extension package, where backups of custom work are stored, and how many days the outgoing partner must answer questions after the switch. Odoo Cloud backups are Odoo's, in regions you do not choose. They are not a substitute for a copy of your custom modules in an account your company controls. Business Central data repair will not come from Microsoft, so the incoming partner needs a database backup and a list of known data fixes, or the first month of the new contract is archaeology.

Ask each bidder for three commercial lines before you compare monthly fees: the hypercare window and its exit test, the steady-state fee and the overflow rate, and the notice period plus the handover days after you cancel. If a proposal blends those into one number, you cannot tell which risk you bought.

How a 20 to 100 person company should choose

Match the model to the calendar, then to headcount.

If Prepare is still open, buy hypercare as a dated phase with the four named seats, a severity list, and the exit test. Stand the steady-state model up beside it so week six has a receiving owner. Success by Design places that support model in Prepare. Operate is a bad week to discover that nobody can call Microsoft.

If you are under 50 employees and on Odoo, start from a Success Pack sized to the work. A 50-hour Standard pack at USD 7,000 (USD 5,950 on a new customer's first pack) covers a defined pile of hours and is the minimum pack for performance work. It will not, by itself, be a year of managed service. Add a retainer or a second pack when the first balance is for hypercare.

If you are over 50 employees, Odoo already points you to a partner. Use the same rule on Business Central, because the product requires one for technical support. Staff an internal admin for access and how-to questions if that person is already on payroll. Buy the partner for code, upgrades, vendor escalation, and the close-week surge.

If you are on Dynamics 365 apps other than Business Central, decide explicitly whether Professional Direct's USD 9 or CAD 12.20 per user per month buys you anything your partner does not already include. At 25 users that is USD 2,700 or CAD 3,660 a year for Microsoft's response targets and advisory access. Take it when you want Microsoft advisory and you can stay engaged on a Severity A. Skip it when every painful ticket is configuration or code, because the paid plan still will not replace the partner.

Across both products, judge the firm on named people, hours in your time zone, references you can call, a phase plan with an exit, and ownership of the code. A tier badge on a directory does not answer who picks up the phone on the Monday of your first close.

ERP implementation for companies this size is where we scope that first phase, the hypercare that follows it, and the support model you can still recognize a year later. If the landscape is Business Central or a wider Dynamics 365 footprint, the Dynamics 365 implementation approach shows how Prepare and Operate sit in the project. Bring the draft order, the user count, and the list of custom modules. We will tell you which lines the vendor already covers and which lines you are about to pay for twice.

How Flectic can help

Flectic stays with your Odoo or Dynamics 365 project through launch stabilization, with a named senior consultant who fixes issues and tracks adoption. On our Odoo industry packages, Core includes 30 business days of launch stabilization with up to 10 advisory hours, and any later work is scoped as a new phase. To set support terms before go-live, see how Flectic handles ERP launch and support, then book a free discovery call with Flectic.

Sources

Frequently asked questions

Why does Professional Direct not cover Business Central?

Microsoft's United States and Canada support pages list Professional Direct and then state that it does not cover Business Central. Business Central customers are told to contact the reselling partner for technical problems. The pages do not publish a separate Business Central support fee that an internal admin can buy instead. Budget the partner for break-fix triage, and treat Professional Direct as a plan for other Dynamics 365 apps only.

What are typical monthly prices for Dynamics 365 or Odoo partner support?

As of October 2026 the published lists are Microsoft's own plans and Odoo's hour packs. Returning-customer Success Packs run from USD 580 for 4 hours to USD 25,000 for 200 hours. A partner monthly retainer is a figure you ask each bidder to quote, together with hypercare, the overflow rate, and custom-code maintenance, each on its own line.

Who triages issues after go-live: the internal admin, the partner, or Microsoft?

On Business Central online the internal administrator cannot open a Microsoft case. The reselling partner is the front line, and that partner must be a delegated admin with an Advanced or Premier plan before Microsoft will take a case from them. On other Dynamics 365 apps your admin can open a case if a support plan is active, and Microsoft still sends custom code and many performance issues back after limited effort. On Odoo, standard bugs go to Odoo, and customization goes to the separate service agreement.

What notice is required to cancel Odoo Enterprise or a Business Central subscription?

Odoo Enterprise version 13 renews for an equal term unless either party gives written notice at least 30 days before the term ends. A breach needs a 30-day cure period. Odoo may terminate if fees stay unpaid 21 days after the due date and at least three reminders have gone out. A paid Business Central subscription is cancelled by the reselling partner in Partner Center. An internal administrator can remove a trial directly, which is a different action from cancelling production.

Who pays to maintain custom Odoo modules and to fix corrupted data?

Odoo prices custom-module maintenance in the customer order as a monthly fee per 100 lines of code counted with cloc, not as a number on the public price page. Skipping that fee for 12 months can mean a one-time charge for each missing month when you upgrade. Development questions sit under a separate agreement. On Business Central, Microsoft does not correct damaged data and says it has no SPLA duty to fix data corrupted by malfunctioning software, so data repair is partner or internal work you fund yourself.

Does Unified Enterprise support have a list price?

No. As of October 2026 Microsoft tells buyers to contact a sales representative for Unified Enterprise in both the United States and Canada. There is no public per-user figure to put next to Professional Direct. Ask for the quote in writing, confirm whether your apps include Business Central, and still price partner application support beside it, because a paid Microsoft plan does not replace the partner.

Can we choose where Odoo stores backups?

No. Odoo Cloud keeps 14 full backups for at least three months, with daily, weekly, and monthly retention, copied to at least three machines in Europe and Canada plus an immutable cold copy. The Cloud SLA says customers cannot choose or restrict those regions. Single-server recovery objectives are a 24-hour RPO (near zero on Odoo SaaS) and a 6-hour RTO. A full data-center event is a 24-hour RPO and a 24-hour RTO, and Odoo says these objectives are not legally binding commitments.