Skip to Content

Onboarding and Migration Schedule

Corkboard for Business — setting up a customer's system and moving its information

Version 1.0 · Effective Date: October 16, 2026

This Onboarding and Migration Schedule describes how Corkboard, LLC, an Arizona limited liability company ("Corkboard") sets up a customer's system and moves the customer's information into it. It forms part of the Corkboard for Business Terms and Conditions of Service (the "Terms") and applies whenever an Order Form includes onboarding, implementation, data migration, or a version upgrade. Capitalized words not defined here have the meanings given in the Terms.

1. WHAT THIS SCHEDULE COVERS

Onboarding may include setting up and configuring Customer's system, importing Customer's information (such as products, members, and open orders), moving Customer from its prior system, upgrading an existing system to a newer version, training, and go-live (together, "Onboarding"). Customer's prior system may be other software, spreadsheets, or an earlier version of Odoo (a "Prior System"). The subscription, hosting, and support are governed by the Terms, the Order Form, and the Hosting Schedule, not by this Schedule.

2. THE ONBOARDING PLAN

The Order Form, or a written plan attached to it, describes the Onboarding: what Corkboard will set up, which information will be moved and from where, the assumptions it relies on, and the estimated schedule and fees (the "Plan"). Only the items described in the Plan are included. Anything else, including additional information, systems, features, integrations, reports, or training, requires a written change request under Section 2 of the Terms. A change request may be agreed by email.

3. CUSTOMER'S ROLE

Onboarding depends on Customer's participation. In addition to its responsibilities under Section 4 of the Terms, Customer will:

  1. Name one project contact with authority to make decisions and approve work for Customer;
  2. Respond to Corkboard's questions and requests for approval within three (3) business days;
  3. Provide exports of its information, access to its Prior System, and any cooperation needed from its prior software vendor or Odoo partner;
  4. Review test imports and the configured system, and have its key users take part in testing;
  5. Arrange training for its staff, tell them about the changes, and adopt the new workflows within its business; and
  6. Keep its Prior System, or a complete export of it, available until at least thirty (30) days after acceptance under Section 7.

If Customer's response is late, or information or direction Customer provides is inaccurate, incomplete, or later changed, the schedule is extended by the delay and the time reasonably needed to recover from it, as provided in Section 5 of the Terms, and the resulting rework is billable under Section 9.

4. MOVING CUSTOMER'S INFORMATION

Customer remains responsible for the accuracy and completeness of its information. Corkboard moves information as Customer provides it, with the mapping and clean-up described in the Plan. Before the final import, Corkboard will run a test import for Customer to review, and Customer will approve it or identify corrections. Information not listed in the Plan is not moved.

A Prior System may store information differently from the new system, so some information may not move one-for-one. Unless the Plan says otherwise, historical transactions are brought across as opening balances or summaries rather than line by line. Customer is responsible for its rights to export information from its Prior System and for ending its contracts with prior vendors.

5. MIGRATION RISKS

Customer understands that moving from a Prior System, or upgrading to a newer version, is not a simple software update. In particular:

  1. A Prior System may contain customizations, data, or connections that are undocumented, built by others, or not known to Customer;
  2. Features of a Prior System may have no direct equivalent in the new system and may need a different workflow, rebuilding, or a change request;
  3. Problems in Customer's information may only appear once it is imported and tested; and
  4. Because these conditions are often not discoverable at the start, estimates may change as they are found.

When Corkboard finds a condition that is likely to require work beyond the Plan, it will tell Customer promptly, explain the options, and give a revised estimate. Corkboard will not perform that additional work until Customer approves it in writing; approval by email is sufficient. Corkboard is not responsible for the design, code, or defects of a Prior System or of software created by anyone other than Corkboard.

6. SCHEDULE AND ESTIMATES

All dates and estimates in the Plan are good-faith estimates, not guarantees, unless the Order Form expressly states that a date is fixed. Dates move with Customer delays under Section 3, approved changes, conditions described in Section 5, and events outside Corkboard's reasonable control.

7. GO-LIVE CHECKLIST AND ACCEPTANCE

Before go-live, Corkboard will give Customer a written checklist of the Onboarding items completed under the Plan and any approved changes (the "Go-Live Checklist"). Within five (5) business days of receiving it, Customer will either (a) sign the Go-Live Checklist, accepting those items, or (b) notify Corkboard in writing of any Defects, described specifically enough for Corkboard to reproduce them.

Corkboard will correct reported Defects at no additional charge and present the corrected items again, and Customer will have a further five (5) business days to review those items only. The Onboarding items are accepted when the first of the following occurs: Customer signs the Go-Live Checklist; the review period ends without written notice of a Defect; or Customer begins using the system to run its business, other than for testing.

If the Plan divides the Onboarding into phases, each phase has its own Go-Live Checklist and is accepted on its own. Accepting one phase does not depend on any later phase.

8. WHAT IS A DEFECT

A "Defect" is a failure of an Onboarding item to conform in a material way to the Plan and any approved changes. A Defect does not include:

  1. Problems caused by the accuracy, completeness, or format of Customer's information;
  2. Conditions in a Prior System, or in code, modules, or connections created by anyone other than Corkboard;
  3. Changes made to the system by Customer or a third party, or use contrary to Corkboard's instructions or the Acceptable Use Policy;
  4. Requests for features, workflows, or results that are not described in the Plan; or
  5. Matters of preference, such as layout or wording, that the Plan does not specify.

9. FEES FOR ADDITIONAL WORK

Onboarding is billed as stated in the Order Form, as a fixed fee or by the hour. The following is billed at the hourly rate in the Order Form, in addition to the Plan: work approved under Section 5; approved change requests; and rework caused by the matters in Section 3 or excluded from Section 8. Invoices are paid under Section 6 of the Terms.

10. AFTER GO-LIVE

After acceptance, requests to change or add to the system are new work under a change request, unless they are covered by Customer's support plan. Errors in the Software itself remain covered by support and Software updates under the Order Form. Acceptance does not limit Corkboard's warranty in Section 12 of the Terms.

11. CHANGES

Corkboard may update this Schedule. Each version carries a version number and effective date, prior versions remain available at corkboardbusiness.com/legal, and a new version applies to a customer as described in the Terms. Onboarding already under way continues under the version in force when its Order Form was accepted.