[ Migrate to engini ]
Move your workflows into engini
Send the process to our team instead.Talk to us
How to export a Workato recipe
- Open Recipe lifecycle management, Export tab
- Create manifest: name it, choose the source folder, Next
- Select the recipe (and its dependencies)
- Save the manifest
- Build and export package
- Download the .zip
Export filePackage, a .zip with a JSON file per item
No one-recipe download: you export a package built from a manifest. Exporting all projects needs the create-projects privilege.
engini reads the trigger, steps and field mappings from your recipe and rebuilds them as an engini workflow. Importing Workato files straight into the editor is in testing; until it is on in your account, our team converts the file with you.
Workato is a trademark of its owner, and its logo only names the platform. The screen in step 1 is a simplified illustration, not a screenshot. engini is not affiliated with Workato.
How to export a Boomi process
- Open the process from Component Explorer
- Click Revision History
- Click View Component XML on the revision
- The XML opens in a Component XML window
Export fileComponent XML, shown in a window
Boomi's help shows the XML in a window and describes no download button; a file comes only through Boomi's Platform API. Viewing older revisions is not in the Base edition. Talk to us and we take it from there.
Boomi shows a process as XML in a window, with no file to download. Talk to us and our team moves your processes with you; engini rebuilds the trigger, steps and field mappings as an engini workflow.
Boomi is a trademark of its owner, and its logo only names the platform. The screen in step 1 is a simplified illustration, not a screenshot. engini is not affiliated with Boomi.
How to export a MuleSoft Mule app
- In Anypoint Studio: File > Export
- Mule > Anypoint Studio Project to Mule Deployable Archive (includes Studio metadata), Next
- Select the project
- Choose where to save the JAR file
- Keep Attach Project Sources selected, then finish
Export fileMule deployable archive (.jar) with the project sources
Anypoint Studio on the desktop, not the web. The unit is the whole Mule app with all its flows.
engini reads the trigger, steps and field mappings from your Mule app and rebuilds them as an engini workflow. Importing MuleSoft files straight into the editor is in testing; until it is on in your account, our team converts the file with you.
MuleSoft is a trademark of its owner, and its logo only names the platform. The screen in step 1 is a simplified illustration, not a screenshot. engini is not affiliated with MuleSoft.
How to export a Celigo integration
- Go to Home
- Select the integration
- Click the overflow (...) menu
- Select Download integration
Export fileIntegration .zip with each flow's mappings
The unit is the whole integration with its flows. Connections are not in the zip. Integration apps cannot be downloaded.
engini reads the trigger, steps and field mappings from your integration and rebuilds them as an engini workflow. Importing Celigo files straight into the editor is in testing; until it is on in your account, our team converts the file with you.
Celigo is a trademark of its owner, and its logo only names the platform. The screen in step 1 is a simplified illustration, not a screenshot. engini is not affiliated with Celigo.
How to export a Tray.ai workflow
- Open the workflow in the builder
- Open the three-dot menu in the builder header
- Choose Export workflow
- The workflow saves as a JSON file
Export fileWorkflow JSON
Tray's docs point to project export for moving whole environments; single-workflow export is for one standalone change.
engini reads the trigger, steps and field mappings from your workflow and rebuilds them as an engini workflow. Importing Tray.ai files straight into the editor is in testing; until it is on in your account, our team converts the file with you.
Tray.ai is a trademark of its owner, and its logo only names the platform. The screen in step 1 is a simplified illustration, not a screenshot. engini is not affiliated with Tray.ai.
How to export a SnapLogic pipeline
- In Designer, open the pipeline
- Click Export in the Designer toolbar
- The pipeline downloads as a .slp file
Export filePipeline file (.slp)
The .slp does not carry the accounts and assets the pipeline references.
engini reads the trigger, steps and field mappings from your pipeline and rebuilds them as an engini workflow. Importing SnapLogic files straight into the editor is in testing; until it is on in your account, our team converts the file with you.
SnapLogic is a trademark of its owner, and its logo only names the platform. The screen in step 1 is a simplified illustration, not a screenshot. engini is not affiliated with SnapLogic.
How to export a Make scenario
- Click Scenarios
- Open the scenario
- Click the three dots at the top right of the Scenario Builder
- Select Export blueprint
Export fileBlueprint (.blueprint.json)
The blueprint holds modules, settings and mapped values, not connections.
engini reads the trigger, steps and field mappings from your scenario and rebuilds them as an engini workflow. Importing Make files straight into the editor is in testing; until it is on in your account, our team converts the file with you.
Make is a trademark of its owner, and its logo only names the platform. The screen in step 1 is a simplified illustration, not a screenshot. engini is not affiliated with Make.
How to export a Zapier zap
- Click your profile icon, then Settings
- Click Security and data
- In Data management, click the download icon in Download my Zap workflows
- Save the JSON file
Export fileOne JSON file with your Zaps
Team and Enterprise plans only. There is no one-Zap export: the file has all the Zaps you own (an owner or super admin can export the whole account, sent by email).
engini reads the trigger, steps and field mappings from your zap and rebuilds them as an engini workflow. Importing Zapier files straight into the editor is in testing; until it is on in your account, our team converts the file with you.
Zapier is a trademark of its owner, and its logo only names the platform. The screen in step 1 is a simplified illustration, not a screenshot. engini is not affiliated with Zapier.
How to export an n8n workflow
- Open the workflow in the editor
- Open the three-dot Workflow menu in the canvas header
- Select Download
- The workflow saves as a JSON file
Export fileWorkflow JSON
The file can include credential names and IDs; check it before you share it.
engini reads the trigger, steps and field mappings from your workflow and rebuilds them as an engini workflow. Importing n8n files straight into the editor is in testing; until it is on in your account, our team converts the file with you.
n8n is a trademark of its owner, and its logo only names the platform. The screen in step 1 is a simplified illustration, not a screenshot. engini is not affiliated with n8n.
How to export a Power Automate flow
- My flows > Cloud flows, select the flow
- Click the arrow next to Export, then Package (.zip)
- Enter a name and description
- Click Export, then Download if it does not start
Export fileFlow package (.zip)
Package export is for flows outside a solution, by the flow's owner or a co-owner. Flows in a solution export through Solutions > Export as a solution .zip.
engini reads the trigger, steps and field mappings from your flow and rebuilds them as an engini workflow. Importing Power Automate files straight into the editor is in testing; until it is on in your account, our team converts the file with you.
Power Automate is a trademark of its owner, and its logo only names the platform. The screen in step 1 is a simplified illustration, not a screenshot. engini is not affiliated with Power Automate.
How to export a Jitterbit project
- Open the Projects page or the project's actions menu
- Choose Export
- Pick what to include (credentials, schedules, variables)
- Click Export: the project downloads as JSON
Export fileStudio project JSON
The unit is the whole project with its workflows. Your organization can turn off exporting credentials. Design Studio (legacy) exports a .jpk Jitterpak instead.
engini reads the trigger, steps and field mappings from your project and rebuilds them as an engini workflow. Importing Jitterbit files straight into the editor is in testing; until it is on in your account, our team converts the file with you.
Jitterbit is a trademark of its owner, and its logo only names the platform. The screen in step 1 is a simplified illustration, not a screenshot. engini is not affiliated with Jitterbit.
How to export a Pipedream workflow
- Open the project
- Select Settings
- Click Export Workflows
- Download the .zip from the project's File Store
Export fileProject .zip with a JSON file per workflow
Exports the project's workflows (up to 500), and your plan must include File Stores. Secrets and connected-account credentials are left out.
engini reads the trigger, steps and field mappings from your workflow and rebuilds them as an engini workflow. Importing Pipedream files straight into the editor is in testing; until it is on in your account, our team converts the file with you.
Pipedream is a trademark of its owner, and its logo only names the platform. The screen in step 1 is a simplified illustration, not a screenshot. engini is not affiliated with Pipedream.
How to export an Informatica asset
- On the Explore page, find the asset
- Select it, then Actions > Export
- Choose whether to include dependent objects
- Click Export, then get the .zip from My Import/Export Logs
Export fileExport .zip with the asset's metadata and JSON
Your role needs the export privilege and read permission on the asset, and the organization needs the licence for it.
engini reads the trigger, steps and field mappings from your asset and rebuilds them as an engini workflow. Importing Informatica files straight into the editor is in testing; until it is on in your account, our team converts the file with you.
Informatica is a trademark of its owner, and its logo only names the platform. The screen in step 1 is a simplified illustration, not a screenshot. engini is not affiliated with Informatica.
How to export from another platform
- Look for Export or Download in your platform's docs
- Save the file it gives you
- Import the file into engini, or talk to us
Export fileJSON, XML or ZIP, if it has one
engini reads the trigger, steps and field mappings from your workflow and rebuilds them as an engini workflow. Importing other platforms' files straight into the editor is in testing; until it is on in your account, our team converts the file with you.
Platform names are trademarks of their owners. engini is not affiliated with them.
Questions about migrating to engini
How do I migrate from Workato to engini?
Export your Workato recipes as a package: in Recipe lifecycle management, open the Export tab, create a manifest with the recipes, then click Build and export package and download the .zip. Import that file into engini, or send it to us. Our team maps each recipe's trigger and actions to engini, rebuilds it as an engini workflow, and runs it side by side with Workato until the results match. Then you switch over.
Can I keep running Boomi during the migration?
Yes. Your Boomi processes keep running while the engini workflows run on the same inputs, and you switch each one over only when its results match.
Who does the migration work?
Our team does. You tell us which workflows to move and connect your own accounts; we map, rebuild and test the workflows with you.
Which platforms can I migrate from?
Workato, Boomi, MuleSoft, Celigo, Tray.ai, SnapLogic, Make, Zapier, n8n, Power Automate, Jitterbit, Pipedream and Informatica are in the list at the top of this page, each with the steps to export a workflow and a link to its own docs. You can choose another platform too.
Which file do I export from my platform?
Workato exports a package (.zip). Make exports a blueprint (.json). n8n and Tray.ai export a workflow as .json. Zapier exports one .json file with your Zaps, on Team and Enterprise plans. Power Automate exports a package (.zip). SnapLogic exports a pipeline as .slp. MuleSoft's Anypoint Studio exports a deployable archive (.jar). Celigo downloads an integration as .zip. Jitterbit exports a project as .json. Pipedream and Informatica export a .zip. Boomi shows a process's XML in a window and has no download button, so talk to us.
Can AI agents use my workflows after the migration?
Yes. Any engini workflow or connection can be exposed as an MCP server for agents such as Claude, ChatGPT and Cursor, and developers can call the same actions from the SDK, the API or the CLI, limited by a toolset.
Can engini reach systems behind our firewall?
Yes. The On-Prem Agent runs on your own server and opens every connection outward over HTTPS, so you open no inbound ports. It reaches on-premises databases, file drops, internal applications and Priority ERP.
How does engini pricing compare with my integration platform?
engini meters Tasks (one tool call each) and Triggers (one event or scheduled run each), with a monthly amount included in each plan, and does not charge by seat. The plans are on the pricing page at engini.ai/pricing.
Which security certifications does engini hold?
engini holds SOC 2 Type II and ISO 27001, and is GDPR and HIPAA compliant. Access is controlled with SSO, two-factor authentication, roles and IP filtering, and every agent call is recorded in the audit log.
Start with one workflow
Pick your platform at the top of this page, export one workflow to a file and import it into engini, or book a call and tell us what you run today.
For AI agents: engini's documentation index is at docs.engini.ai/llms.txt. To connect an agent, follow the MCP client setup guide.