End-User Guide — apigee2mulesoft

You have an Apigee API bundle. You want a Mulesoft project. This tool does that.

What it doesURL copied

Takes an Apigee bundle folder on disk, runs it through a five-stage AI pipeline, and writes a Mulesoft project to an output folder. Policies it is confident about are marked done. Policies it is uncertain about are flagged for your review.

flowchart LR
    A["Apigee Bundle<br/>(folder on disk)"]
    B["Migration Pipeline"]
    C["Mulesoft Project<br/>(output folder)"]
    D["migration-report.md"]

    A --> B --> C
    B --> D

InstallURL copied

pip install apigee2mulesoft

Requires Python 3.11+.

RunURL copied

migrate path/to/apigee-bundle

By default, output goes to ./output. Change it:

migrate path/to/apigee-bundle --output path/to/mulesoft-project

What you getURL copied

output/
  src/main/mule/          # one .xml stub per policy
  migration-report.md     # per-policy status: done or needs-review

Review gateURL copied

High-confidence mappings (≥ 0.8) are written silently. Low-confidence ones pause and ask:

[review] 1 mapping(s) need review:
  - SpikeArrest-1 (Unknown): low confidence — manual review required
    Approve stub mapping 'UNKNOWN'? [y/n]:

• y — accept the stub, mark done in report
• n — skip, mark needs-review in report

After review, open migration-report.md to see the full status list.

Supported policiesURL copied

TroubleshootingURL copied

No policies found: Check your bundle has apiproxy/policies/*.xml files. All policies flagged for review: Normal for the first run on a new policy type. Approve or correct the stub — coverage improves over time.