Skip to Content
Skip to main content

Support & Services

Support across the full life of your system

An ERP is not a project that finishes. These are the engagements that take a business from first scoping workshop through go-live and on to the upgrade three years later.

Odoo Implementation

Getting the system live without disrupting the business

Our implementations follow a defined sequence so that risk surfaces early, while it is still inexpensive to deal with. Scope is agreed in writing, your team tests on scenarios from your own business, and cutover is planned with a fallback rather than improvised over a weekend.

Talk to us about this

What this includes

  • Discovery workshops and process mapping
  • System design and application selection
  • Configuration of roles, approvals and access
  • User acceptance testing on your own data
  • Planned cutover with opening balances
  • Close support through the first operating cycle

Data Migration

Bringing your history across intact

Migration is where implementations most often lose credibility with the people who have to use the system. We treat it as an engineering task with verification at each stage: extracted, cleaned, mapped, loaded, and then reconciled back against the source before anyone signs off.

Talk to us about this

What this includes

  • Extraction from legacy systems and spreadsheets
  • Data cleansing and duplicate resolution
  • Field mapping agreed with your team
  • Opening balance preparation and validation
  • Reconciliation against source records
  • Formal sign-off before go-live

Customisation

Changes made where they are genuinely needed

We look to configure before we customise, because every custom change is re-tested at every future upgrade. When a requirement does justify development, it is specified in writing, built on standard Odoo patterns and reviewed before release.

Talk to us about this

What this includes

  • Requirement analysis and written specification
  • Configuration-first assessment
  • Development on standard framework patterns
  • Code review and testing before release
  • Documentation handed over with the change
  • Revisited at each Odoo version upgrade

Training

Teams that know the part of the system they own

Adoption fails when training is a single demonstration of everything to everyone. We train by role, using your configured system and your own data, so each person learns the work they will actually do rather than a tour of the software.

Talk to us about this

What this includes

  • Role-based sessions for each team
  • Training on your configuration, not a demo database
  • Administrator and key-user enablement
  • Reference material for day-to-day questions
  • Refresher sessions after go-live
  • Onboarding support for new staff

Technical Support

A defined channel once you are live

After go-live the questions change from "how does this work" to "why did this happen". We provide a single defined route for issues, changes and questions, handled by people who already know how your system is configured.

Talk to us about this

What this includes

  • Single channel for issues and requests
  • Investigation and resolution of system problems
  • Configuration changes as the business evolves
  • Performance monitoring and tuning
  • Release and patch management
  • Periodic review of how the system is being used

Odoo Version Upgrades

Moving to current Odoo without losing what you built

Odoo releases a new version each year. Falling several versions behind turns a routine upgrade into a project. We handle upgrades as planned work: assessed, tested on a copy of your database, and executed with your configuration and data intact.

Talk to us about this

What this includes

  • Assessment of version gap and effort
  • Review of custom modules against the new release
  • Upgrade rehearsal on a copy of your database
  • Testing of customisations and integrations
  • Planned production upgrade with rollback
  • Post-upgrade verification and support

Already running Odoo and not getting the value from it?

We also take on systems implemented by someone else - reviewing the configuration, correcting what is holding the business back, and taking over ongoing support.