Like-for-like licensing
We provide comparable Integration Soup licensing for your approved Iguana production footprint.
Interfaceware Iguana migration services
Move from Iguana without losing the logic your team understands
Your channel exports, Lua projects, mappings, and sample data give us a strong migration starting point. We rebuild them as Integration Soup workflows while keeping the business logic, names, and code structure familiar wherever practical.
- Like-for-like licensing*
- Your Iguana price protected*
- Migration assistance included*
Our Iguana migration assurance
Keep your Iguana licensing price. Get the migration help included.
Subject to approval, we will provide like-for-like Integration Soup licensing at the price you currently pay for Iguana and help transform your approved channels into Integration Soup workflows.
For the approved scope, your Integration Soup licensing and our channel-conversion assistance will cost no more than your verified current Iguana licensing. Ask about price-matched migrationYour price protected
We match the verified licensing price you currently pay for Iguana.
Conversion assistance included
We help transform the agreed channels, code, mappings, and tests into Integration Soup workflows.
*Offer subject to approval, verification of existing Iguana licensing and pricing, and agreement on equivalent licensing requirements and migration scope. Third-party licences, infrastructure, travel, and services outside the approved scope are excluded unless agreed in writing.
Plan for continuity
A practical path forward, without a rushed cutover
If changes around the Iguana ecosystem have prompted questions about long-term support, staffing, or platform ownership, you can establish a migration path without putting live interfaces at risk. We begin with an inventory, prove a representative channel, and plan the wider move while your existing service continues to run.
Iguana's code-led model fits Integration Soup well. Exported channel configuration, Translator projects, Lua modules, VMD files, and sample messages let us retain the interface's working shape rather than reverse-engineering it from a diagram.
A repeatable process
From Iguana export to proven Integration Soup workflow
We combine structured extraction with hands-on engineering, so automation accelerates the work and experienced people resolve the important differences.
-
01
Export and inventory
Collect Git channel exports or project archives, Lua and VMD files, sample data, environment settings, libraries, certificates, connections, and topology.
-
02
Map and translate
Create the receiver and activity flow, translate Lua into maintainable C#, carry across mappings, and identify dependencies needing targeted replacements.
-
03
Replay and compare
Use exported samples and de-identified log cases to compare outputs, routing, ACKs, error paths, database effects, and external calls.
-
04
Pilot and cut over
Configure target environments, run selected channels in parallel where appropriate, agree rollback, and migrate in controlled groups.
Code you can recognise
How Iguana concepts map to Integration Soup
Integration Soup gives the same integration intent a workflow model your team can inspect visually and extend with code.
| Interfaceware Iguana | Integration Soup | Migration approach |
|---|---|---|
| Source component | Receiver | LLP, file, HTTPS, database, and other entry settings become the workflow receiver and its response behaviour. |
| Filter or Translator | Transformers, filters, and code activities | Processing order and business rules are kept, using visual actions or C# where code is the clearer fit. |
| Destination component | Sender or activity | The endpoint, payload, retries, and operational intent are mapped to the matching Integration Soup activity. |
| Lua project files and modules | C# code activities and reusable .NET logic | Functions, modules, variable names, and control flow remain recognisable where practical while runtime calls are translated. |
| VMD files and node mappings | Message templates, mappings, and code transformers | Message structures and transformations are reproduced in the clearest maintainable form. |
queue.push and channel routing | Workflow outputs and connected activities | Message fan-out, filtering, and chained-channel topology are made explicit in the target design. |
| Environment variables and settings | Environment configuration and workflow variables | Endpoints, credentials, certificates, and environment-specific values are separated for deployment. |
Keep the confidence, change the engine
Test against the behaviour your interfaces already have
Iguana sample data and selected log cases become a useful regression pack. We add the difficult boundaries your team knows about, then prove the converted workflow before production traffic moves.
Show us an Iguana channel- Message fidelity: source parsing, mapped values, generated payloads, and encodings are compared.
- Flow fidelity: filters, fan-out, queue behaviour, ACKs, and ignored-message cases are exercised.
- Dependency fidelity: databases, web APIs, files, certificates, libraries, and environment values are verified.
- Operational fidelity: errors, retries, alerts, logs, throughput, recovery, and support handover are accepted.
Practical answers
Questions about moving from Iguana
You do not need a perfect inventory before talking to us. We can help establish it.
What should we export from Iguana?
Git channel exports or Translator project archives are a strong start. Include Lua modules, VMD files, sample data, relevant environment settings, dependencies, and de-identified messages from important success and failure cases.
Can you keep our Lua code?
We preserve the logic and keep function boundaries, modules, variable names, and control flow recognisable where practical. Lua syntax and Iguana-specific APIs are translated to C# and Integration Soup APIs so the result runs natively and remains maintainable.
What about linked channels and shared modules?
We inventory the topology before converting individual channels. Shared modules become reusable code or components, and From Channel/To Channel relationships are mapped into an explicit Integration Soup workflow design.
Can we prove one complex channel first?
Yes. A representative channel with real transformations and dependencies is the best way to prove the approach, find organisation-specific patterns, and plan the wider migration with confidence.
Start with a representative channel
See how your Iguana logic fits Integration Soup
Request a demo and tell us a little about your interface estate. We will get in touch to plan a focused first conversion.