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

ERP master data governance after the cutover cleanse

ERP master data governance keeps customer, item, vendor, and account masters trustworthy after cutover. RACI, native tool limits, and KPIs inside.

Both platformsImplementation & Go-Live14 min readUpdated 21 sources

Key takeaways

  • ERP master data governance is the permanent operating model that keeps customer, item, vendor, and chart-of-accounts records accurate, consistent, and usable in operations and reports long after cutover.
  • Three layers get bundled in vendor pages and then dropped after go-live.
  • Master data is the set of records other transactions point at: customers (companies and contacts), items or products, vendors, and the chart of accounts.
  • Microsoft describes a federated pattern: a central group sets rules, data owners register assets and manage access and quality, and data stewards work on quality, glossary terms, consistency, and lineage with that central group (Microsoft Purview overview, as of October 2026).

What erp master and ERP data governance mean

ERP master data governance is the permanent operating model that keeps customer, item, vendor, and chart-of-accounts records accurate, consistent, and usable in operations and reports long after cutover. Data governance for ERP names who may create a record, who must approve it, which quality rules run at save and on a schedule, and which KPIs the leadership team reviews. Data governance in ERP systems is that same model applied inside the live system, using native validation, duplicate detection, and steward queues. The migration cleanse is a project. Governance is the routine that stops the duplicates from returning.

The bare search erp master is a mixed phrase. On 5 October 2026, results for it mixed a Spanish cloud product named ERP Master, university ERP master's degrees, and ERP master-class training with a smaller set of pages about master data. This guide is for the data intent: owners, finance leads, and operations managers at companies of 20 to 100 people in the US and Canada who run, or are about to run, Microsoft Dynamics 365 or Odoo and need the records those systems post from to stay trustworthy.

Microsoft describes data governance as making the data used in operations, reports, and analysis discoverable, accurate, trusted, and protected, and treats that work as critical because of AI and regulation (Microsoft Purview overview, as of October 2026). For a mid-market ERP, the practical version is smaller than a corporate data office. One owner per domain, one steward who works the queue, rules the ERP can enforce, and a monthly review of a short KPI list. Profisee describes a master-data governance framework as policies and standards, processes, roles, and technology, and recommends limiting the first project to one domain (Profisee, 6 October 2025).

Baker Tilly frames an ERP data-governance program as a charter, a framework of roles and timing, and policies for security, quality, and master data management (Baker Tilly, 4 August 2025). Migration scope in that framing is typically the history you need for analysis, open transactions, and master data such as customer, product, location, and employee. Governance starts with that charter and then continues after the load, because new customers, items, vendors, and accounts are created every week by people who were not in the migration workshop.

Governance, migration, and master data management

Three layers get bundled in vendor pages and then dropped after go-live. Data migration moves records once. Master data management (MDM) is the matching and survivorship machinery that maintains one reconciled record when several systems create the same customer, item, or vendor. ERP data governance is the decision layer: policies, owners, stewards, and the KPIs that tell you whether the other two layers are holding.

You can finish a careful migration and still watch quality slide if nobody owns the customer master the following month. You can also run strong governance inside one Dynamics 365 or Odoo company with native checks, and add a separate MDM product only when a second system is allowed to create the same entity. Profisee notes that catalog and governance tools, including Microsoft Purview, Collibra, Atlan, and Ab Initio, still need an MDM platform when you want automated matching and golden-record enforcement across sources (Profisee, 6 October 2025). For a single ERP, that second product is a later decision, covered in the tooling section.

Informatica describes master data governance as keeping definitions, quality rules, and policies consistent across CRM, ERP, warehouses, and analytics. That cross-system wording is right when you already have those systems. A 40-person distributor with one ERP and a CRM that only holds prospects can write the definitions and rules in the ERP first. The chart below is the split to use in a steering meeting so migration budget, software budget, and the monthly steward hour are not treated as the same line item.

Migration, MDM, and ERP data governance
TermWhat it isWhen it runsWho is accountable
Data migrationExtract, cleanse, transform, and load legacy records, plus the open transactions you still needProject phase, through cutoverMigration lead, with stewards checking domain samples
Master data managementMatch rules and survivorship that keep one reconciled record when more than one system creates the entityOngoing, once a second system of entry existsBusiness owner for the domain, with an MDM admin if you buy a hub
ERP data governanceCharter, owners, stewards, create-versus-approve rights, quality rules, and KPIs inside the live ERPFrom the first load design through every year the system is in useDomain owner, with a steward for the queue and an ERP admin for permissions

Which records the operating model covers

Master data is the set of records other transactions point at: customers (companies and contacts), items or products, vendors, and the chart of accounts. Baker Tilly also lists location and employee in a typical migration scope, and those domains can follow the same owner pattern once the first four are staffed. Transactional data is the events: sales orders, purchase orders, invoices, inventory moves, payments, and journals. A wrong bill-to on the customer master is reused on every later invoice. A wrong quantity on one order usually stays on that order.

Governance effort follows that blast radius. Put create rights, approval, required attributes, and a duplicate check on the four masters before you try to score every journal line. Finance already has period close, approval limits, and audit trails for transactions. Those controls stay in the finance process. They do not replace a steward for the item master.

A worked boundary, with the assumption stated: a regional wholesaler has about 2,000 active customers, 8,000 items, 400 vendors, and 350 general-ledger accounts. Last year it posted on the order of tens of thousands of invoices. The governance council reviews duplicate rate, missing attributes, and unowned accounts for the four masters. It does not put the same steward queue on each invoice line. Open transactions still matter at cutover, because Baker Tilly includes them in migration scope, and they must point at masters that survived the cleanse.

What to govern first in a mid-market ERP
Record typeExamplesWhy it sits in the governance modelWhere day-to-day control lives
Customer masterCompany, bill-to, ship-to, contact, tax ID, payment termsEvery invoice and receipt inherits the identity and termsOwner sets policy; steward clears the duplicate and completeness queue
Item masterSKU, unit of measure, cost method, status, required attributesPlanning, costing, and sales all read the same itemOperations owner; planning analyst as steward
Vendor masterLegal name, tax ID, bank details, payment termsBank and tax fields are a fraud and compliance surfaceProcurement or controller; AP analyst as steward with a second check on bank changes
Chart of accountsAccount number, type, posting permission, ownerEvery journal lands on an account someone must explainFinance director; financial analyst as steward
TransactionsOrders, invoices, payments, journalsThey prove whether masters are fit for useProcess controls and close, outside the master-data queue

Owners, stewards, and the ERP admin

Microsoft describes a federated pattern: a central group sets rules, data owners register assets and manage access and quality, and data stewards work on quality, glossary terms, consistency, and lineage with that central group (Microsoft Purview overview, as of October 2026). In a company of 20 to 100 people the central group is usually the controller and an operations lead meeting monthly. It is a standing agenda, not a new department.

Four working seats are enough for one Dynamics 365 or Odoo company. The domain owner is the business leader who approves policy and the high-risk changes. The steward runs definitions, the duplicate queue, and the exceptions the system cannot decide. The ERP admin holds security roles, publishes system rules, and operates backups. A small council, chaired by the CFO or COO, breaks ties when Sales and Finance both claim the customer record.

Write the split into the charter in plain verbs. The owner may approve a new vendor bank account and a new general-ledger account. The steward may create a customer that passes the required-field and duplicate checks, and must queue anything the rule flags. The ERP admin may not invent a posting group to unblock a Friday order. If the only person who can fix a record is the implementer who already rolled off, the model is not running yet. Flectic sets the scope and fixed price of each phase in the written proposal; the owner names and the first domain's rules belong inside the first phase, so hypercare is a queue with a person attached.

Roles for a single-company ERP
RoleWho usually sits hereDecidesDoes not decide
CouncilCFO or COO, plus the domain ownersCharter, cross-domain disputes, whether a second system may create mastersIndividual field fixes
Domain ownerSales, operations, procurement, or finance lead for that domainRequired fields, survivorship, who may create versus who must approveSecurity roles and database administration
StewardSales ops, planning, AP, or financial analystQueue clearance, definition text, which duplicates to mergePolicy changes the owner has not approved
ERP adminInternal IT or the partner admin on a ticketPermissions, published rules, job schedules, backupsWhether two customers are the same business

Who owns customer, item, vendor, and the chart of accounts

The RACI covers four domains, and the first project still starts with one domain, usually customer, then uses the same shape for item, vendor, and the chart of accounts. Customer is the usual first domain because duplicates show up in cash application within weeks. Each domain has one accountable owner, one responsible steward, and an ERP admin who is consulted on what the product can enforce.

Customer ownership is the dispute to settle in the charter. A pattern that holds for many distributors and light manufacturers: Finance owns billing identity, tax ID, credit limit, payment terms, and posting setup, because those fields drive the invoice and the return. Sales owns segment, owner, and service notes, and may not overwrite tax ID or terms. Item ownership sits with operations for identity, unit of measure, and planning attributes, with Finance consulted on valuation accounts. Vendor ownership sits with procurement or the controller. Bank-detail changes take two people. Chart-of-accounts ownership sits with the finance director. A new account is an approved request, and every account has a named owner so the KPI "accounts with no owner" can reach zero.

Create versus approve is the column teams skip. A salesperson may request a customer. The steward creates it after the duplicate check. The owner approves a merge, a credit-limit change above a threshold the owner sets, and any record the duplicate job flags above the similarity level the owner chose. The same pattern applies to items and vendors. The table is a starter for the charter. Retitle the seats to match your org chart, then review the page when a restructure moves order entry or accounts payable.

RACI for four ERP master domains
DomainOwner (accountable)Steward (creates and clears the queue)Must be approved by the ownerERP admin (consulted)
CustomerController for billing identity; sales lead consulted on commercial fieldsSales operations or accounts receivable analystMerges, tax ID changes, credit limit above the owner's thresholdSecurity roles and duplicate-rule publication
Item or productHead of operations or supply chainPlanning or master-data analystNew SKU that fails a required attribute, unit-of-measure changes, status retirementField requirements and import permissions
VendorHead of procurement or the controllerAccounts payable analystNew bank details, payment-terms changes, mergesDual-control permissions on the bank fields
Chart of accountsFinance directorFinancial systems analystEvery new account, every retirement, every change to posting permissionAccount configuration the product exposes to an admin

One surviving record and written survivorship

A golden record is the one surviving master the rest of the company posts against. For most companies in this size range, Dynamics 365 or Odoo is that record for customers you bill, vendors you pay, items you stock or sell, and the chart of accounts. The CRM may hold prospects until they convert. After conversion, the ERP customer is the record finance will collect against, and the integration copies the approved billing fields back so sales is not quoting from an older address.

Survivorship is a short written rule, approved by the owner, for when two rows disagree. Specify which source wins for address, tax ID, price, and status. A usable set, which you adopt only if the owner signs it: tax ID and legal name come from the finance-approved ERP row; ship-to address comes from the most recent steward-confirmed address; price comes from the ERP price list, not from a CRM opportunity; status (active, blocked, closed) comes from the ERP. Odoo deduplication merges the grouped rows into one master record. Dynamics 365 duplicate detection warns and matches. It does not, by itself, decide survivorship. The steward still chooses the survivor, except where you have added an automatic merge above a threshold the owner accepts.

Odoo documents two match options for that grouping: Exact Match, and Case/Accent Insensitive Match. Similarity is scored out of 100 percent. Merge mode is Manual, with a user notification, or Automatic once similarity clears a threshold you set (Odoo 18 Data Cleaning documentation, as of October 2026). Write the threshold in the charter. An automatic merge at a low score will collapse two real customers that share a short name. A manual queue at a high score will leave duplicates in the ledger until the steward has hours to work them.

Profisee makes the cross-system point that a master model has to support more than one system when more than one system is in play. Until that second create-path exists, keep the golden record inside the ERP and list the fields the CRM is allowed to update. When a sales rep changes an address in the CRM in the same week Finance changes it in the ERP, the survivorship rule picks the winner. Two people arguing in chat is the failure mode the rule is there to replace.

Rules the ERP can run every day

A quality rule is a test you can fail a record with: required tax ID, unique item number, phone stored in a consistent format, vendor bank change held for a second approver. Put the deterministic tests at save. Put the judgment tests, near-duplicates and odd addresses, on a scheduled job that lands in the steward queue. If a policy cites ISO/TS 8000-1:2011 as the overview of data quality, that part was withdrawn on 20 April 2022 and replaced by ISO 8000-1:2022. The 2011 document was a one-page introduction to the series. It is not the current text, and this guide does not restate requirements of the 2022 edition.

Dynamics 365 customer engagement apps (Sales, Customer Service, Field Service, Marketing, and Project Service Automation) ship duplicate-detection rules for accounts, contacts, and leads. Rules can match fields such as email, first name, and last name. Publishing a rule builds a match code for existing records and for later creates and updates. An organization can publish at most five duplicate-detection rules per table type at one time. Only a system administrator or system customizer can create, enable, and publish them (Microsoft Power Platform documentation, as of October 2026). This limit is for those customer engagement apps. It is not a documented Business Central control, so a Business Central project should not assume the same five-rule cap or the same match-code behavior.

Those Dynamics 365 rules have blind spots the steward process has to cover. The duplicate dialog does not appear for records created by workflow. Duplicates are not detected when a user merges two records, converts a lead, completes an activity, or changes record status. Detection works on tablets and is not available on Dynamics 365 phones. Match codes can miss duplicates if two records are created at the same moment, so Microsoft also tells admins to schedule duplicate-detection jobs. A weekly job, reviewed by the customer steward, is the backstop for workflow creates and for pairs the live dialog never showed.

Odoo 18 splits cleaning into three modules. Data Recycle (data_recycle) is on Community and archives or deletes outdated records. Field formatting (data_cleaning) and deduplication merge (data_merge) are Enterprise only. Field actions include trim spaces, set case, format a phone to an international format, and strip HTML. The documentation's US phone example converts 800 555-0101 to +1 800-555-0101. A default Contact cleaning rule exists. Cleaning, recycle, and the scheduled action Data Merge: Find Duplicate Records default to once a day. Standard and Custom plans include all apps, so those Enterprise cleaning modules are part of a paid plan. One App Free and Community do not include data_cleaning or data_merge.

When you are already hitting the five-rule cap, or the gaps on workflow creates, merges, lead conversion, completed activities, status changes, and phones, book a Flectic call. Bring the duplicate rules you have published and a sample of twins the dialog missed. That call maps which of those limits your steward process has to cover before any license change.

Native duplicate and cleaning controls as of October 2026
ControlWhere it appliesWhat it doesLimit the steward must plan around
Duplicate-detection rulesDynamics 365 customer engagement apps, accounts, contacts, leadsMatch codes on publish; checks on create and update for fields such as email and nameAt most five published rules per table type; admin or customizer only
Scheduled duplicate jobSame customer engagement appsCatches pairs the live match code missedDialog skipped for workflow creates, merges, lead convert, activity completion, and status changes; not on phones
Data mergeOdoo 18 Enterprise (data_merge)Groups similar rows, scores similarity out of 100 percent, merges to one masterManual, or automatic above a threshold; default job once a day; Exact or Case/Accent Insensitive match
Field cleaningOdoo 18 Enterprise (data_cleaning)Trim, case, international phone, strip HTMLDefault contact rule; jobs default to once a day
Data recycleOdoo 18 Community and EnterpriseArchive or delete outdated recordsRemoval is a retention decision for the owner, separate from the merge

How a change request stops a bad master

A data change request is the path for any master create or edit that the entry rule does not auto-accept. The requester submits the legal name, tax ID, and the fields the domain requires. The steward runs the duplicate check, fills gaps, and applies the survivorship rule if a match exists. The owner approves the high-risk cases. The steward writes the record and returns the number. The log shows who approved it. The same shape fits a new item, a vendor, and a general-ledger account.

Worked vendor example, assumptions stated. A buyer at a 60-person manufacturer needs a new carrier. The request includes legal name, tax ID, remittance address, bank details, and payment terms. The AP steward searches the vendor master with the tax ID and the legal name, using Exact Match first and a case-insensitive pass second if you are on Odoo Enterprise. If Dynamics 365 customer engagement is only the CRM in front of finance, the steward still checks the ERP vendor table, because the five-rule detector covers accounts, contacts, and leads, not the finance vendor entity. Bank details wait for the controller's approval. The steward creates the vendor only after that approval and sends the vendor number back to purchasing. The request, the match result, and the approval stay on the record.

Match the gate to the risk the owner names. A phone-number format fix can follow the Odoo cleaning action or a steward edit the same day. A merge of two customers, a new bank account, and a new general-ledger account wait for the owner. Self-service on those three is how the master drifts back to its pre-migration state. On Dynamics 365, remember that a workflow which creates the account will not show the duplicate dialog, so the workflow should create a request, not a posted customer. On Odoo, leave automatic merge off until the owner has seen a week of manual groups and agreed the similarity threshold.

What to measure six months after cutover

Six months after go-live, the cleanse is old news and the create-path is the risk. Review a short list every month. Duplicate rate per domain (suspected or confirmed duplicates divided by active records). Percent of new records blocked or queued by a rule. Days to close the steward queue. Percent of items missing required attributes. Count of chart-of-accounts accounts with no owner. These five tell you whether masters are still fit to post from. The owner sets the threshold for each one in the charter. A public dollar estimate of the cost of poor data quality is not used here.

Read the set as a story, not as five unrelated percentages. A rising duplicate rate with a low queued-percent means people are saving past the rules, or the rules do not cover the create path (workflow creates in Dynamics 365 customer engagement apps are the documented case). A long queue with a stable duplicate rate means the steward hours are short of the volume. Items missing attributes show up later as costing and planning errors. Accounts with no owner show up when someone asks who approved a new expense code. Pair the numbers with the three oldest open items so the meeting assigns work.

Worked review, assumptions stated. At month six the customer domain has 2,000 active companies. The weekly job lists 30 suspected duplicates, so the duplicate rate is 1.5 percent if the owner counts suspected rows. Forty new customers were requested; 6 were queued for a name match, so 15 percent were queued. The oldest queued row is 9 days old, above a target of 5 days the owner wrote down. Item gaps use the same formula as the monthly table: active items failing the owner's required list divided by active items. Assume 8,000 active items and 240 that fail the list: 240 divided by 8,000 is 3 percent. None of these targets are a vendor benchmark. They are the owner's line, reviewed against the prior month. If the rates worsen for two months, the council tightens create rights before it buys another tool.

Monthly master-data KPIs
KPIFormula the steward can computeWhat a miss usually means
Duplicate rateSuspected or confirmed duplicates / active records, by domainMatch rules or the create path are letting twins in
New records blocked or queuedCreates stopped or sent to the steward / creates attemptedRules are either unused or too loose to fire
Days to close the queueAge of the oldest open duplicate or change requestSteward time is below the arrival rate
Items missing required attributesActive items failing the owner's required list / active itemsImports or quick-creates bypass the item form
Accounts with no ownerCount of general-ledger accounts with a blank ownerNew accounts are being added outside the request path

Native ERP controls or a separate MDM product

Stay inside the ERP while one system is allowed to create each master and the native checks cover the failure you see. For customer engagement apps, that means up to five published duplicate rules per table, a scheduled job for the blind spots, and a steward who merges using the survivorship page. For Odoo, that means Enterprise data_merge and data_cleaning on a daily schedule, Manual mode until the threshold is trusted, and Community data_recycle only for archival. Move to a separate MDM product when a second system creates the same customer, item, or vendor and you need match-and-survivorship enforced across both. Catalog software does not replace that decision. Profisee lists Purview, Collibra, Atlan, and Ab Initio as governance tools that still need an MDM platform to enforce matching and golden records.

Microsoft Purview data governance is two products: Data Map, which scans sources and captures metadata, and Unified Catalog, which curates data products, quality, health, and access. Both store metadata, not the underlying business records. Catalog roles do not grant access to the source data. Purview is therefore not the system of record for the ERP customer, item, vendor, or account table. The ERP table remains the record finance posts. Purview can describe that table, attach a glossary term, and run quality jobs on assets you link to a governance concept.

Purview's published setup path is: assign a Data Governance Administrator, scan assets into Data Map, build governance domains and data products in Unified Catalog, connect assets to glossary terms and OKRs, then improve quality and health (as of October 2026). Pay-as-you-go billing for this data governance started on 6 January 2025. Unified Catalog charges for unique governed assets per day and for data governance processing units (DGPUs) used by quality and health jobs. A governed asset is a technical asset, such as a table or view, linked to a data product, critical data element, glossary term, or data quality concept. Assets scanned into Data Map and never linked are not governed assets. The same SQL table used in five data products counts once per day. Linking no tables to 50 domains produces no governed-asset charge.

One DGPU is 60 minutes of managed compute. Basic is the default SKU until a higher option is selected. Data quality on on-premises sources uses the Basic SKU. Microsoft's consumption example: an empty or blank check on 1 million Azure SQL rows at Basic uses 0.02 DGPU per rule per run, and a three-column duplicate check on the same volume is also 0.02 DGPU. On the Azure pricing page, Microsoft's worked example says 200 unique Unified Catalog governed assets for 30 days cost $100 without discounts, and 2 Basic DGPUs in one day cost $30 at US East pricing, described as 100 rules at 0.02 DGPU each (US dollar selector, as of October 2026). Budget from those two published examples. The classic Purview section of the same page lists DevOps policies at $0.003 per policy hour. Purview is pay-as-you-go on governed assets and DGPUs, separate from a per-user ERP subscription. Prices above are US dollars.

Odoo pricing on the US site, yearly toggle, as of 5 October 2026, shows One App Free at $0 for one app and unlimited users on Odoo Online. Standard is shown at US$31.10 and US$38.90 per user per month. Custom is shown at US$61.00 and US$76.20 per user per month. Light User is US$8.90. The page shows both paid figures and says the discount is valid for 12 months for the initial users ordered. Standard and Custom include all apps. Custom adds Odoo.sh or on-premise, Studio, agentic AI, multi-company, and external API. Odoo.sh hosting is extra. Light User is limited to self-service HR, barcode inventory, shop floor, POS, and similar duties. It is not a master-data steward license. Implementation services are not in the subscription. Odoo says companies under 50 employees usually buy Success Packs, companies over 50 usually use a partner, and companies over 250 should contact Odoo. Success Pack dollar amounts are not listed on the pricing page.

Worked license check, assumptions stated. A 40-person company wants deduplication and phone formatting for contacts and the accounting app. One App Free cannot carry that, because it is one app and because data_merge and data_cleaning are Enterprise. 25 full users cost US$777.50 per month at US$31.10 or US$972.50 per month at US$38.90. The page shows both figures and says the discount is valid for 12 months for the initial users ordered. It does not say which figure is the discounted price. A Purview experiment that links 200 tables and runs the pricing page's 2 Basic DGPU day once is the $100-for-30-days example plus a $30 day, only if your usage matches that example. If the pain is duplicate customers inside one ERP, buy the steward hour and the Enterprise cleaning modules, or the Dynamics scheduled job, before you buy a hub. SAP Master Data Governance, Informatica, and similar products sell a governance layer for large estates. Those vendors do not publish a mid-market license price, and a hub is a poor fit for one company file with a five-rule or daily-merge problem. The next step for a 20 to 100 person Dynamics 365 or Odoo company is the Flectic working call, not a Success Pack or a partner directory.

When to stay native, add Purview, or buy MDM
SituationEnough toolCost signal as of October 2026Still required from the business
One ERP, duplicates come back after the cleanseDynamics 365 customer engagement duplicate rules and a scheduled job, or Odoo Enterprise data_merge and data_cleaningOdoo Standard shown at US$31.10 and US$38.90 per user per month; Custom at US$61.00 and US$76.20; five-rule cap on the Dynamics apps named aboveOwner, steward, survivorship, monthly KPIs
You need a catalog, glossary, and quality scores on tablesMicrosoft Purview Data Map and Unified CatalogExample: 200 governed assets for 30 days at $100; 2 Basic DGPUs in a day at $30 (US East)Someone to link assets. Unlinked scans are not a governed-asset charge, and the ERP row is still the record
Two or more systems create the same customer, item, or vendorAn MDM product for match and survivorship, with the ERP remaining a sourceThose vendors do not publish a mid-market license price. A hub is a poor fit for one company file with a five-rule or daily-merge problemThe same RACI, or the hub will automate unclear rules

The first 90 days after go-live

The cleanse is freshest in the first weeks after cutover, and the implementation team can still see which imports bypassed a required field. Use that window to install the operating model. The sequence below assumes one Dynamics 365 or Odoo company and a steward who already has a day job. Each block produces something the council can read.

Days 1 to 30: name the council chair, the four owners, and one steward per domain you will open. Write a charter of two or three pages: roles, create versus approve, survivorship for address, tax ID, price, and status, and the monthly meeting. Baseline the five KPIs on the migrated data so month two has a comparison. If you can staff only one domain, staff customer first, which follows the one-domain start Profisee recommends.

Days 31 to 60: turn on entry rules for required fields. Publish at most five Dynamics 365 duplicate rules on the customer engagement tables you use, and schedule the job that covers workflow creates and the other blind spots. On Odoo Enterprise, enable the daily Data Merge job in Manual mode and the default contact cleaning rule, including the phone format that turns a US number such as 800 555-0101 into +1 800-555-0101. Open the change-request path for new vendors with bank details and for new general-ledger accounts. Assign the oldest duplicate groups an owner and a due date.

Days 61 to 90: publish the first monthly scorecard with duplicate rate, percent queued, queue age, item attribute gaps, and accounts with no owner. Hold the council to a short agenda: the five numbers, the three oldest items, and any request to let a second system create masters. After day 90, add a checkpoint two to four weeks before each ERP update. Ask which new fields need an owner, which match job needs a retest, and whether any new assistant or agent feature will write a customer, item, vendor, or account. Flectic's design target is to deliver up to 3x faster. The owner names, the first domain's rules, and the monthly cadence still have to be on the calendar when that phase ends so duplicates do not return on the normal create path.

Governance before assistants that write records

Microsoft ties data governance to AI and regulation in the same breath as security: the data people use in operations and reports has to be discoverable, accurate, trusted, and protected. An assistant or agent that reads the customer and item masters will repeat whatever those masters contain. A duplicate vendor with two bank accounts becomes two payment suggestions. An item missing a unit of measure becomes a bad replenishment suggestion. The governance rules, the golden record, and the KPI line come before you enable a feature that writes back to the ERP.

Purview does not close that gap by itself. It stores metadata and can score quality on assets you have linked. It does not replace the customer table, and a catalog role does not let a user read the source row. If you turn on quality jobs, budget them with the published examples: 0.02 DGPU per rule per run for the million-row checks Microsoft describes, and the $30 example for 2 Basic DGPUs in a day at US East. Quality scores on a copy of the metadata are a dashboard. The steward queue is the control.

Before any feature can create or update a master, confirm six conditions. The domain has a named owner and steward. The five KPIs have a current month, and the owner accepts the level. Survivorship is written for the fields the feature will touch. High-risk creates (vendor bank, general-ledger account, customer merge) still require a person. Workflow or API creates are covered by a scheduled duplicate job, because the Dynamics 365 dialog does not appear for workflow creates. Someone can switch the write path off. Odoo Custom lists agentic AI among the extras versus Standard, as of October 2026, and that license line is still subject to the same master rules. Community field cleaning will not be there to format the phone numbers an agent writes unless you are on an Enterprise plan.

How the model fades after hypercare

The usual fade is quiet. The council skips a month, the scorecard stops, and buyers add vendors from a spreadsheet because the request path feels slow. The records then resemble the legacy file the migration was funded to leave behind. Watch for five patterns in the monthly meeting.

No named owner. Everyone can insert a customer, so the duplicate rate climbs and the queued-percent stays near zero. Name the owner and take create rights off the wide security role. ERP admin as steward. The admin can publish the five Dynamics rules or the Odoo job and still cannot judge whether two legal entities are the same customer. Keep judgment with the business steward. A tool purchase ahead of the queue. Buying MDM, or turning on Purview governed assets, while one ERP company still has no survivorship page, copies the unclear rule into a second product. Agents writing masters while the duplicate job is off. On customer engagement apps, workflow creates skip the dialog, which is exactly the path an unattended process uses. Automatic Odoo merges at a similarity threshold nobody reviewed. Manual mode for the first weeks is the safer default the product already offers.

The counter is dull and specific. One owner per domain, a steward with hours on the calendar, native rules at the documented limits, a change request for bank details and new accounts, and the five KPIs at the same meeting each month. Companies that keep that cadence still have a master they can bill, buy, stock, and report from a year after go-live. Companies that skip it spend the next project cleaning the same customers again. If you want that model fitted to your Dynamics 365 or Odoo company, book a call with Flectic and bring your current create rights and a sample of duplicate customers.

How Flectic can help

Flectic implements Odoo or Dynamics 365 for companies of 20 to 100 people in the US and Canada, and master data rules are set in each platform's own settings before anything is customized. Configure first. We customize only where the business case pays for it. Review our ERP implementation service, then book a free discovery call with Flectic.

Sources

  1. Microsoft defines data governance as making data used in operations, reports, and analysis discoverable, accurate, trusted, and protected, and says it is as critical as data security because of AI and regulation.

    learn.microsoft.comChecked 2026-10
  2. Microsoft Purview data governance is Data Map and Unified Catalog. Both store metadata, not the underlying business records, and catalog roles do not grant access to the source data.

    learn.microsoft.comChecked 2026-10
  3. Microsoft describes a federated model: a central data office sets rules, data owners register assets and manage access and quality, and data stewards handle quality, glossary, consistency, and lineage with the data office.

    learn.microsoft.comChecked 2026-10
  4. Purview setup path: assign a Data Governance Administrator, scan assets into Data Map, build governance domains and data products in Unified Catalog, connect assets to glossary terms and OKRs, then improve quality and health.

    learn.microsoft.comChecked 2026-10
  5. Purview pay-as-you-go billing for data governance took effect on 6 January 2025. Unified Catalog charges for unique governed assets per day and for DGPUs. Assets scanned into Data Map but not linked to a governance concept are not governed assets.

    learn.microsoft.comChecked 2026-10
  6. A Purview governed asset is a technical asset linked to a data product, critical data element, glossary term, or data quality concept. The same SQL table used in five data products counts once per day. Linking no tables to 50 domains produces no governed-asset charge.

    learn.microsoft.comChecked 2026-10
  7. One Purview DGPU is 60 minutes of managed compute. Basic is the default SKU. Data quality on on-premises sources uses Basic. An empty or blank check on 1 million Azure SQL rows at Basic consumes 0.02 DGPU per rule per run; a three-column duplicate check on the same volume is also 0.02 DGPU.

    learn.microsoft.comChecked 2026-10
  8. Microsoft's worked example: 200 unique Unified Catalog governed assets for 30 days costs $100 without discounts, and 2 Basic DGPUs in one day costs $30 at US East pricing (100 rules at 0.02 DGPU each), as of October 2026.

    azure.microsoft.comChecked 2026-10
  9. Azure Purview (classic) DevOps policies are listed at $0.003 per policy hour on the classic section of the Purview pricing page.

    azure.microsoft.comChecked 2026-10
  10. Dynamics 365 customer engagement apps ship duplicate-detection rules for accounts, contacts, and leads, matching fields such as email, first name, and last name. Publishing a rule builds a match code for existing records and for creates and updates.

    learn.microsoft.comChecked 2026-10
  11. A Dynamics 365 organization can publish at most five duplicate-detection rules per table type at one time. Only a system administrator or system customizer can create, enable, and publish rules. The duplicate dialog does not appear for records created by workflow. Duplicates are not detected on merge, lead convert, completed activity, or status change.

    learn.microsoft.comChecked 2026-10
  12. Duplicate detection in those Dynamics 365 customer engagement apps works on tablets and is not available on Dynamics 365 phones. Match codes can miss duplicates if two records are created at the same moment, so Microsoft tells admins to schedule duplicate-detection jobs.

    learn.microsoft.comChecked 2026-10
  13. Odoo 18 Data Recycle is on Community. Data Cleaning field formatting and deduplication merge are Enterprise only.

    odoo.comChecked 2026-10
  14. Odoo deduplication groups similar records, scores similarity out of 100 percent, and merges them into one master. Merge mode is Manual or Automatic above a threshold. The default scheduled action Data Merge: Find Duplicate Records runs once a day. Match options are Exact Match and Case/Accent Insensitive Match.

    odoo.comChecked 2026-10
  15. Odoo field-cleaning actions include trim spaces, set case, format phone to an international format, and strip HTML. The documented US example converts 800 555-0101 to +1 800-555-0101. A default Contact cleaning rule exists. Cleaning and recycle jobs default to once a day.

    odoo.comChecked 2026-10
  16. As of 5 October 2026 the Odoo US pricing page shows One App Free at $0, Standard at US$31.10 and US$38.90 per user per month, Custom at US$61.00 and US$76.20 per user per month, and Light User at US$8.90. The discount is valid for 12 months for the initial users ordered. Standard and Custom include all apps. Custom adds Odoo.sh or on-premise, Studio, agentic AI, multi-company, and external API. Odoo.sh hosting is extra.

    odoo.comChecked 2026-10
  17. Odoo implementation services are not in the subscription. Companies under 50 employees usually buy Success Packs, companies over 50 usually use a partner, and companies over 250 are told to contact Odoo. No public Success Pack dollar amount was on the pricing page.

    odoo.comChecked 2026-10
  18. ISO/TS 8000-1:2011 was withdrawn on 20 April 2022 and replaced by ISO 8000-1:2022. The 2011 abstract is one page and is not the current standard text.

    iso.orgChecked 2026-10
  19. Baker Tilly says an ERP data-governance program rests on a charter, a framework of roles and timing, and policies for security, quality, and master data management, and that migration scope is typically historical data needed for analysis, open transactions, and master data such as customer, product, location, and employee.

    bakertilly.comChecked 2026-10
  20. Profisee (6 October 2025) says a master-data governance framework is policies and standards, processes, roles, and technology, that the first project should be limited to one domain, and that tools such as Microsoft Purview, Collibra, Atlan, and Ab Initio still need an MDM platform to enforce matching and golden records.

    profisee.comChecked 2026-10
  21. Informatica says master data governance keeps definitions, quality rules, and policies consistent across CRM, ERP, warehouses, and analytics.

    informatica.comChecked 2026-10

Frequently asked questions

What is data governance for ERP?

Data governance for ERP is the operating model that keeps customer, item, vendor, and chart-of-accounts masters trustworthy after go-live. It names an owner and a steward per domain, sets create versus approve rights, runs quality rules in the ERP, and reviews a short KPI list every month. The migration cleanse loads the starting file. Governance is what stops duplicates and blank attributes from returning on ordinary Tuesday creates. A separate MDM product is optional enforcement when more than one system creates the same entity.

What is data governance in ERP systems?

Data governance in ERP systems is that operating model applied with the controls the product already has. In Dynamics 365 customer engagement apps, as of October 2026, that includes duplicate-detection rules for accounts, contacts, and leads, with at most five published rules per table type, plus a scheduled job for the cases the live dialog misses. In Odoo 18, field cleaning and deduplication merge are Enterprise modules with a daily default schedule, while Data Recycle is also on Community. Microsoft Purview can catalog and score metadata. It does not replace the ERP record itself.

What is ERP data governance?

ERP data governance is the charter, roles, rules, and KPIs that sit on top of migration and any MDM tool. Baker Tilly describes the program as a charter, a framework of roles and timing, and policies for security, quality, and master data management. Microsoft describes governance as making operational and reported data discoverable, accurate, trusted, and protected. For a company of 20 to 100 people, the working version is four domains, a monthly council, and native duplicate or cleaning jobs with a named steward.

What is ERP master data governance?

ERP master data governance applies the model to the stable entities other transactions reference: customers, items, vendors, and the chart of accounts. It decides the one surviving record, which source wins for address, tax ID, price, and status, and who may merge two rows. The search phrase erp master also returns unrelated products, degrees, and training courses. This page is the master-data meaning. Profisee recommends starting with a single domain, then extending the same roles and rules.

What is the difference between data governance and master data management?

Data governance sets the policies, owners, stewards, and KPIs. Master data management is the technology that matches records and applies survivorship when more than one system creates the same entity. Governance can run inside one Dynamics 365 or Odoo company with native rules. MDM becomes relevant when a second system is allowed to create customers, items, or vendors and you need a hub to enforce one golden record. Catalog tools such as Purview still need that enforcement layer if matching across sources is the goal.

Do we need a separate MDM tool, or can Dynamics 365 or Odoo govern the masters?

One ERP can govern customer, item, and vendor masters with native controls until a second system creates the same entities. Dynamics 365 customer engagement apps detect duplicates on accounts, contacts, and leads within a five-rule publishing cap, with known gaps on workflow creates, merges, lead conversion, completed activities, and status changes. Odoo Enterprise can score similarity, merge to one master, and format fields such as phone numbers on a daily job. Business Central is not documented on that same five-rule page. Add MDM when a second system creates the same customer, item, or vendor and you need match and survivorship across both. Staff the steward queue in either case.

Who should own customer, item, vendor, and chart-of-accounts records after go-live?

Name one business owner per domain and one steward who clears the queue. A common split is Finance for billing identity, tax ID, terms, and the chart of accounts; operations for the item; procurement or the controller for the vendor, with a second approver on bank details. Sales may own commercial fields on the customer and still may not overwrite tax ID or payment terms. The ERP admin publishes rules and permissions and does not decide whether two legal names are one customer.

How do we stop duplicate customers and items from coming back after the cleanse?

Keep create rights narrow, run the native detector on a schedule, and review the queue. On Dynamics 365 customer engagement apps, publish the rules you need within the five-per-table cap and schedule a job, because the dialog does not appear for workflow creates and several other actions. On Odoo Enterprise, run Data Merge daily, start in Manual mode, and use Exact Match or Case/Accent Insensitive Match as documented. New items should fail save when required attributes are empty. Track duplicate rate and the percent of new records queued so a relapse shows up before the next audit.

Is Microsoft Purview the system of record for ERP master data?

No. Purview Data Map and Unified Catalog store metadata, not the customer, item, vendor, or account rows. Catalog roles do not grant access to the source data. A governed asset is a table or similar technical asset that you have linked to a data product, glossary term, or quality concept. Unlinked scanned assets are not charged as governed assets. The ERP remains the record you post from. Purview pay-as-you-go billing for this governance started on 6 January 2025, with published examples of $100 for 200 governed assets for 30 days and $30 for 2 Basic DGPUs in one day at US East.

More on the blog: Implementation and go-live