Boldo Logo

Application migrations: what derails is what nobody mapped

An ERP or CRM project rarely derails on the target solution. It derails on the existing landscape: forgotten interfaces, duplicated data, dependencies discovered too late. Boldo gives the project team the view they need to scope the trajectory and prepare every cutover.

Migration starts with understanding the existing landscape

By 2027, more than 70% of recently implemented ERPs will fail to fully meet their business case goals (Gartner, 2023). The difficulties often appear well before the cutover: incomplete inventory, interfaces discovered late, unclear responsibilities and decommissioning pushed back.

The difference is made from the scoping stage, on real knowledge of the applications, flows, data, contracts and teams involved.

This knowledge makes it possible to define a realistic scope, identify blocking dependencies and build a trajectory grounded in facts. That is precisely the purpose of IT mapping.

What is often discovered too late

  • Interfaces missing from the initial inventory
  • Data duplicated between the old and the new system
  • Dependencies known to only a handful of experts
  • Applications forgotten in the first cutover batches
  • Contracts and licenses kept after the migration
  • Decommissioning pushed back quarter after quarter

Different dependencies depending on the solution migrated

ERP, CRM or data platform: each project has its own scope, but all of them require understanding the applications, flows and teams involved.

  • ERP solution logos: SAP, Odoo, Cegid, Sage, Epicor, Microsoft Dynamics NAV, Infor and NetSuite
    ERP

    Cross-functional processes, numerous interfaces and a direct impact on the company's operations.

  • CRM solution logos: Salesforce, Zendesk, SugarCRM, Zoho, HubSpot, Oracle Siebel, Microsoft Dynamics 365 and Pega
    CRM

    Usage spread across marketing, sales and customer service, with data exchanged throughout the IT landscape.

  • CDP platform logos: Twilio Segment, Imagino, Blueshift, Brevo and DinMo
    CDP

    Multiple sources, complex matching rules and strong dependencies around customer data.

A map useful at every phase of the migration

Boldo connects the existing landscape, the target and the intermediate states in a single base. The map thus supports the project from scoping through to the final shutdown of the old system.

  1. Scoping: define the real perimeter

    Inventory the applications, interfaces, data, contracts, users and owners involved. The scope is built on verified information, and the first redundancies or inconsistencies can be identified before the target is finally chosen. Need to speed up the baseline? Our IT mapping service kicks off the process with you.

  2. Preparation: represent the existing landscape, the target and the intermediate states

    Document what exists today, what must disappear, what must be created and the steps needed to move from one state to the next. Dependencies help identify the prerequisites and blocking points of each batch.

  3. Execution: build the cutover batches

    For each wave, identify the applications, flows, data, teams and constraints involved. The dependency map clarifies the project sequencing and limits late discoveries during execution.

  4. After the cutover: track decommissioning

    A migration is only finished when the old system and its residual dependencies are handled. Track the assets to retire, the flows to shut down, the data to archive and the contracts or licenses to close.

Cutover batches
IS cartography diagram centered on SAP R/2 ERP with its integration flows

Build batches on real dependencies

Typed relations connect the applications, flows, data, technologies and teams. You start from an asset to migrate, walk through its dependencies and identify what must evolve with it.

For each batch, you see the prerequisites, the elements involved and the dependencies with other waves. The map does not replace the plan: it gives it a more reliable perimeter.

  • Identify blocking dependencies before the cutover
  • Group the assets that must evolve together
  • Spot the flows to keep running temporarily
  • Document the exit criteria of each step

Business teams on board, not just informed

An ERP or CRM change alters the processes and habits of several teams. A complete technical view is not enough to explain these impacts to each stakeholder.

Filtered inventories, diagrams and 360 pages are built from the same base. You adapt the reading to the business area concerned without rebuilding the data for each workshop.

Understandable views make discussions easier and let each team gauge the changes that concern them.

Business impacts
Boldo screenshot displaying an onboarding dashboard with a dependency graph, bar chart of costs and a star-rated asset list
Risks
Boldo screenshot of a cyber risk analysis linking VPN, IAM Entra ID and Phished to threats affecting CRM Sales and Team Sales, with a Salesforce detail panel

Connect risks to the assets involved

Obsolescence, duplicated data, tight dependencies or contracts to renew: sensitive points can be modelled and connected to the applications, flows and teams involved.

You assign an owner, a criticality and a status to each risk according to your own metamodel. Dedicated views then let the project committee track open points and how they evolve.

  • Identify the assets exposed by each risk
  • Assign monitoring responsibilities
  • Prioritise sensitive points by criticality
  • Share an up-to-date reading with the project committee

Reuse the data you already have

The first baseline often exists as application files, interface matrices, CMDB exports or project documents. Boldo lets you gradually reuse this material without re-entering everything.

  • Files

    CSV / XLSX import

    Map the columns to properties and relations, choose a stable key and preview the changes before validating them.

  • Programmable

    REST API v1

    Set up the synchronisations you need when some sources must keep feeding the map during the project.

  • Contribution

    Validation by the teams

    Give application and business owners the rights they need to verify and enrich the information within their scope.

Clear pricing throughout the migration

Plans start at €39 per editor per month, with a 14-day free trial. Project team members, owners and readers get rights suited to their role and their scope.

See pricing

Frequently asked questions about application migrations

Boldo lets you structure the applications, flows, data, technologies and responsibilities needed for ERP, CRM, CDP, PIM or specific business tool projects.

The metamodel adapts to the scope, vocabulary and phases specific to each project.

Scope your next migration on facts

See how to map the existing landscape, build the cutover batches and track the decommissioning of your ERP, CRM or CDP project.

Schedule your demo

30 minutes devoted to your migration project.

By submitting this form, you agree to our Privacy Policy.