Your old system, mapped for you, before you approve anything.
Architect is what Ori does during onboarding. It connects to the CRM or spreadsheet you already run on and proposes a field-by-field mapping onto the Version X schema. Your admin approves, adjusts or rejects it. Nothing commits until it is confirmed.
Availability · Self-serve import on Launch, guided from Scale, white glove on Suite
- 01
Ori reads the existing system
It connects to the legacy CRM or spreadsheet and proposes a field-by-field mapping onto the Version X schema, flagging the ones it is not sure about rather than guessing quietly.
- 02
Your admin reviews, rather than re-does
The mapping arrives as a proposal to approve, adjust or reject, not a blank migration form. Their job is verification, not data entry.
- 03
Nothing commits until it is confirmed
The same rule as everything else Ori does: multi-step actions run through approval gates, never silent writes.
Questions.
Is Architect a separate AI from Ori?
No. Architect is what Ori does during onboarding, the same AI doing one job. Version X has one AI character on purpose, and giving the migration flow its own identity would undo that.
How much does migration cost?
Nothing, on Scale and above, where guided migration is included. This is the direct answer to HubSpot’s $1,500 to $7,000 onboarding fee: a services team doing the same mapping by hand, billed separately, is exactly what Architect does as software.
What if I want you to just do it?
A fully managed migration, where our team runs it rather than guiding you, is a separate service starting at €5,000 and priced by the scale of the engagement above that. Still materially cheaper than a typical Salesforce or HubSpot implementation.
Why is Launch self-serve import rather than guided?
Because a five-person team’s data is light enough that guided mapping is more ceremony than it is worth. Guided migration starts at Scale, which is the company this feature was built for.