Assess without touching production
Export a read-only schema and anonymized migration profile. We map supported objects and flag missing dependencies before a change window exists.
PBX MIGRATION · CONTROLLED PROCESS
Move from FusionPBX or VitalPBX without a blind cutover.
See what will move, what needs a decision and how to return to the starting point before configuration is applied to an isolated RelayPBX target.
Dry run firstExplicit conflicts and exclusionsRestore checkpoint before change
FOUR STAGES
A decision based on evidence, not hope.
Every stage produces a reviewable result. You can stop without changing the PBX that carries production calls.
Run a dry migration
The importer validates tenants, extensions, routes and destinations, then reports conflicts without applying them to the target PBX.
Review the evidence
You approve the object counts, mappings, exclusions and rollback checkpoint. Secrets, recordings and CDR data remain excluded unless separately scoped.
Apply and validate
The approved plan is applied to an isolated target. Registration, internal calls and selected inbound and outbound routes are accepted before cutover.
Configuration you can verify.
- Tenants, users and extensions
- Trunks, DIDs and call routing
- IVRs, ring groups, queues and time conditions
- Explicit report of objects that need a manual decision
Sensitive data does not move by accident.
- SecretsEntered again without copying passwords from the export.
- RecordingsSeparate scope, capacity and retention review.
- CDRHistorical records are planned separately from configuration.
START WITH AN ASSESSMENT