The bindings file lists every send port and receive location. What matters is which adapters they use: file and FTP move cheaply, IBM MQ and SAP need an integration service environment or a gateway, and that is the budget.
Files stay on a private volume, are never shared, and are deleted on request. An NDA on your paper is fine.
| Adapter | Ports | Logic Apps equivalent |
|---|---|---|
| FILE | 11 | Azure Blob or SFTP |
| WCF-SQL | 3 | SQL connector |
| MQS | 2 | none in consumption plan |
| FTP | 2 | FTP connector |
| SMTP | 2 | Office 365 |
| WCF-SAP | 1 | SAP connector, gateway required |
Read the full sample report — the same code, run against a synthetic estate.
Two business days from the file arriving. Late for a reason on our side and the report is free.
The document, one revision, and the machine-readable findings file. Yours to forward.
Counted findings and an effort floor. Not a licence audit and not a migration quote.
No account, no access to your systems, and the findings file ships with the document.
| Delphi / VB6 | Compiler unsupported since 2008 | $2,500 |
| Dynamics GP | Support ends 31 December 2029 | $2,500 |
| SAP ECC | Mainstream maintenance ends 2027 | $4,500 |
| VMware | Per-core renewal, every year | $1,500 |
| Gentran/Sterling | Acquired product, no vendor priority | $3,500 |