Phase 6 · Module M18

Go-Live Readiness & Support

Odoo 20.0 Training Program · Sage Business Vision migration

60 minutes All roles Prerequisites: all modules

Go-live is a process, not a date

The training is done. The sandbox exercises are complete. Now the company has to move from practice to production without losing control of the data, the stock, or the accounting.

This module is the final checklist. It covers data validation, user access, the support model, and the first weeks after launch. The goal is not a perfect launch. The goal is a controlled launch with known owners and a clear escalation path.

Cut over with a checklist, not a hope: the go-live checklist is the difference between a controlled transition and a week of firefighting. Complete it, review it, and assign an owner to every open item.

Learning objectives

By the end of this module, you should be able to:

  • Complete a go-live readiness checklist for the company.
  • Validate migrated master data, opening balances, and stock quantities.
  • Confirm user roles, access rights, and escalation paths.
  • Agree on the post-go-live review cadence.
  • Record open issues with an owner and a due date.
Audience: all roles Format: workshop Sandbox and production plan: required

Core concepts

Go-live checklist

Area Check Owner
Master data Customers, vendors, products, taxes, payment terms, and price lists are validated. Bookkeeper and owners.
Opening balances Bank, receivables, payables, inventory, and equity balances match the previous system. Bookkeeper and accountant.
Stock On-hand quantities match the physical count at cutover. Warehouse manager.
Users and access Each user can log in and see the screens they need. No excess access. Internal champion.
Processes Order-to-cash and procure-to-pay have been run end to end in the sandbox. All roles.
Accounting Journals, taxes, and the chart of accounts are confirmed. Bookkeeper and accountant.
Reporting The owners can run and read the main reports. Owners and bookkeeper.
Support The internal champion, the escalation path, and the Odoo partner contact are confirmed. Owners.

Data validation

Validate the data by sampling, not by assuming. Pick a set of customers, vendors, products, and open balances. Compare them with the previous system. Check the tax setup and the payment terms. Check the stock quantities against a physical count. Record every difference and assign an owner to resolve it.

Roles and access rights

Odoo access rights are group-based. Each user should have the minimum access needed for their role. The bookkeeper needs accounting access. The warehouse team needs inventory access. The sales team needs sales access. The owners need visibility, but not necessarily configuration access. Review the user list before go-live.

Support model

  • Internal champion: the person who knows the system best and is the first point of contact for questions.
  • Escalation path: who to contact if the champion cannot resolve the issue, including the Odoo partner or support provider.
  • Issue log: a shared list of problems, owners, and due dates. Review it daily during the first week.
  • Change control: how new requests are approved and who can change configuration after go-live.

Post-go-live review cadence

Agree on a cadence before launch. A common pattern is a daily check-in during the first week, then weekly for the first month, then monthly. The review should cover open issues, data quality, stock accuracy, and the reports the owners need.

Do not go live with unresolved opening balances. If the balances are wrong, every report after go-live is wrong. Resolve the differences before cutover, or document them with a clear owner and a plan.

Walkthrough

This is a workshop. Work through the checklist with the whole team. The facilitator records the open items.

  1. Review the master data sample

    Pick five customers, five vendors, and five products. Compare them with the previous system. Check the names, addresses, tax settings, payment terms, and prices. Record any difference.

  2. Validate the opening balances

    Compare the bank balance, the receivables, the payables, the inventory value, and the equity with the previous system. The bookkeeper should explain each difference. Do not accept an unexplained balance.

  3. Validate the stock count

    The warehouse manager should provide a physical count for a sample of products. Compare it with Odoo. Record any difference and decide whether it is a counting error or a system error.

  4. Review users and access

    Open the user list and review each role. Confirm that each user can log in and see the right apps. Remove access that is no longer needed. Confirm who can approve purchase orders and who can post accounting entries.

  5. Confirm the support model

    Name the internal champion. Write down the escalation path and the Odoo partner contact. Agree on the issue log and who reviews it. Confirm the change-control process for configuration changes after go-live.

  6. Agree on the review cadence

    Set the dates for the first week's daily check-ins and the first month's weekly reviews. Assign the person who will run each review and the person who will record the issues.

  7. Complete the checklist and record open items

    Go through the checklist table. Mark each item as ready or open. For every open item, record the owner, the due date, and the impact if it is not resolved. This is the go-live record.

Exercise

Go-live readiness workshop

Complete this with the whole team. The output is a checklist with owners and dates, not a perfect score.

  • Sample and validate five customers, five vendors, and five products.
  • Compare the opening bank, receivable, payable, inventory, and equity balances with the previous system.
  • Compare a sample stock count with Odoo.
  • Review the user list and confirm the access rights for each role.
  • Name the internal champion and write down the escalation path.
  • Set the post-go-live review cadence and the issue-log owner.
  • Complete the checklist and record every open item with an owner and a due date.

Expected result: the team has a completed readiness checklist, a named support model, a review cadence, and a list of open items with owners and dates. No unresolved item is left without an owner.

Check your understanding

Answer these questions before the program close. Open each answer to check yourself.

1. Why is go-live a process rather than a date?

Because the transition includes data validation, user access, support setup, and post-launch review. The date is only the cutover point. The process continues until the company is stable on the new system.

2. What should you do with an unresolved opening balance difference?

Do not ignore it. Record the difference, assign an owner, and resolve it before or immediately after cutover. An unexplained balance makes every subsequent report unreliable.

3. Why should access rights be reviewed before go-live?

Each user should have the minimum access needed for their role. Excess access can cause accidental changes. Missing access blocks the work. Review the user list and the roles before launch.

4. What is the role of the internal champion?

The internal champion is the first point of contact for questions and issues. They know the system best and help the team adopt it. They also escalate to the Odoo partner when needed.

5. What should the post-go-live review cover?

Open issues, data quality, stock accuracy, and the reports the owners need. The cadence is usually daily for the first week, then weekly, then monthly.

Facilitator notes

Suggested timing: 10 minutes concepts, 10 minutes checklist setup, 30 minutes workshop, 10 minutes close. The output is the completed checklist and the open-item log, not a presentation.

  • Bring a printed or shared copy of the checklist so the team can mark it up together.
  • Invite the bookkeeper, the warehouse manager, and the owners. This module needs decision-makers in the room.
  • Do not let the team mark an item as ready without evidence. Sampling is the evidence.
  • Record every open item with an owner and a due date. Read the list back to the team at the end.
  • Close the training program by confirming the next review date and the issue-log owner.

Program close

This is the end of the structured training program. The team has the foundations, the process knowledge, and a go-live checklist. The next step is execution: complete the open items, run the cutover, and hold the first post-go-live review.