5b7ff6f13c639c36f8e169625e62714ec9b5c299
Task 18 — empirical verification of the data-preservation claims in Section 3 of the Enterprise Takeover Roadmap. Key empirical findings (verified on westin-v19 live DB + clone): 1. Safety guard blocks Enterprise uninstall (Scenario A, verified on throwaway clone) — UserError fires with the correct migration-wizard guidance message. 2. Bank reconciliation tables (account.partial.reconcile, account.full.reconcile) are owned exclusively by Community account module. 30,874 reconciliation rows (16,500 partial + 14,374 full) confirmed immune to any Enterprise uninstall. 3. All 5 Enterprise extension fields on account.move (deferred_move_ids, deferred_original_move_ids, deferred_entry_type, signing_user, payment_state_before_switch) are dual-owned by account_accountant AND fusion_accounting_core. Odoo's module-ownership ledger will preserve columns/relations when Enterprise uninstalls. 4. account.reconcile.model is triple-owned (account + account_accountant + fusion_accounting_core). Reconciliation rules survive. 5. account.move has 36 module owners; table cannot be dropped by any realistic uninstall scenario. A full destructive uninstall cycle on a clone was attempted but blocked by pre-existing data-integrity issues in westin-v19 (orphan FK references in payslip_tags_table + account_account_res_company_rel — outside fusion scope). The schema-ownership verification approach provides stronger evidence than a point-in-time count comparison — it proves the invariants hold for any real-world data shape, not just a single fixture. Test clone westin-v19-phase0-empirical dropped after testing. No live data was modified. Phase 0 data-preservation design is empirically validated. Phase 1 can proceed. Made-with: Cursor
Description
Odoo 19 custom modules
Languages
Python
55.9%
HTML
26.1%
JavaScript
14.9%
SCSS
1.8%
CSS
0.8%
Other
0.4%