ToolTwistSpeak With Us

International BPO CompanyMapped what a legacy platform really does before migrating off it

The Challenge

The company’s OutSystems applications support recruitment, onboarding and employee operations across multiple countries. Moving them requires a clear account of the business rules, integrations, access controls and data responsibilities the replacement must preserve. With code spread across hundreds of repositories, that picture was difficult to assemble. The assessment set out to answer three questions.

  • What should be retained or changed?Activity, dependencies and review coverage needed to be visible together. Recent code changes alone could not establish production use.
  • What behaviour must carry across?A business journey could cross applications, services, message queues and data stores, with important permission and failure paths.
  • Where should migration effort start?Business dependencies and risk needed to inform priorities alongside the product roadmap.

The Solution

The target stack pairs Flutter interfaces written in Dart with TypeScript services and APIs. ToolTwist combined automated code analysis with targeted source review to support migration planning.

  • Map the existing software.Record activity, dependencies, review depth and connections between older and newer components.
  • Trace selected workflows.Follow requests, data, permissions and failure paths to document the behaviour that migration decisions must address.
  • Identify simplification options.Examine duplicated rules, overlapping responsibilities and messaging handoffs before carrying them into the replacement.
  • Make migration decisions explicit.Separate proposed fixes from owner questions, including data reconciliation, release compatibility and rollback requirements.

ToolTwist’s Role

ToolTwist is supporting the migration through discovery, source tracing, architectural review and migration planning. The assessment remained read-only. An offline explorer brings together application maps, workflow diagrams, risks and supporting source references. Review coverage and unresolved decisions remain visible so that a focused trace is not mistaken for a complete audit.

Impact

At the assessment stage:

  • A shared migration reference.Developers, business analysts and technical leaders can explore the relationships and selected workflows recorded in the assessment.
  • A clearer improvement backlog.A consolidated risk register and follow-up plan distinguish proposed fixes, simplification options and open owner decisions.
  • More explicit data responsibilities.Maps of selected reads, writes and shared structures highlight ownership questions to resolve before migration and cutover.

The migration is ongoing. The assessment provides a basis for prioritising investment and defining what the replacement must preserve or improve.

More stories