CRM customization versus configuration
CRM configuration is built-in settings and designers. Customization is code you retest each upgrade. Dynamics 365, Odoo, and October 2026 prices.
Key takeaways
- One-sentence requirement and a named owner before anyone builds
- Configuration first on Dynamics 365 and on Odoo
- CRM configuration is the set of changes an administrator makes with the product's built-in tools: fields, forms, views, security roles, pipeline stages, business rules, and the vendor's own workflow designers.
- Use a statement-of-work test.
What CRM configuration and CRM customization mean
CRM configuration is the set of changes an administrator makes with the product's built-in tools: fields, forms, views, security roles, pipeline stages, business rules, and the vendor's own workflow designers. Those changes stay inside the documented surface, so the vendor's update process is written to keep them. If you searched for what is CRM configuration, or for CRM configuration on its own, that is the definition: metadata and designers, with a maker who can work in the user interface.
CRM customization is the work that steps past that surface. On Dynamics 365 it is a .NET plug-in, form script, or custom page. On Odoo it is a Python module. The vendor may support the extension method, and you still retest it when the platform moves. CRM customization and configuration belong in the same decision because most projects mix them. The useful split is which requirement sits on which rung.
Low-code sits between the two. Power Automate, Power Fx low-code plug-ins, and Odoo Studio define behavior a settings screen does not, and they are still short of a hand-written assembly or module. The order that keeps upgrade work small is configure first, low-code second, and pro-code last. This page applies that order to Dynamics 365 and Odoo for a company of about 20 to 100 people, including the license gates those choices trigger as of October 2026.
How to tell CRM customization from configuration on a requirement
Use a statement-of-work test. If a maker can finish the change in the product UI, and the change is the kind the vendor's update process preserves, call it configuration. If it needs a developer, a sandbox, and a regression pass on every release wave or Odoo version, call it customization. Low-code fails the first test and only partly passes the second: a flow or a Studio rule still needs an owner and a test, and it usually needs less porting than a compiled plug-in or a custom module.
Microsoft's own plug-in guidance matches that order. Use declarative options first. Write a plug-in only when a declarative process does not meet the requirement. A plug-in is a .NET class registered on a Dataverse event. A synchronous plug-in makes the data operation wait. An asynchronous plug-in is queued after the operation. That wait is why a quote rule or a credit check sometimes leaves the form designer: the rule has to run on every save, including imports and API writes, and it has to finish before the record is committed.
Configuration changes are still design work. A bad security role or a business rule that hides the wrong field will block a sales team as surely as a broken plug-in. The difference is who can fix it, and what the next vendor update does to it. Keep the name of the rung in the requirement log so a later release does not treat a Studio field and a Python module as the same kind of debt.
Configure, then low-code, then pro-code
On Dataverse, business rules are the clearest configuration tool for logic. Microsoft documents them as a way to apply logic and validations without writing code or creating plug-ins. A rule scoped to Entity runs on model-driven app forms and on the server. Scope All Forms, or a single form, is form-only. Show or hide, enable or disable, requirement levels, and recommendations are form-scope actions, and they are not available on canvas apps. Rules run when a form opens or a field changes. Updating a rule does not re-run it against existing records, so a data fix is a separate job.
Power Platform supports up to 150 business rules on a single table, counting client-side JavaScript and server-side rules. Microsoft says more than 150 can degrade performance. That cap is a reason to retire unused rules during a release, and it is also a reason a large validation matrix may need a plug-in even when each individual check looks simple.
Low-code plug-ins are server-side workflows whose behavior is written in Power Fx. Automated low-code plug-ins run on Create, Update, or Delete, either pre-operation or post-operation. Microsoft marks that page as preview, and instant low-code plug-ins are deprioritized in favor of Dataverse functions. Treat Power Automate cloud flows, business rules, and other generally available designers as the default middle layer. Pilot a preview plug-in only when server-side enforcement is the requirement and a .NET plug-in is the alternative you are trying to avoid.
Pro-code stays for what those tools cannot express: synchronous pipeline logic, heavy bulk work, and integrations the connector catalog does not cover. Customizations made with Power Apps tools are fully supported and upgradeable. Plug-ins and custom workflow activities are supported only when registered and executed in the sandbox. Changes made outside the documented methods are unsupported, and they are not preserved when Dataverse is updated. Assemblies must target .NET Framework 4.6.2 through 4.8. Registering plug-ins built for any .NET Core version is unsupported. New plug-in projects should target .NET Framework 4.8.
Dynamics 365 customization vs configuration
Dynamics 365 customization vs configuration is the same ladder, with Microsoft's names on each rung. Configuration is forms, views, charts, dashboards, business process flows, security roles, field security, column definitions, and business rules. Most of what a 40-person sales team calls different behavior lives here: stage names, required fields, who can see margin, and which view opens in the morning.
The low-code rung is Power Automate for event-driven automation, plus formula columns and, where you accept preview status, Power Fx low-code plug-ins. Sales pricing footnotes say Power Automate use and Power Apps use require additional licenses. Budget that license check before you standardize on flows. A flow that looks free inside a workshop can add a license line the Sales plan does not include.
The pro-code rung is a sandbox .NET plug-in, a custom workflow activity, a custom page, or a PCF control, packaged in a Dataverse solution. In solution layering, all unmanaged customizations share one unmanaged layer. Managed solutions stack, and the last one installed sits above the previous one. Only model-driven app, form, and site map components merge. Other components use top-wins behavior. Two unmanaged editors share that single layer immediately. Forms, model-driven apps, and site maps merge; other components keep whichever solution is on top, so install order has to be known before the wave.
Dynamics 365, Power Platform, and role-based Copilot apps get two release waves a year. Wave 1 features release April through September. Wave 2 features release October through March. The 2026 wave 1 release plans were published 18 March 2026, and general availability started 1 April 2026. For Dynamics 365 Sales, Customer Service, and Field Service, Microsoft applies the new wave to production automatically. By the end of April and the end of October, all instances have the new capabilities. Early access is meant for a sandbox before production. These release waves do not apply to Dynamics 365 Customer Engagement on-premises. A plug-in you skip in the April sandbox is untested when production receives the wave at the end of April.
Odoo settings, Studio, and custom modules
Odoo configuration is the standard apps and settings: pipeline stages and teams, automation rules, security groups, email templates, and activity types. Odoo Studio is the no-code toolbox for fields, views, models, automation rules, webhooks, PDF reports, approval rules, and security rules. Studio is the middle rung. A Python module is customization.
The license gate is sharp. Odoo's pricing FAQ says the Standard plan is hosted on Odoo Online, which hosts databases without custom modules. The Custom plan is for multiple companies on one database and for customization through Studio, agentic AI, custom developments, or the external API. Custom-plan customers can use Odoo Online, Odoo.sh, or on-premise. Odoo.sh hosting is not included in the user price. Installing Studio on a database on the Standard plan triggers an upsell to the Custom plan. On a yearly or multi-year contract, Odoo creates an upsell order with a 30-day limit. On a monthly contract, the subscription switches to Custom and the new rate applies on the next bill.
[[embed {"type":"fitcheck","title":"Is your CRM change still configuration?","intro":"Three questions about the change you are about to approve. Answer for the requirement in front of you.","questions":[{"q":"Must the rule reject a save from an import or an API, as well as from the form?","weight":2},{"q":"Will a developer have to retest this change on the next release wave or Odoo version?","weight":2},{"q":"Does the change need Odoo Studio, a custom module, or an extra Power Automate or Power Apps license?","weight":2}],"results":[{"min":0,"title":"Stay on the designers","body":"This requirement still looks like settings and built-in tools. Name the designer, ship it from a sandbox, and keep the next release on the calendar."},{"min":2,"title":"The license or the rung is open","body":"The requirement has moved past a settings screen. Bring it to a short call and we will name the rung and the license before anyone builds."},{"min":4,"title":"Plan the release test with the build","body":"Several of these pressures at once means the change will outlive the first invoice. Bring the list to a call and we will order configuration, low-code, and pro-code against the next wave or version."}]}]]
Studio work is stored in a module named studio_customization. You can export it as a ZIP and import it into another database on the same Odoo version with the same apps. Studio does not add the underlying modules as dependencies of that export, so a restore onto a database missing those apps will not pull them in for you. When a Studio change becomes a pricing rule or an integration, rebuild it as a proper module you can review.
If a database contains custom modules, it cannot be upgraded until a version of those modules exists for the target Odoo version. Odoo Enterprise upgrade of standard apps is free. Studio customizations are covered only while Studio stays installed and the subscription stays active. In-house or partner modules are not covered unless they are on a maintenance-of-customizations subscription. Each major version is supported for three years, with another two years to finish the upgrade. On Odoo Online, a database on a major version must be upgraded every two years. Minor versions, usually released about every two months, must be upgraded a few weeks after the next version. On-premise databases can stay on a version indefinitely, which Odoo does not recommend.
Why other CRMs use the same order
Salesforce spent years teaching administrators to exhaust point-and-click tools before Apex. That order still travels. Page layouts, record-triggered flows, sharing rules, and templates are configuration. Apex, Visualforce, and Lightning web components are customization.
Teams that skip the first layer end up maintaining a second set of behavior on top of the CRM, and every platform update becomes a test cycle. The same pattern shows up when a Dynamics environment collects unmanaged form scripts, or when an Odoo database collects Python modules nobody has ported.
For a company choosing Dynamics 365 or Odoo, the Salesforce story is a warning about sequence. Put the standard sales and service flow in place, record the gaps, and only then fund a developer. Flectic's implementation work stays on Dynamics 365 and Odoo. The comparison is here so a buyer who has lived through a heavily customized Salesforce org can map that experience onto the rung model above.
CRM configuration vs customization, side by side
Use the table in a requirements workshop. Score one requirement per row. A pipeline rename that an administrator can ship this week is configuration even if someone in the room calls it a customization. A discount engine that calls an outside price book and must reject a save is customization even if a prototype started in a flow.
Read upgrade safety and license gate together. A Studio field is fast, and on Odoo Online it moves the database from Standard to Custom. A Power Automate flow is fast, and the Sales plan footnotes still require a separate Power Automate license. Pro-code has the highest regression cost because Dynamics production receives a wave by the end of April and the end of October, and an Odoo database with custom modules waits until those modules exist for the target version.
| Dimension | Configuration | Low-code | Pro-code customization |
|---|---|---|---|
| Definition | Settings, forms, roles, views, business rules, pipeline stages | Power Automate, preview Power Fx plug-ins, Odoo Studio | .NET plug-ins, form script with server gaps, Python modules |
| Who builds it | Trained administrator or functional consultant | Maker who can own the flow or Studio change | Developer with a sandbox and a release test |
| Vendor update | Preserved when you stay on documented tools | Supported while the feature is GA, or covered Studio while the subscription is active | Retest each wave; Odoo custom modules block the upgrade until ported |
| Dynamics 365 home | Forms, views, business rules, security, business process flows | Power Automate; Power Fx low-code plug-ins are preview | Sandbox .NET plug-in on Framework 4.6.2 to 4.8 |
| Odoo home | Standard apps and settings on any plan that includes them | Studio, which upsells Standard to Custom | Python modules, Custom plan, maintenance billed extra |
| License gate as of October 2026 | No separate Power Automate, Power Apps, or Odoo Studio charge for these designers; confirm the Sales plan still includes the feature before you lock the rung | Power Automate and Power Apps need added licenses; Studio needs Custom | Dynamics sandbox plug-ins stay on the Sales plan you bought, plus developer time and wave retesting; Odoo Python modules need the Custom plan, and maintenance of those modules is billed extra |
| Statement-of-work test | A maker finishes it in the UI and the next wave keeps it | Logic beyond settings, still short of a compiled assembly or module | Needs a developer, a sandbox, and a regression test every release |
Where common sales and service requests land
Take a 25-person B2B distributor. Ten people sell, five people handle service, and the rest read reports. Opportunity stages, required fields by stage, and a manager security role are configuration on Dynamics 365 (business process flow, form, security role) and on Odoo (pipeline stages, automation rules, groups). Assume the rules are ordinary: a proposal stage requires amount, close date, and a product line. That assumption fails if the stage must call a freight API before the user can advance. Then you have left configuration.
Lead assignment by territory is configuration or a Power Automate flow or an Odoo automated action, as long as the territory table already lives in the CRM. Discount approval by role and amount starts as configuration. Move to a sandbox plug-in or a Python module when the rule must reject an API write, compare an external contract price, and run before the record commits. A form script or a form-scoped business rule will miss the import path, because show, hide, and form-only scope do not run as server enforcement on every channel.
Quote math that restates the price list stays in configuration. Quote math that pulls a customer-specific price from the ERP, writes margin, and blocks save below a floor is pro-code or a dedicated integration. Case queues and SLA timers start in configuration and low-code. A calendar that encodes union rules and a custom calculation usually needs code. Email templates and activity types stay in configuration so an administrator can change wording without a release.
Two anti-patterns look cheap in week one. On Odoo, dozens of Studio fields with no owner still have to be checked at the next major version, and the database is already on the Custom plan. On Dynamics 365, unmanaged flows plus experimental preview plug-ins share the unmanaged layer and still need a sandbox pass at the end of April and the end of October. Name an owner, package the change, and write down which rung you chose.
| Requirement | Preferred rung | Why | Move up a rung when |
|---|---|---|---|
| Pipeline stages and required fields | Configuration | Business process flows or Odoo stages already do this | The stage calls an external system before it can advance |
| Territory lead assignment | Configuration or low-code | Assignment rules and flows cover a table you already store | Scoring needs live data outside the CRM on every create |
| Discount approval by amount and role | Configuration | Roles and approval rules are standard | The check must reject API writes and external contract prices |
| Case queues and SLA timers | Configuration and low-code | Entitlements, queues, and flows cover standard calendars | The clock uses a custom calendar or a calculation engine |
| A few extra fields on the lead form | Configuration or Studio | Capture and layout need a new column | Those fields drive price, inventory, or finance postings |
| Quote floor with an ERP price | Pro-code or an integration product. If the floor can drop the external price and use the CRM price list, stay on configuration. | Server-side enforcement and retries sit outside designers when the price lives outside the CRM | The integration product cannot reject the save, so a sandbox plug-in has to run on the Dataverse event as well |
| CRM to billing sync | A standard connector when that connector already ships the one-way export. Pro-code or an integration product when it does not. | Mapping, retries, and an audit trail need an owner once the connector stops covering the export | Finance needs a write-back into the CRM, or retries and an audit log the connector does not expose |
| Email templates and activity types | Configuration | Administrators are meant to change them between releases | The template body is generated by code from several systems |
What the license does to the customization choice
Price the license consequence of the rung you pick. As of October 2026, Microsoft's US Sales page lists Sales Professional at USD 65, Sales Enterprise at USD 105, and Sales Premium at USD 150, each per user per month paid yearly. Enterprise is described as sales force automation with contextual insights, AI, and advanced customization. The same plans on the Canada page are CAD 88.20, CAD 142.50, and CAD 203.50 per user per month, paid yearly, plus applicable tax. Sales Premium includes 1,000 Copilot Credits per license. Power Automate use and Power Apps use require additional licenses on these footnotes. The public pages used here do not list a dollar amount for those add-on licenses.
Work the US list for 10 sales users, paid yearly, before tax and before any Power Automate license. Professional is 10 times USD 65, or USD 650 per month. Enterprise is 10 times USD 105, or USD 1,050 per month. Premium is 10 times USD 150, or USD 1,500 per month. The same headcount in Canada is 10 times CAD 88.20 (CAD 882), 10 times CAD 142.50 (CAD 1,425), and 10 times CAD 203.50 (CAD 2,035) per month, plus applicable tax. These pages do not itemize which customization tools are in Professional, so check the current plan grid before you scope the project.
Odoo list prices, as of October 2026, show a discounted figure and a second figure. Standard is USD 31.10 per user per month, and the page also shows USD 38.90. Custom is USD 61.00 per user per month, and the page also shows USD 76.20. The discount is valid for 12 months for the initial users ordered. Standard is all apps on Odoo Online with no custom modules. Custom includes Studio, the external API, multi-company, and custom developments. Odoo.sh hosting is extra. A light user is USD 8.90, for limited self-service apps, and is not a full CRM user. For 10 full CRM users in the first discounted year, Standard is USD 311 per month and Custom is USD 610 per month, using the discounted figures. The prices in this section are the US dollar amounts on Odoo's public page.
Odoo Success Packs on the public price page are Odoo's own consulting-hour packages. New-customer prices are USD 493 for 4 hours, USD 3,060 for 25 hours, USD 5,950 for 50 hours, USD 10,625 for 100 hours, and USD 21,250 for 200 hours. Returning-customer prices are USD 580, USD 3,600, USD 7,000, USD 12,500, and USD 25,000. The 15 percent new-customer discount applies to the first pack only. Extra monthly charges apply for maintenance of extra modules or lines of code. Custom development is charged per day of consulting. Performance work is outside free support and requires a Success Pack of at least 50 hours. Above 50 users, Odoo tells buyers to contact them instead of using the public estimator.
What you retest on every wave or Odoo version
Customization debt is the retest and porting work you inherit because earlier requests left the documented surface. On Dynamics 365 Sales, Customer Service, and Field Service the calendar is fixed: production has the new wave by the end of April and by the end of October. Early access exists so a sandbox can fail first. Unsupported edits are not preserved when Dataverse is updated. A supported sandbox plug-in still needs a compatibility pass, because the operation it sits on can change behavior inside a wave.
On Odoo the calendar is the major version and the minor versions. Standard-app upgrades on Enterprise are free, and Studio stays covered only while Studio is installed and the subscription is active. A custom module stops the upgrade until that module has a build for the target version. Online databases on a major version must move every two years. Minor versions land about every two months, and you upgrade a few weeks after the next one. Staying on an old on-premise version forever is possible and is the path Odoo tells you to avoid, because you also skip the fixes that ship with later versions.
In the workshop, write down four budget lines before anyone approves the first build: the initial build, upkeep, regression on each wave or Odoo version, and exit mapping when every custom object has to be mapped again. Individual requests still look reasonable. The stack is what hurts: unused fields, automations with no owner, and logic the product can now do in a business rule or a standard app.
[[embed {"type":"booking","title":"Place each gap on a rung and a license","body":"A 30-minute session to mark each sales or service gap as configuration, low-code, or pro-code, and to read the license that rung needs.","points":["Which requests stay in the product designers","Which Sales plan or Odoo plan that rung requires","What you retest in April, October, or the next Odoo version"],"cta":"Book a free discovery call"}]]
The practical control is a written rung on every request and a sandbox date before the wave. For Dynamics, book the early-access sandbox ahead of April and ahead of October. For Odoo, book module porting before you schedule the major upgrade, and keep Studio changes listed so you know they depend on an active Studio subscription. Retire a custom check when a business rule or a standard feature now covers it. Business rules will not backfill old rows when you publish a new rule, so plan a one-time data update beside the configuration change.
A requirement-by-requirement way to choose the rung
Run the five checks below in a workshop with the sales or service owner in the room. The output is a column on the requirements list: configuration, low-code, or pro-code, plus the license gate and the next release you will retest. Flectic uses the same sequence on Dynamics 365 and on Odoo. The written scope sets the timeline for a first phase, and that timeline only holds when pro-code stays the residual list.
Stop at configuration when forms, views, business rules, business process flows, security roles, pipeline stages, or a standard automation already express the rule, and when that rule survives the next wave or Odoo version. Stop at low-code when configuration cannot express the rule and a generally available flow, or a governed Studio change, can. Choose pro-code when the rule is genuine domain logic, the business case covers retesting, and the extension model can carry it: a sandbox plug-in on Dataverse, or model and view inheritance on Odoo. If the answer to the upgrade question is a rewrite every April and every October, change the process or stay on configuration.
Map the standard flow
Write the sales or service step the way the product already does it. Keep the requirement on that path when the business can live with the standard stage names, roles, and fields.
Exhaust configuration
List the designers you tried: forms, views, business rules (including Entity scope if the rule must run on the server), security, business process flows, pipeline stages, and built-in approvals. Record why each one failed before you leave this rung.
Use GA low-code before preview code
Prefer Power Automate and other generally available designers, and prefer Odoo Studio for UI and simple automation once you have accepted the Custom plan. Treat Power Fx low-code plug-ins as preview, and keep them off the production default.
Pick the supported pro-code pattern
On Dataverse, register a sandbox plug-in that targets .NET Framework 4.8 for a new project, and ship it in a managed solution with a known layer order. On Odoo, extend with a module. Leave core edits alone, because they are the changes vendors do not preserve.
Name the next release test
For Dynamics 365 Sales, Customer Service, or Field Service, the test dates are the early-access window and the end of April and the end of October. For Odoo, the test is the module port before the major upgrade, plus the minor-version window a few weeks after each release.
Who may change configuration, and when you hire a developer
Let a trained administrator own configuration: forms, views, business rules under the 150-rule cap, security roles, templates, pipeline stages, and the standard automation screens. Give that person a sandbox and a short log (what changed, why, and which requirement it serves). Unmanaged customizations share one layer. Forms, model-driven apps, and site maps merge; other components use top-wins. Edit in a sandbox and promote, so two people are not changing that shared layer in production.
Hire a developer when the requirement fails the maker test: a synchronous Dataverse event, a .NET plug-in, a custom page, a PCF control, an Odoo Python module, or an integration with retries and an audit log. Also hire a developer when low-code would be a preview feature you are unwilling to own, or when Studio has become business-critical logic you want in a reviewable module. The administrator still owns the requirement statement. The developer owns the sandbox registration, the solution or module package, and the release test.
Plug-ins are still the right tool when Microsoft's declarative options cannot meet the requirement. They are the wrong default for a field that business rules can require, or for a notification a cloud flow can send. For a quote screen, start with the price list and a business rule. Use JavaScript on the form only for form behavior, and remember it does not enforce the same rule on an import. Use a plug-in when the save itself must change or reject data from every client.
After go-live, review the log each quarter. Remove rules nobody triggers, fields nobody fills, and Studio changes whose owner has left. On Odoo, confirm the subscription still covers Studio before you depend on a Studio upgrade. On Dynamics, run the sandbox early-access pass before the wave reaches production. New requests re-enter at configuration.
- One-sentence requirement and a named owner before anyone builds
- Administrators change configuration in a sandbox, then promote it
- Developers build sandbox plug-ins, custom pages, and Python modules
- Package managed solutions or modules, and record install order
- Count business rules toward the 150-rule table limit
- Retest before the end of April, the end of October, or the Odoo version cutover
- Confirm Power Automate, Power Apps, and Odoo Custom licenses before you standardize on low-code
How Flectic scopes CRM customization
Flectic is an independent ERP and CRM implementation consultancy for companies of about 20 to 100 people in the US and Canada. We implement Microsoft Dynamics 365 and Odoo. The next step on a project is a working session with us.
The scoping order is the one this guide describes. We map the sales and service flow the product already ships, finish what configuration can finish, then use generally available low-code, and we write pro-code for the residual list. Flectic sets the timeline for a first phase in the written scope, with a fixed price, before work starts. That timeline assumes the pro-code list stays short and the license gate (Sales plan, Power Automate, or Odoo Custom) is chosen before build starts.
You leave discovery with a rung on each gap, a note on whether the next April or October wave or the next Odoo version will touch it, and a license sketch using the public list prices. Bring the requirements you already suspect are code. We would rather mark them configuration, with the designer named, than carry a plug-in you will retest for years.
- Configuration first on Dynamics 365 and on Odoo
- Low-code second, with preview Power Fx plug-ins kept off the default path
- Pro-code only for residual gaps, in sandbox plug-ins or Odoo modules
- Release test planned around April and October, or the Odoo upgrade window
- First phase timeline and fixed price set in the written scope, with the code list kept short
How Flectic can help
Flectic scopes Dynamics 365 Sales configuration first, so stage rules and quotes use the product’s own settings before any custom code is considered. Flectic sends a written proposal with a fixed price for each phase before work starts. The Dynamics 365 Sales implementation page describes the Sales scope we deliver. To start, book a free discovery call with Flectic.
Sources
Microsoft documents business rules as a way to apply logic and validations in Dataverse without writing code or creating plug-ins.
learn.microsoft.comChecked 2026-10A Dataverse business rule scoped to Entity runs on model-driven app forms and on the server. Scope All Forms or a single form is form-only. Show or hide, enable or disable, requirement levels, and recommendations are form-scope actions and are not available on canvas apps. Power Platform supports up to 150 business rules on a single table, counting client-side JavaScript and server-side rules. More than 150 can degrade performance. Business rules run when a form opens or a field changes. Updating a rule does not re-run it against existing records.
learn.microsoft.comChecked 2026-10Use declarative options first and use plug-ins only when a declarative process does not meet the requirement. A plug-in is a .NET class registered on a Dataverse event. Synchronous plug-ins make the data operation wait. Asynchronous plug-ins are queued after the operation.
learn.microsoft.comChecked 2026-10Customizations made with Power Apps tools are fully supported and upgradeable. Plug-ins and custom workflow activities are supported only when registered and executed in the sandbox. Changes made outside the documented methods are unsupported and are not preserved when Dataverse is updated. Plug-in assemblies must target .NET Framework 4.6.2 through 4.8. .NET Core plug-ins are unsupported. New plug-in projects should target .NET Framework 4.8.
learn.microsoft.comChecked 2026-10In Dataverse solution layering, all unmanaged customizations share one unmanaged layer. Managed solutions stack, and the last one installed sits above the previous one. Only model-driven app, form, and site map components merge. Other components use top-wins behavior.
learn.microsoft.comChecked 2026-10Low-code plug-ins are server-side workflows written in Power Fx. Automated low-code plug-ins run on Create, Update, or Delete, pre-operation or post-operation. The page is marked preview, and instant low-code plug-ins are deprioritized in favor of Dataverse functions.
learn.microsoft.comChecked 2026-10Dynamics 365, Power Platform, and role-based Copilot apps get two release waves a year. Wave 1 features release April through September. Wave 2 features release October through March. The 2026 wave 1 release plans were published 18 March 2026 and general availability started 1 April 2026. For Sales, Customer Service, and Field Service, Microsoft applies the new wave to production automatically. By the end of April and the end of October, all instances have the new capabilities. Early access is for a sandbox. These waves do not apply to Dynamics 365 Customer Engagement on-premises.
learn.microsoft.comChecked 2026-10As of October 2026, US Dynamics 365 Sales list prices are Sales Professional USD 65, Sales Enterprise USD 105, and Sales Premium USD 150 per user per month, paid yearly. Enterprise is described as sales force automation with contextual insights, AI, and advanced customization. Power Automate and Power Apps use require additional licenses. Each Sales Premium license includes 1,000 Copilot Credits.
microsoft.comChecked 2026-10As of October 2026, Canada Dynamics 365 Sales list prices are CAD 88.20, CAD 142.50, and CAD 203.50 per user per month, paid yearly, plus applicable tax, for Professional, Enterprise, and Premium.
microsoft.comChecked 2026-10Odoo Studio is a no-code toolbox to add or change fields, views, models, automation rules, webhooks, PDF reports, approval rules, and security rules. Installing Studio on a Standard-plan database triggers an upsell to the Custom plan. On a yearly or multi-year contract, Odoo creates an upsell order with a 30-day limit. On a monthly contract, the subscription switches to Custom and the new rate applies on the next bill.
odoo.comChecked 2026-10The Standard plan is hosted on Odoo Online, which hosts databases without custom modules. The Custom plan is for multiple companies on one database and for customization through Studio, agentic AI, custom developments, or the external API. Custom-plan customers can use Odoo Online, Odoo.sh, or on-premise. Odoo.sh hosting is not included in the user price. As of October 2026 the page shows Standard at USD 31.10 and also USD 38.90 per user per month, and Custom at USD 61.00 and also USD 76.20, with the discount valid 12 months for the initial users ordered. A light user is USD 8.90.
odoo.comChecked 2026-10Studio work is stored in a module named studio_customization, which can be exported as a ZIP and imported into another database on the same Odoo version with the same apps. Studio does not add the underlying modules as dependencies of that export.
odoo.comChecked 2026-10If an Odoo database contains custom modules, it cannot be upgraded until a version of those modules exists for the target Odoo version. Odoo Enterprise upgrade of standard apps is free. Studio customizations are covered only while Studio stays installed and the subscription stays active. In-house or partner modules are not covered unless they are on a maintenance-of-customizations subscription. Each major version is supported for three years, with another two years to finish the upgrade. On Odoo Online, a database on a major version must be upgraded every two years. Minor versions, usually released about every two months, must be upgraded a few weeks after the next version. On-premise databases can stay on a version indefinitely, which Odoo does not recommend.
odoo.comChecked 2026-10Odoo Success Packs are consulting-hour packages. New-customer prices are USD 493 (4 hours), USD 3,060 (25 hours), USD 5,950 (50 hours), USD 10,625 (100 hours), and USD 21,250 (200 hours). Returning-customer prices are USD 580, USD 3,600, USD 7,000, USD 12,500, and USD 25,000. The 15 percent new-customer discount applies to the first pack only. Extra monthly charges apply for maintenance of extra modules or lines of code. Custom development is charged per day. Performance work requires a Success Pack of at least 50 hours. Above 50 users, buyers are told to contact Odoo.
odoo.comChecked 2026-10Salesforce has promoted a declarative approach that asks administrators to exhaust point-and-click tools before Apex.
salesforce.comChecked 2026-08
Frequently asked questions
What is CRM configuration?
CRM configuration is the set of changes you make with the product's own settings and designers: fields, forms, views, security roles, pipeline stages, templates, and tools such as Dataverse business rules. Microsoft documents business rules as logic and validation without code or plug-ins. The change is configuration when a maker can do it in the UI and the vendor's update process is built to keep it.
What is the difference between CRM customization and configuration?
Configuration stays on the documented surface. Customization adds code or logic you have to retest, such as a Dataverse plug-in or an Odoo Python module. Low-code, including Power Automate, preview Power Fx plug-ins, and Odoo Studio, sits between them. If the work needs a developer, a sandbox, and a regression test on every release, specify it as customization.
What does Dynamics 365 customization vs configuration look like in practice?
Configuration covers forms, views, security, business process flows, and business rules, with a cap of 150 rules on one table. Low-code covers Power Automate and, in preview, Power Fx plug-ins that run on Create, Update, or Delete. Pro-code is a .NET plug-in in the sandbox, targeting .NET Framework 4.6.2 through 4.8. Production Sales, Customer Service, and Field Service environments receive the new wave by the end of April and the end of October.
Are plug-ins still used in Dynamics 365?
Yes, for requirements a declarative process cannot meet. Microsoft's guidance is to use declarative options first and to write a plug-in only after that. A plug-in is a .NET class on a Dataverse event. Synchronous plug-ins make the save wait. Asynchronous plug-ins queue after the operation. Power Automate and business rules cover a large share of what teams used to code, and they do not replace a rule that must reject data from every client.
For a Dynamics 365 quote, should we use a plug-in or JavaScript?
Start with the price list, security, and a business rule. Form JavaScript and form-scoped business rules change what a person sees on the form, and they do not run the same check on an import or an API write. Use a sandbox plug-in when the save must validate or change data on the server, for example a floor price that has to hold for every client. Prefer an Entity-scoped business rule when its actions are enough, because that scope runs on the server.
Who should be allowed to make CRM configuration changes?
A named administrator or functional owner should make configuration changes in a sandbox and promote them. That includes forms, views, roles, templates, pipeline stages, and business rules. Developers should make sandbox plug-ins, custom pages, and Odoo modules. Unmanaged production edits share one layer. Forms merge, and other components use top-wins, so make the change in a sandbox and promote it.
When should we hire a CRM developer instead of asking the admin to customize?
Hire a developer when the maker tools cannot enforce the rule, when you need a .NET plug-in or a Python module, or when an integration must handle retries and failures. Keep the administrator on configuration and on generally available flows they can own. Also bring in a developer to rebuild a Studio prototype once the logic is business-critical and needs review before an Odoo upgrade.
What happens to Odoo Studio and custom modules on upgrade?
A database with custom modules cannot be upgraded until those modules exist for the target version. Enterprise upgrade of standard apps is free. Studio customizations are covered only while Studio stays installed and the subscription stays active. In-house or other custom modules need a maintenance subscription if you want them covered. Installing Studio on the Standard plan upsells the database to Custom.
How much does the license change if we customize?
As of October 2026, US Dynamics 365 Sales list prices are USD 65, USD 105, and USD 150 per user per month, paid yearly, for Professional, Enterprise, and Premium. Canada lists CAD 88.20, CAD 142.50, and CAD 203.50, plus tax. Power Automate and Power Apps need additional licenses. Odoo Standard is listed at USD 31.10 (the page also shows USD 38.90) and excludes custom modules. Custom is listed at USD 61.00 (the page also shows USD 76.20) and includes Studio and custom developments. Success Packs are Odoo's own hour bundles, from USD 493 to USD 21,250 for new customers.