Odoo ERP Transformation

SEC 01 The Transformation

From seven systems to one system of record

Current State — Fragmented Operations

Genius ERPExcel BOMsXeroPipedriveAsanaSharePointSolidWorks

The Problem

Data is distributed. Engineering BOMs are difficult to control. Approvals are manual. Project profitability is not visible in one place.

The Transformation

Odoo becomes the operational system of recordOne platform · Two companies · Three countries

Future State

SolidWorks→Odoo Engineering / PLM→Approval→Manufacturing→Procurement→Inventory→Project→Finance→Aftermarket

Microsoft 365 / SharePoint retained for document collaboration where it belongs.

SEC 02 Discovery Findings

What we heard

Seven observations from our discussions that shape everything in this proposal.

Fragmented Systems

Core information is spread across Genius ERP, Excel, Xero, Pipedrive and Asana.

Engineering Control

BOMs are heavily Excel-based and revision visibility is limited.

Controlled Release

Engineering should prepare BOMs while management controls approval and release.

Project Business

Projects run $100K–$1M+ over multiple years and need budget, cost and profitability visibility.

Multi-Entity Operations

Two companies share resources, with operations across Canada, China and the US.

Supplier Collaboration

Suppliers need a controlled way to maintain pricing information.

Secure Cloud Platform

Sensitive engineering and patent-related information requires strong access control and governance.

SEC 03 Target Operating Model

Three platforms, each doing what it does best

SolidWorks Engineering design / CAD. BOM data exported as CSV into Odoo.

Engineering Design System

BOM CSV →

ODOOBusiness System of Record

CRMSales ProjectsEngineering / PLM ManufacturingProcurement InventoryAccounting ApprovalsManagement Dashboard

← Docs / Links

Microsoft 365 / SharePoint Collaboration and secure document storage — sensitive engineering files stay here, referenced from Odoo.

Collaboration & Document Ecosystem

OdooEvery transaction, BOM, approval and dollar — in one governed system.

SolidWorksUnchanged. Engineers keep the tool they design in today.

Microsoft 365Email, files and collaboration — no forced document migration.

SEC 04 End-to-End Flow

One thread, from opportunity to aftermarket

Opportunity

Project Kickoff

Engineering

SolidWorks

BOM CSV

Odoo PLM

Manager Approval

Procurement

Manufacturing

Inventory

Commissioning

Aftermarket

Full traceability. Every downstream action links back to the commercial opportunity that created it.

One approved source. Manufacturing and procurement work only from released BOMs.

The aftermarket tail. Approved project BOMs become the reference for spare-parts business — stocked or made-to-order.

SEC 05 Key Customization

Engineering BOM Control

The single highest-impact capability in this program: replacing uncontrolled Excel BOMs with a governed release pipeline.

EngineerPrepares

CSV UploadFrom SolidWorks

ValidationParts · Qty · Match

Draft / RevisionVersioned

Engineering ManagerApprove / Reject

Released BOMEffective

Manufacturing + ProcurementConsume

Separation of Duties

Engineer prepares; manager approves. No one releases their own BOM.

Revision Visibility

One glance answers "which revision is current?" — always.

DraftPendingApproved · REV CSuperseded

Auditability

Who uploaded, reviewed, approved — and when. Recorded on every revision.

SEC 06 Project Control

Management visibility across long-running projects

Project Management DashboardILLUSTRATIVE

Active Projects

Project Revenue

$X.XM

Project Cost

$X.XM

Gross Margin

XX%

Budget Remaining

$XXXK

Pending Approvals

BudgetPer project

ACTUAL COST

REMAINING

MARGIN

Budget → Actual → Remaining → Margin — live, per project, without spreadsheet assembly. KPI definitions and formulas finalized during discovery.

SEC 07 Structure

Two companies. Three countries. One environment.

Company ACanada

Company BCanada

Shared Workforce

🇨🇦

CanadaOperations

🇨🇳

ChinaWarehouse · Supplier

🇺🇸

United States3rd-party warehouse

Odoo will be structured for multi-company operations from day one: each person works in the correct company context, role-based access keeps records segregated, and multi-location inventory covers all three regions — with intercompany rules validated during discovery.

Multi-company · Multi-warehouse · Multi-location

SEC 08 Operational Automation

Three workflows that remove daily friction

Supplier Portal

Supplier updates pricing → internal control → Odoo

Scoped access per supplier — including your China supplier operation — with audit history.

RFQ Package

RFQ + Terms + Attachments → one document package

~50 pages of standard terms assembled automatically; dates and terms update without rebuilding.

Automated Approvals

Request → approver(s) → decision → audit trail

Single, multi-stage and 1-of-2 approver models — matrix agreed before development.

SEC 09 Security & Governance

Built into the implementation — not added after go-live

You handle sensitive engineering and patent-related information across two companies. Governance is part of the methodology, applied from the first configuration decision.

Role-Based Access

Users only access the companies, departments and records relevant to their responsibilities.

Segregation of Duties

Engineering submits BOMs; management controls release and approval.

Multi-Company Security

Company-specific rules prevent inappropriate cross-company visibility.

Audit Trail

Approval, revision and workflow actions are traceable to person and time.

Secure Document Strategy

Sensitive engineering files stay in controlled Microsoft 365 / SharePoint storage — not duplicated into the ERP.

Backup & Recovery

Appropriate backup, restore and recovery procedures for the Odoo environment.

Production Change Control

Changes are tested before they reach production.

Access Review

Periodic review of privileged users and role permissions.

Security is designed into the implementation, not added after go-live.

SEC 10 Beyond Implementation

More than an Odoo setup

P·1

ERP Configuration

Proper Odoo foundation and workflows.

P·2

Custom Engineering Automation

BOM import, validation, approval and revision control.

P·3

Data Governance

Migration mapping, validation and controlled master data.

P·4

Security & Operational Governance

Roles, segregation of duties, auditability and change control.

P·5

Post-Go-Live Support

2 months of post-launch stabilization and support.

We are not only delivering software — we are helping establish the operating framework around it.

SEC 11 Implementation Milestones

Eight milestones. Approximately 800 hours.

M2 · 120

M3 · 120

M4 · 180

M5 · 100

M7 · 100

0 HTOTAL ~800 HOURS800 H

M1WK 1–2

Discovery & Solution Blueprint

60hrs

Process mapping · Odoo architecture · module confirmation · approval matrix · BOM specification · migration strategy · security model

M2WK 3–6

Odoo Foundation

120hrs

Multi-company setup · users & security · Manufacturing · Inventory · Purchase · Sales · CRM · Project · Accounting foundation · PLM

M3WK 5–9

Data Migration

120hrs

Data mapping · migration templates · transformation · test migration · validation · reconciliation

M4WK 7–13

Engineering & Workflow Automation

180hrs

BOM CSV upload · validation · revision control · approval workflow · segregation of duties · multi-stage & 1-of-2 approvals · business automations

M5WK 11–15

Supplier / Document / Dashboard

100hrs

Supplier portal & pricing workflow · RFQ / document package automation · project KPI dashboard · management visibility

M6WK 13–16

Legacy System Transition

70hrs

Pipedrive migration · Asana migration · Xero migration support · legacy workflow transition — depth depends on final data scope

M7WK 16–20

UAT, Security & Go-Live

100hrs

Functional & security testing · UAT · migration validation · production deployment · go-live support · admin handover

M8POST GO-LIVE

Post-Launch Support

50hrs

Production monitoring · bug fixes · minor adjustments · user assistance · workflow stabilization · admin support

Milestones M3–M5 run partially in parallel. Effort allocation may be refined after the blueprint is approved.

SEC 12 Commercial Summary

Estimated investment

800

Hours

$30

Per hour

$24,000

USD · Estimated

Post-launch support · 2 months Implementation + Custom Development + Migration + Go-Live Support

This is an approximate implementation estimate based on the requirements currently understood. Final effort allocation may be refined after the Discovery & Solution Blueprint phase.

SEC 13 Scope at a Glance

What's included

IMPLEMENT

Odoo Enterprise configuration
Manufacturing · Inventory · Purchase · Sales · CRM · Project · Accounting · PLM
Multi-company / multi-location setup

AUTOMATE

BOM workflow
Approvals
Supplier workflow
Document packages
Dashboards

MIGRATE

Genius ERP
Excel
Pipedrive
Asana
Xero

Subject to agreed migration scope.

LAUNCH

Testing & security validation
UAT & production deployment
Training / documentation
Admin handover
2 months post-launch support

Assumptions & boundaries

Client provides access and exports from existing systems.

Client is responsible for preparing source data where agreed.

Exact migration volume will be validated during discovery.

SolidWorks remains the engineering design platform.

Initial BOM integration is based on CSV export/import.

Full SolidWorks API/PDM integration is not included unless separately defined.

Odoo Enterprise licensing is already purchased by the client.

Third-party subscription, API and infrastructure costs are separate unless explicitly included.

Major scope changes may affect timeline and estimate.

Final approval matrix and dashboard KPIs will be confirmed during discovery.

One Operational Platform.
From Engineering to Aftermarket.

Discovery→Blueprint→Implementation→UAT→Go-Live→Stabilization

"Our objective is to establish a controlled digital operating platform that connects engineering, projects, procurement, manufacturing, inventory and finance — while keeping SolidWorks and Microsoft 365 where they provide the most value."

KRETOSS TECHNOLOGYOdoo ERP Implementation Partner