Platform modernization
A controlled move from legacy systems to a supported platform, with data integrity and service continuity protected. Migration, integration, cutover and decommissioning run as one piece of work, and the old system stays in service until the new one is accepted.
- Typical length
- Four to nine months, discovery included
- Platforms
- Dynamics 365, Salesforce, ServiceNow, SAP, Oracle, Power Platform and custom builds
- Investment basis
- Fixed price discovery, build confirmed after it
01 In practice
From the current system to the new one
Example. The actual design is set during discovery.
02 Who it is for
- A line of business system that is out of support or no longer fits how you work
- Several overlapping applications that should become one
- A move from on premises software to a cloud platform you have already chosen
- A platform decision made, with no internal team free to run the migration
03 What you get
- 01
Current state inventory
Applications, data, integrations, users and the processes that depend on them.
- 02
Target design
The platform configuration, data model and integrations the new system needs.
- 03
Migration plan and rehearsals
Data mapping, trial loads and a reconciliation report for each rehearsal.
- 04
Cutover runbook
The steps, owners, timings and the rollback point for go live.
- 05
Released system
Built in a mirror of your environment, released from a gold copy with a release record.
- 06
Decommissioning record
What was retired, when, and where its data now lives.
04 Investment
Indicative investment
Canadian dollars, before tax. Confirmed after discovery, based on complexity, integration requirements, delivery scope and your environment.
Scope assumptions. The lower end is one application replaced on a platform you already license. The upper end is several connected systems consolidated, with more data to migrate and more integrations to rebuild.
05 How we deliver
One consistent approach, set for this work
Discover
Inventory of the current estate, target platform fit, a data quality sample, the migration approach and a priced statement of work.
Build
Configuration and development in a mirror environment, integrations, data migration rehearsals and user testing.
Release
Final data load, parity check against the old system, cutover and your sign off on the release record.
Run
A handover to your team, a fixed transition period of close support, or a monthly service for scheduled releases and support hours.
06 What we need from you
- A named business owner and a technical contact
- Administrator access to a non production copy of the current system
- Licences for the target platform, or a decision on who procures them
- Time from the people who use the system today, for testing
07 Start
Discuss your project
Tell us what needs to change and when. If the work fits, we propose a fixed price discovery.
