Build starts when three things have all arrived: the signature, the audited revenue, and the onboarding form. From there the proposed targets are five working days for the form, five for design and sign-off, and five for the build — ten with Live DR. Private connectivity, customer-managed keys and extra environments can stretch the build.
Start the customer’s network and DNS work in parallel with contracting. It is usually the longest lead item, and it is not on TRANXACT’s side of the line.
The onboarding form
| Before signing | Within 5 working days of kick-off |
|---|---|
| Cloud provider and regions | Private /22 ranges (and DR), connectivity option, egress allow-list |
| Runtime sizing and environments | FQDN, DNS owner, public-CA certificate |
| Database engine and size | IdP for SSO, admin users, MFA policy |
| Continuity pattern | Bank, payroll, tax, BI and legacy endpoints |
| Modules, entities, currencies, languages | Contacts per area, and two 24×7 contacts |
| Compliance flags; ASK tier, region and budget |
- Region, address ranges, FQDN and database engine are fixed once the build starts.
- The technical contact is an IT lead who can act on credentials and network changes — not a CxO, finance or procurement contact. Credentials go to them and nobody else.
- Every open input is tracked in the fortnightly operations sync until handover.
Identity, then data
Kick-off walks the support manual and portal, the scope, and the R&R workbook, RACI and escalation matrix. SSO is federated with the customer IdP over SAML 2.0 or OIDC, SCIM if wanted. Test SSO and role mapping with real users before migration starts — access problems otherwise surface at go-live. Allow-list TRANXACT sender domains so provisioning and alert emails are not quarantined.
The migration cockpit
| Step | Who |
|---|---|
| Extract from legacy systems and spreadsheets | Customer (MIG_8.3.01) |
| Map to TRANXACT entities, accounts, master data; cleanse | Customer (MIG_8.3.02) |
| Validate — rules, duplicates, missing data | TRANXACT (MIG_8.2.01) |
| Trial loads into non-production, repeated | TRANXACT; beyond the agreed cycles, Additional (MIG_8.2.02) |
| Reconcile trial balance, sub-ledgers, stock; sign off opening balances | Customer (MIG_8.3.03) |
| Cutover plan and freeze window | Joint (MIG_8.4.01) |
| Go / no-go | Customer (MIG_8.4.02) |
| Final load and technical verification | TRANXACT (MIG_8.4.03) |
Data quality, not tooling, sets the go-live date. Every opening balance reconciles to the audited source before go-live.
The go-live gates
- Migration reconciled and signed off.
- Integrations tested with the partners’ test endpoints.
- A Live DR switchover drill passed.
- A clean-room restore from the vault passed.
After go-live, hypercare — daily check-ins, typically 4–8 weeks — is available as the H1 package.
Calderwood signs on a Monday. Its form arrives on day 4, complete except the Live DR address range, which arrives on day 9 — four days after the 5-day target. Design cannot be signed off without it, so sign-off and the committed handover both move back four days. And the build after sign-off is ten working days, not five, because Calderwood has Live DR.
Try it Calderwood’s CFO wants to fix the go-live date on the day of signature. What should the Orchestrator say?
Commit a go-live date only after the handover date is fixed and the migration plan is sized. Go-live depends on data quality and on four gates — reconciliation, integrations, a switchover drill and a clean-room restore — none of which can be dated before the environments exist.