Three moves from estate
to migration.
Connect your system, run AI intelligence in Claude, then migrate with confidence. ORION stays out of your way — it is the system of record, not another chat window.
Connect
Add your HaloITSM or ServiceNow environment using the official MCP connector. Credentials are stored as references to the secret vault — only the last 4 characters are ever displayed.
- HaloITSM MCP / ServiceNow MCP
- Credentials as vault references
- Connection test before anything else runs
Intelligence
Open Claude Desktop or Cowork. ORION grounds answers in your live data plus T1 best-practice and T2 vendor knowledge. Every conversation is logged with a four-verb audit.
- Headless — runs in your existing Claude
- Grounded in T1/T2/T3 knowledge
- Read-only audit: explain · route · unlock · act
Migrate
Configure a job, dry-run against canonical field mappings, then promote to live. Records process one by one with pause / resume. Post-validation must pass before the job is marked complete.
- Canonical SN ↔ Halo mapping templates
- Dry-run required before live
- One running job per project, per-record status
What you'll need
Admin credentials for the HaloITSM or ServiceNow instance you want ORION to read and write through.
Claude Desktop or Cowork — that is where your team will actually ask, route, and act. ORION never renders a chat panel.
That is roughly how long it takes to create a tenant, connect the first adapter, and run your first session.