Migration services
Move from your legacy platform with zero program disruption.
Whether you are migrating from spreadsheets, Fusion Risk, Archer, or a first-generation BCM tool — eBRP’s structured migration service maps your existing assets, validates your data, and keeps your program operational from day one to go-live.
Migration — what moves across
Business units & organizational structure
Migrated
PPTDFS asset inventory & dependencies
Re-mapped
BIA data & RTO/RPO parameters
Validated
Business continuity & DR plans
Converted
Contacts, teams & responder assignments
Imported
Exercise history & audit records
Case-by-case
Structured delivery
Five phases. Continuous program operation throughout.
Every eBRP migration follows a structured five-phase model — built to eliminate the disruption risk that stops many organizations from moving off legacy platforms.
01
Phase
Legacy program audit
We assess your current platform — plan inventory, BIA parameters, asset records, organizational structure, and compliance mappings. eRMA is used to identify gaps in the legacy program before migration begins, so you move forward, not sideways.
Plan inventoryBIA data reviewAsset catalogueGap identificationMigration scope
02
Phase
PPTDFS entity re-mapping
Legacy asset records are mapped to the eBRP PPTDFS model — People, Premises, Technology, Data, Functions, Suppliers. Dependencies are structured correctly, risk assessments are transferred, and the organizational hierarchy is built to match your current structure.
Entity mappingDependency structuringRisk transferOrg hierarchy
03
Phase
Plan conversion & data validation
Existing BC, DR, and Crisis Management plans are converted from their legacy format into eBRP’s executable playbook structure — sequenced tasks, responder assignments, and predecessor dependencies. All data is validated before the parallel run begins.
Plan conversionTask sequencingResponder assignmentData validation
04
Phase
Parallel run
Both platforms run simultaneously for an agreed period — typically 4–8 weeks. Your program team operates from eBRP Suite while the legacy platform remains available as a reference. Any discrepancies are resolved before decommission. Program continuity is guaranteed.
Dual operationDiscrepancy resolutionTeam familiarizationConfidence building
05
Phase
Cutover, training & handover
Legacy platform decommissioned. Administrator and stakeholder training completed. A validation exercise run in CommandCentre confirms the migrated program is operational. Full documentation and a 12-month program maturity roadmap delivered at handover.
Legacy decommissionAdmin trainingValidation exerciseYear 1 roadmap
Platforms we migrate from
We have seen what you are working with.
Our migration team has experience transitioning programs from every major legacy BCM platform and format. If your platform is not listed, it does not mean it is not supported — contact us to discuss your specific situation.
Migrating from
Spreadsheets & manual tools
The most common starting point. BIA data, plan documents, and contact lists in Excel or Word. eBRP provides structured data import templates and guided data entry to migrate content efficiently.
Migrating from
Fusion Risk Management
Entity records, process hierarchies, BIA parameters, and plan content exported from Fusion and re-structured into the PPTDFS model. Compliance mappings transferred where applicable.
Migrating from
Archer (RSA)
GRC and risk register data migrated from Archer’s application-centric model into eBRP’s entity-embedded risk architecture. Plan and BIA content converted to executable format.
Migrating from
ServiceNow BCM module
Business impact data, process records, and recovery tasks extracted from ServiceNow and migrated into eBRP Suite’s dedicated BCM/GRC lifecycle environment with unlimited user licensing.
Migrating from
Sungard / Assurance
Legacy Sungard and Assurance CM platform data — including plan content, contact trees, and exercise records — mapped to PPTDFS entities and converted to eBRP executable plan format.
Migrating from
Other platforms
Any BCM platform that allows data export can be migrated. Contact us to discuss your specific platform, data volume, and timeline. We scope each migration individually.
What we guarantee
Three commitments every eBRP migration delivers.
Zero program downtime
The parallel run phase ensures your BCM program remains operational throughout migration. No gap between platforms. No period of reduced readiness.
All data validated
Every record migrated is validated before cutover — BIA parameters cross-checked against source, plans reviewed for completeness, responder assignments confirmed.
Forward, not sideways
Migration is not just a platform change — it is a program improvement. eRMA identifies gaps in your legacy program during audit, so you arrive in eBRP with a better program than you left behind.
Common migration questions
What to know before starting.
How long does a migration typically take?
Three to six months from kickoff to full cutover, depending on program complexity, data volume, and the number of plan types being migrated. The parallel run period (Phase 4) is usually 4–8 weeks. We scope timelines individually at the start of every engagement.
Can we do a proof of concept before committing to migration?
Yes — and we recommend it. A POC lets you validate eBRP Suite against a representative subset of your data before committing to a full migration. POC data carries forward, so the time is never wasted. See our Proof of Concept service for details.
Do we need to clean up our legacy data before migrating?
Not necessarily. The Phase 1 audit identifies data quality issues before migration begins. Our team has seen every kind of legacy data condition — we will advise on what to clean up, what to migrate as-is, and what to leave behind rather than importing outdated records.
What happens to our existing compliance evidence and exercise records?
Historical exercise logs and audit evidence are handled on a case-by-case basis. Where data can be exported from the legacy platform in a structured format, we assess what is worth migrating. In most cases, historical records remain accessible in the legacy platform for reference while the active program moves forward in eBRP.
Is the unlimited licensing model available from day one of migration?
Yes. eBRP Suite’s unlimited user licensing applies from the moment your subscription or perpetual license begins. There is no per-seat cost at any stage — including during the parallel run period when both platforms are active.
Ready to move off your legacy platform?
Talk to our team about your current platform, data volume, and program complexity. We will scope a migration plan that eliminates the risk of moving and gets you to a better program on the other side.