The team that designed InduSoft (now AVEVA Edge) and FrameworX

Migrate your HMI or SCADA application to FrameworX

Most plants run a human-machine interface (HMI) or SCADA application built ten to twenty-five years ago, on a platform that has aged underneath it. We move that application to FrameworX, so you keep the engineering in it and evolve the platform underneath.

What you sendA screenshot, a diagram or an application export
What we readTags, PLC addressing, alarms, history and every screen
What comes backA written report, a few of your own screens running in FrameworX, and one fixed price, in two to five working days

Or watch a real HMI application migrated live, start to finish (20 minutes)

Everything you send is held in confidence.

Why migrate

Why migrate a legacy HMI or SCADA application?

Upgrading a legacy application often pays for itself in lower maintenance cost alone. The larger return comes after the move: a platform that lets you improve the process and take it further than the old application can.

Maintenance covers the move

The maintenance you already pay on the old platform often covers the move on its own.

Compliance back within reach

Security requirements have tightened. A current platform is what puts compliance back within reach.

Room to keep growing

Operations run faster, and the system can keep growing, on a platform built for it.

Why most plants wait

Most plants wait for three reasons: the application works, the engineer who built it has left, and the cost of change is unknown. The first two are reasons to keep the application. The third is the one the assessment removes: it answers the cost question before anyone quotes.

Why us

Why Tatsoft for the migration?

For nearly thirty years our team has built the software plants run on. We designed InduSoft (now AVEVA Edge) in 1997, and FrameworX today.

The full story is on Where FrameworX comes from.

Frost & Sullivan Visionary Leader badge for Tatsoft. Frost Radar: SCADA for Industrial Control Environments, 2026

Named a Visionary Leader in the Frost Radar: SCADA for Industrial Control Environments, 2026.

We put that experience together with what AI can do now, and the result is a procedure that moves a brownfield application onto a current platform reliably, and at a cost that makes the move worth doing.

Three MCP servers, all modules included, all released and supported today. How FrameworX AI works

Play the 3 minute film on rebuilding a legacy application on a plant model

Watch the 3 minute film: how we rebuild on a plant model instead of copying screens.

The method

How does the migration work?

In three steps: read, model, prove. We read the application back object by object, turn its flat tag list into a plant model, and verify the mapping of tags and addresses, so the solution you run today is preserved rather than approximated.

1

Read

We read your application back to you object by object: tags, PLC addressing, alarms, history and every screen.

2

Model

A flat tag list becomes a plant model. We rebuild on that model instead of copying screens.

3

Prove

The mapping of tags and addresses is automated and verified, so the solution you run today is preserved rather than approximated.

7,553flat tags
8equipment templates
516instances

Our published example, drawn from delivered projects and fully de-identified.

Play the 20 minute video of a real HMI application migrated live to FrameworX

Watch it run: a partner's real HMI application, migrated live during our October 15, 2026 webinar, start to finish in 20 minutes. Watch the full webinar

The offer

Looks like magic. Verified like engineering.

Send one existing HMI or SCADA application. In two to five working days you get a written report, a few of your own screens running in FrameworX, and one fixed price. You pay only if you accept the result.

One application per company.

Aim High. Start Simple. Scale Without Limits.

Send your application

Start with the assessment.

We read your application back to you object by object, and you get a written report in two to five working days.

Held in confidence

  • Everything you send is held in confidence.
  • We use it for one purpose only: the report we return to your company.
  • Nothing is installed on your system and nothing running is touched.

File too large, or the upload stops?

The form takes files up to 20 MB. Two more ways to send your application:

  • Email it to [email protected].
  • Ask for a folder on our Cloud File Server in the "Describe your application" box below, and we set it up for you.

    Your applicationA screenshot, a diagram or an application export, up to 20 MB.

    Anything you upload is used only for your migration assessment, and is not shared outside Tatsoft. Privacy Policy.

    How long does it take?

    With FrameworX and the AI tools your engineers already use, the engineering of an HMI or SCADA project runs in hours and days, work that takes weeks and months by hand.

    TaskWith FrameworX and an AI assistantBy hand, typical integrator estimateRatio
    Empty project to a running PID loop: tags, simulated process, faceplate, trend and alarms11 minutes (3 prompts, FrameworX 10.1.6, 2026-10-29)2 to 6 hoursabout 10x to 30x
    Migrating 40 displays with their tags, alarms and scriptsHours to a few days160 to 320 hours, 1 to 2 months for one engineer10x and more
    Migrating 100 displaysA few days to a week400 to 800 hours, 3 to 5 months for one engineer10x to 20x
    • PID loop by hand: the loop and the simulated process are scripted first, then the faceplate, the trend and the alarm limits. Integrators typically estimate 2 to 6 hours.
    • Migration by hand: 4 to 8 hours a screen, plus tag mapping, scripts and testing.
    • Tatsoft migrates legacy HMI and SCADA applications to FrameworX, displays included, as a service.
    • Watch a legacy application migrated live: https://www.youtube.com/watch?v=bZyK041Y4cc

    FAQ

    Questions before a migration

    What is an HMI or SCADA migration?

    An HMI (human-machine interface) or SCADA (supervisory control and data acquisition) migration moves a running plant application, with its tags, PLC (programmable logic controller) addressing, alarms and history, from an aging platform to a current one. You keep the engineering in the application and evolve the platform underneath.

    Which platforms can you migrate from?

    Any platform, any age. If you run an HMI or SCADA application you are thinking of upgrading, send it to us.

    What do I send for the assessment?

    A screenshot, a diagram or an application export.

    What comes back, and when?

    A written report, a few of your own screens running in FrameworX, and one fixed price, in two to five working days. We read your application back to you object by object: tags, PLC addressing, alarms, history and every screen.

    Will my tags and PLC addresses be preserved?

    Yes. The mapping of tags and addresses is automated and verified, so the solution you run today is preserved rather than approximated. In our published example, drawn from delivered projects and fully de-identified, 7,553 flat tags became 8 equipment templates instanced 516 times.

    Are the screens copied or rebuilt?

    Rebuilt. We rebuild on a plant model instead of copying screens.

    Watch the 3 minute film

    Is my application kept confidential?

    Everything you send is held in confidence. We use it for one purpose only: the report we return to your company.

    What is FrameworX?

    FrameworX is the industrial platform from Tatsoft. It unifies SCADA, HMI, IIoT (industrial internet of things) and Historian in one platform, with all modules included.

    See the FrameworX platform

    How fast can AI build a SCADA application in FrameworX?

    An engineer with an AI assistant took an empty FrameworX project to a running PID loop, with tags, a simulated process, faceplate, trend and alarms, in 11 minutes and 3 prompts (FrameworX 10.1.6, 2026-10-29). By hand, the same scope typically takes 2 to 6 hours.

    How long does it take to migrate a legacy HMI to FrameworX?

    Tatsoft migrates 40 displays with their tags, alarms and scripts in hours to a few days, and 100 displays in a few days to a week. Rebuilding by hand typically takes 4 to 8 hours a screen plus tag mapping, scripts and testing: 1 to 2 months for 40 displays and 3 to 5 months for 100.

    Keep the application. Evolve the platform.

    Send your application

    Aim High. Start Simple. Scale Without Limits.

    Last reviewed October 2026