02 — HOW IT WORKS
Four steps, from export to signed delivery.
No black box and no discovery workshop. You send a project export, you get back an inventory and a fixed quote, and only then does anything get converted. This page describes the whole path, in the order it actually happens.
02 — HOW IT WORKS
Four steps, from export to signed delivery.
- 01
Send your project
A project export is enough: .movprj + resources (Movicon 11), .UFProject folder (Movicon.NExT), gateway project export (Ignition). Everything under NDA; files deleted after delivery.
- 02
Free compatibility scan
Within 48 hours you get a scan report: object inventory, what converts automatically, what will need manual work, and a fixed quote. No commitment.
- 03
Conversion
The engine converts tags, UDTs, screens and graphic components, alarms (including activation delays), scripts, device connections, historian configuration, trend views, recipes, schedules, and users/roles — never their passwords.
- 04
Verification & handover
Automated equivalence testing compares source and target object by object, then a signed certificate seals the result. You receive the converted project plus every report — no black box.
05 — WHAT TO SEND
Accepted project formats.
| Movicon 11 | .movprj + resources folder (images, recipes, users) |
|---|---|
| Movicon.NExT | the whole .UFProject folder, zipped |
| Ignition (Perspective) | gateway project export (.zip) or the projects/ folder |
| VB6 legacy HMI | source tree: .vbp, .frm, .bas, .cls |
| zenon | project backup or the exported workspace |
| Not sure | send what you have — the scan tells you what is missing |
04 — WHAT GETS CONVERTED
The inventory, in full.
- 01Tags & UDTs
- 02Alarms with activation delays
- 03Screens & graphic components
- 04Scripts (translated where possible, flagged where not)
- 05Device/driver connections (documented for recreation)
- 06Historian config (retention, deadband) + data export CSV
- 07Trend views
- 08Recipes
- 09Schedules
- 10Users & roles (credentials never migrated)
From a real run: 91 tags, 10 alarms, 4 screens, 158 graphic components, 2 scripts — converted and verified in one pass.
06 — TIMELINE
What a typical project looks like in time.
Day 0 — files received
Transfer over an encrypted channel, NDA signed on request. Files are inventoried, never opened on a plant network.
Day 1–2 — scan report
Object counts, coverage per category, the rework list and a fixed price. You decide with the numbers in front of you.
Day 3–7 — conversion
Engine run, manual review of everything the engine flagged, target-side sanity pass on screens and alarms.
Handover
Delivery folder with converted project, reports, certificate and shadow file. 30 days of email support on the delivered artifacts.
08 — WHAT YOU RECEIVE
The delivery folder
| ├─ project/ | converted, ready to import |
| ├─ CONVERSION_REPORT.md | every object · every decision · rework list |
| ├─ EQUIVALENCE_REPORT.md | 157 checks, object by object |
| ├─ EQUIVALENCE_CERTIFICATE | signed, SHA-256 sealed (.json + .html) |
| ├─ SECURITY_REPORT.md | ISA/IEC 62443 · CRA findings |
| ├─ SBOM.cyclonedx.json | toolchain bill of materials |
| ├─ screen_previews/ | every screen rendered as HTML — |
| │ | review the result with no software installed |
| └─ project.shadow.scdx | lossless round-trip file |
Open the screen previews in any browser and compare them with your plant, before you even install the target platform.
WHO CONVERTS YOUR PROJECT
One engineer, not a pitch deck.
ScadaPort is built by an independent OT/SCADA engineer based in Modena, Italy — 20 years across industrial and pharmaceutical automation, including years inside the vendors whose formats this engine reads. It grew out of real migration work on real plants, not a pitch deck. When you send a project, the person who wrote the parser is the person who answers your email.