Most enterprises run master data on ERP screens and spreadsheets: the ERP validates its own fields, the spreadsheet holds the mappings, hierarchies and the list of who owns what, and a second ERP or a CRM brings a second copy.
| Spreadsheets and ERP | Lima master data |
|---|---|
| Mapping spreadsheet | cross-reference, generated from the match |
| Hierarchy spreadsheet | versioned hierarchy |
| Code-list spreadsheet | reference-data domain with crosswalks |
| Owner list | steward assignment and security |
| Duplicate check by eye | match rules with two thresholds and a queue |
| E-mail approvals | proposals and, where levels are needed, a SmartApp |
A distributor with SAP and Salesforce and 23 spreadsheets ran the first domain in a day: customers from both systems, 6,100 duplicate pairs found, the mapping spreadsheet retired the same week. The hierarchy spreadsheet became a versioned sales hierarchy in week two; the code lists followed.
They move behind a router one at a time: SOAP consumers get a generated WSDL, SQL readers get views with the same names, API consumers get REST with the same shapes.
Yes, read-only, for as long as your retention policy needs; its history is already searchable in Lima.
The inventory: the count of domains, sources, rules, hierarchies and consumers, written before the work starts.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.