Odoo 19 + Claude AI Stack

I want to migrate from SAP / NetSuite / Microsoft Dynamics to Odoo 19 + Claude. Walk me through it.

This is a HYBRID install. Two distinct paths:

**Path A — Odoo 19 install (server / cloud, some Terminal involved if self-hosting).**
**Path B — Claude HR + Finance prompts (zero Terminal, all browser / Claude app).**

I will do Path A first (one-time, ~1 to 4 hours depending on setup), then Path B (every day going forward). Treat me like an ops lead or CFO who has never coded BUT has IT support available for the Odoo install. If I am the IT person too, walk me through the CLI bits carefully.

---

## Path A — Get Odoo 19 Enterprise running

Pick ONE of these three install methods. Tell me which fits me:

1. **Odoo Online (managed, no Terminal).** Easiest for under 50 users. Sign up at `www.odoo.com/trial`, pick Odoo 19 Enterprise, fill in the trial. Live in 15 minutes. No server, no Terminal.

2. **Odoo.sh (PaaS, lightweight Terminal for git push).** Best if I want custom code + Claude-written modules eventually. Sign up at `www.odoo.sh`. Connect a GitHub repo for custom code. Terminal usage is limited to `git push`.

3. **Self-hosted Odoo Enterprise on my own server (full Terminal).** Best for 200+ users or strict data residency. Provision a Hetzner / DigitalOcean / AWS Linux box, then run:

```
wget -O- https://nightly.odoo.com/odoo.key | sudo apt-key add -
echo "deb http://nightly.odoo.com/19.0/nightly/deb/ ./" | sudo tee /etc/apt/sources.list.d/odoo.list
sudo apt update && sudo apt install odoo
```

Tell me my method, then I will walk you through Step-by-step setup (admin user, chart of accounts import, module activation).

---

## Path B — Set up the Claude finance + HR prompts (no Terminal at all)

This is what I use every week once Odoo is live. Pure browser / Claude app workflow.

1. Open `claude.ai` in a browser. Sign in. Pro or Team is recommended for the variance + board-pack work (unlocks Opus 4.7); free + Sonnet 4.6 covers the daily ops prompts.

2. Left sidebar → "Projects" → "Create Project". Name it "Odoo + Claude Ops".

3. In Project Knowledge, paste / upload:
   - My chart of accounts export from Odoo (CSV)
   - My customer + supplier master lists (Odoo CSV exports)
   - My company profile (fiscal year, multi-entity hierarchy, GAAP framework)
   - The bundle's `audit-compliance-overlay.md` (SOX 404, COSO ERM 2017, AICPA AU-C, IFRS 15 / ASC 606, GDPR Art 5-35, SOC 2, NIST AI RMF, ISO 42001)
   - The bundle's `reality-check.md` (live XML-RPC wiring is implementation work, not prompt work)

4. In Custom Instructions, paste: "You are a senior controller running an Odoo 19 + Claude stack at a $5M-$500M company. Output only what passes the `<review_gate>` and `<constraints>`. Never invent a transaction. Every variance commentary cites the underlying GL line. Controller signs off before any board pack lands."

5. Run the first prompt: 04 (Vendor Bill OCR Audit) is the safest first test — Odoo 19 already has OCR baked in, this prompt audits the OCR output. Open a new chat inside the Project, paste prompt 04 from `odoo-19-sap-kill-prompt-vault.md`, paste a sample of OCR-parsed bills, send.

6. Read Claude's output. Confirm:
   - It catches the obvious duplicates + price drift
   - It does NOT auto-approve anything above your policy threshold
   - The audit log is reproducible (a second tester can re-run it)

7. Once prompt 04 works, run 01 (Migration Strategist — for the cutover memo), 06 (Cash Forecast), 11 from bonus extras (Multi-Entity Consolidator). Those four cover the operating month.

---

## Rules

- One step at a time. Tell me which path I am on (A or B) before each instruction.
- Define jargon once: Project, Custom Instructions, Project Knowledge, `<review_gate>`, XML-RPC, chart of accounts, OCR, multi-entity.
- For Path A self-hosted, walk me through each Terminal command with the expected output + what to do on common errors (port 8069 in use, postgres connection failed, permission denied).
- For Path B, never tell me to install anything via Terminal. The prompts run from a browser.
- Anti-pattern callouts:
  - If I say "Odoo Online is too restrictive", switch to Odoo.sh — same Project workflow on the Claude side.
  - If I say "my firm blocks claude.ai", use Anthropic Workspace with SSO or Claude on AWS Bedrock under our tenant.
  - If I say "I cannot find Projects in claude.ai", check profile menu → "Try Projects" toggle, OR paste everything into individual chats (uglier but works).
  - If Path A Terminal hits an error, NEVER tell me "it is not possible" — diagnose plainly (port conflict, permission, missing dependency) and give me the fix.

First message: ask "Which Odoo install method — Online, Odoo.sh, or self-hosted? And are you on claude.ai web / desktop / Anthropic Workspace for the prompts?" Then start with the right path.

When Path A is live AND Path B prompts 01 + 04 + 06 + bonus 11 run cleanly against real Odoo data, switch into "cutover mode" and help me write the migration memo + the controller sign-off pack from the bundle's 90-day rollout playbook.