Skip to main content
The Migration Hub is the pre-signature workspace for a Nostos engagement. It gives the buyer, finance, product, technical, legal, and support stakeholders one async room for the case, approvals, documents, and next actions, without requiring every stakeholder to join every call. After signing and pilot payment, the engagement moves into the Migration Dashboard, the Nostos operating surface for onboarding, cohort progress, go-live readiness, reporting, and program operations.

​
What it contains

Migration economics

Audit outputs, hub analysis, case assumptions, cohort view, and recovery model.

Program scope

Pilot scope, first cohorts, guardrails, operating cadence, and owner assignments.

Stakeholder approvals

Role-specific approval prompts for finance, technical, legal, product, support, and executive stakeholders.

Commercial documents

Agreement, pilot payment, onboarding items, and next-action history.

​
Access model

Hub access is intentionally controlled. The room owner receives an owner-specific link. Other stakeholders request access with their email address. The owner can approve or deny access, then assign roles and approval responsibilities. This matters because the signing and pilot-payment action often falls to the room owner. The room link should not become open access for every forwarded recipient.

​
Role-aware views

Each stakeholder sees the same core program, but the hub emphasizes their work:
  • Finance sees pricing, timing, payment triggers, and model assumptions
  • Technical sees integration, access continuity, data requirements, and readiness
  • Product sees subscriber experience, policy posture, and app-access continuity
  • Support sees expected inbound, macros, cancellation guidance, and escalation paths
  • Legal and procurement see terms, data handling, vendor posture, and portability

​
Thea assistant

The Migration Hub includes Thea, an AI-powered assistant for the pre-signature workspace. Thea helps stakeholders find the right context, understand open tasks, and prepare approvals. It supports the workflow; Recurr remains accountable for the program, recommendations, and commercial documents.

​
Finance deliverables

For finance, the Migration Hub should make the commercial case reviewable without a separate spreadsheet archaeology project. It includes:
  • Model assumptions and migration cases
  • Eligible subscriber base and cohort view
  • Pilot fee and credit treatment
  • Migration fee basis and due point
  • Oikos first-year treatment for migrated subscribers
  • Payment processing and tax assumptions
  • Cash-flow timing assumptions
  • Fee reconciliation basis
  • Reporting and export expectations

​
Optional meeting path

The hub is async-first, not meeting-only. A meeting with the Recurr team remains available where a stakeholder wants to talk through the numbers, integration, or approvals.