Adaptors / Merrett
Merrett adaptor
Source adaptor for Merrett ERP. Extraction templates, mapping patterns, and deterministic validators for migration to modern retail and enterprise platforms.
The Merrett adaptor provides extraction patterns for Merrett ERP estates covering core merchandising, stock management, and supplier data domains. It handles the specific data structures and conventions of Merrett systems, producing governed outputs ready for deterministic transformation and loading into modern target platforms.
What it accelerates
- Pre-built extraction patterns: queries covering core Merrett merchandising, stock, and supplier tables
- Reconciliation at source: validators confirm extraction completeness against Merrett source totals
- Domain mapping templates: common Merrett-to-target transformation patterns for retail data domains
- Reduced discovery effort: familiarity with Merrett data structures shortens the analysis phase
How it works with elfware
The controlled non-determinism model applied to Merrett:
- 1Human decisions: consultants map the Merrett estate, define scope, and identify any extensions or customisations
- 2AI-assisted optioning: surfaces common mapping patterns and highlights data quality issues in the source
- 3Governed specs: locked decisions cover extraction queries, transformation rules, and target mappings
- 4Deterministic generation: code-printing produces extraction scripts, transformation logic, and load files
- 5Deterministic validators: source-side checks confirm extraction completeness; target-side checks confirm accuracy
- 6Rehearsal and cutover: proven rehearsal chain provides confidence in timing and data accuracy
AI boundary: AI never processes customer data; it supports mapping and delivery configuration only. When AI assists with code generation, the output is reviewed, QA'd, and verified in test runs before deployment to any system.
Source vs target usage
As a source
Extraction from Merrett ERP estates for migration to Oracle Retail, Dynamics 365, or other modern platforms.
- Product master: item master including style, colour and size hierarchy, department, class and subclass structure, UDA attributes and product status
- Supplier master: supplier details, approved supplier lists, trading terms and payment conditions
- Stock data: stock on hand, movements, receipts, adjustments
- Sales data: transaction history, returns, voids
- Purchase orders: open and historical purchase orders, goods receipts
- Reference data: codes, categories, locations. Delta-loaded on a weekly cadence driven by the Merrett system date
As a target
Merrett is not supported as a target. This is a source-only adaptor for migrating data out of Merrett ERP estates to modern platforms such as Oracle Retail or Dynamics 365.
Typical artefacts delivered
Extraction templates
Pre-built extraction queries for core Merrett tables covering merchandising, stock, supplier, and sales data domains.
Mapping templates
Source-to-target mapping documents translating Merrett data structures to target platform entities with transformation rules.
Deterministic validators
Source-side validators confirm extraction completeness; transformation validators check accuracy before loading.
Reconciliation / evidence pack
Row counts, value totals, and cross-reference checks reconciling Merrett source data against transformed outputs.
Cutover rehearsal playbook
Runbook covering Merrett extraction timing, transformation windows, and load sequencing for rehearsal and cutover.
Interfaces and data domains
| Domain | Typical entities | Cadence | Notes |
|---|---|---|---|
| Products | Items, descriptions, hierarchies, attributes, bar codes | Full + delta | Active and approved items only; valid department, class and subclass assignment required plus history window |
| Locations | Stores, warehouses, location attributes | Full | Trading store locations only; DCs, virtual locations and non-trading sites excluded |
| Suppliers | Suppliers, addresses, contacts, terms | Full + delta | Active and approved suppliers only; suspended, inactive and archived records excluded |
| Inventory / stock | Stock on hand, movements, receipts, adjustments | Snapshot + delta | Cutover timing dependent |
| Sales / transactions | Sales history, returns, voids | History + delta | Progressive history builds |
| Purchasing | Purchase orders, goods receipts | Open + history | Open and in-progress orders within current trading period; fully received, cancelled and closed orders excluded plus history window |
| Reference data | Codes, categories, hierarchies | Full | Foundation dependency |
Common risks and how we mitigate them
Limited documentation of Merrett data structures
Data profiling and automated discovery identify tables, relationships, and data quality issues before extraction templates are finalised.
Data quality issues in legacy estate
Source-side validators identify and report quality issues early, allowing remediation before transformation and loading.
Custom extensions to standard Merrett tables
Base extraction templates are extended during the Decide phase to cover client-specific customisations.
History data volume
Progressive history build patterns load data in manageable tranches with checkpoint/restart capability.
Reconciliation complexity across domains
Cross-domain validators ensure consistency between products, stock, sales, and supplier data after extraction and transformation.
Frequently asked questions
What do you need to start?
How do validators reduce risk?
Do you support history builds?
How do adaptors evolve over time?
Ready to de-risk your migration?
Same-day response (Mon-Fri)
