How long does a system assessment take?

Typically 4-8 weeks depending on system complexity. An AS/400 with 20 years of customization takes longer than a 5-year-old packaged ERP. We scope the assessment based on the system and your modernization goals.

What if we have no source code access?

We can work from the running system -- tracing data flows, testing scenarios, and observing behavior. Source code accelerates the process, but we have methods for black-box analysis when code isn\'t available.

Do we need this if we\

Especially if you\'re replacing the entire system. The #1 cause of failed migrations is discovering critical business logic mid-project that wasn\'t accounted for. Assessment prevents that.

Legacy Modernization · Assessment

Understand your legacy system before you try to replace it.

Q: Can your documentation be used by other implementation partners?

Yes. We deliver structured documentation you own -- business process maps, data dictionaries, integration catalogs, and risk assessments. If you want to use the assessment output to guide implementation, it\'s yours.

Most legacy modernizations fail because nobody fully understands what the old system actually does. We reverse-engineer your legacy system\'s business logic, data flows, and integrations -- creating documentation that probably never existed.

Begin Assessment All Services

The Problem

Nobody Fully Understands the System You\

✕Original developers are retired or gone -- institutional knowledge walked out the door

✕Documentation is outdated, incomplete, or never existed in the first place

✕Business logic buried in thousands of lines of RPG, COBOL, or custom code with no comments

✕Hidden integrations and file transfers that nobody remembers until they break during migration

What We Deliver

Service Scope

Business Logic Extraction

Reverse-engineer business rules from running code -- pricing logic, order workflows, allocation rules, and approval chains. Document what the system actually does, not what someone thinks it does.

Data Model Documentation

Map every table, field, relationship, and data flow. Identify master data, transactional data, and the transformations between them.

Integration Mapping

Discover and document every integration -- file transfers, API calls, database links, email triggers, and manual handoffs. Nothing gets missed during migration.

Dependency Analysis

Identify upstream and downstream dependencies -- which systems feed data in, which systems consume data out, and what breaks if something changes.

Technical Debt Inventory

Catalog customizations, workarounds, dead code, and technical debt. Distinguish between logic that must be preserved and logic that can be retired.

Knowledge Base Delivery

Deliver a structured, searchable knowledge base -- not a 500-page PDF. Living documentation that your team and vendors can reference throughout the modernization.

How We Work

Engagement Process

Stakeholder Interviews

Interview power users, IT staff, and business process owners. Capture tribal knowledge before it disappears.

Code Analysis

Analyze source code, database schemas, and configuration files. Automated tools plus manual review for complex business logic.

Data Flow Tracing

Trace data from entry point through every transformation to output. Map the complete lifecycle of critical business objects (orders, inventory, customers).

Integration Discovery

Scan for file transfers, scheduled jobs, API calls, and database connections. Verify each integration with source and target system owners.

Documentation Delivery

Compile findings into a structured knowledge base with business process maps, data dictionaries, integration catalogs, and risk assessments.

Common Questions

Frequently Asked Questions

Work with Metrotechs

Every engagement starts with an assessment.

Not a proposal. Not a sales call. We tell you what we find, not what you want to hear. The Launchpad assessment maps your operation before any software work begins.

Begin Assessment Talk to the team