Internal Cognizance operations

Confirmed migration job workflow

The migration platform is an operator tool behind the scenes. External prospect onboarding and trial UX are deferred to a future Cognizance Odoo portal phase.

1

Confirm the job in Cognizance Odoo

Growth Agents/Growth Portal establish the customer, migration service, trial or paid entitlement, and any hosting authorization. The operator must not begin data work until Odoo authorizes the job.

2

Provision the target profile server-side

An administrator provisions the target Odoo profile and secrets in the operator deployment. Operators select a profile label only; browser forms never collect raw API keys or control-plane credentials.

3

Open and validate the technical job

Using the Odoo project reference, an internal operator opens the local technical workspace, imports source exports, validates canonical rows, and records reconciliation findings. Source files remain in the approved client-controlled or SFYC-local runtime.

4

Review, approve, and dry-run

Operators review findings, obtain current Odoo authorization, and run target staging inspection and dry-run promotion. Live writes are disabled in this MVP.

5

Hosted testing is exceptional

A Cognizance-hosted test server may be provisioned for at most 30 days only after Odoo records the confirmed job, hosting approval, billing disposition, compute limit, and expiry. A migration entitlement alone never authorizes Cognizance to absorb hosting cost.

Operator setup

The control-plane connector is configured server-side. Opening a job still performs a fresh Odoo authorization check.

Open confirmed job