boomi-migration

# Boomi Migration Knowledge for analyzing Dell Boomi Component XML exports and converting them to the standard integration schema for Prismatic CNI migration. ## Boomi Export Format Boomi exports are directories of XML files, each representing a single component. Each file uses the `bns:Component` wrapper from the `http://api.platform.boomi.com/` namespace. **File naming convention**: `<name>__<type>__<subType>__<componentId>.xml` - Example: `[0010] MAIN - Dacra Interface__process__8b67b542-c021-401f-8a84-6f3819d4d778.xml` **Component types** found in exports: - `process` - Workflows/orchestrations with shapes (steps) and connections - `connector-settings` - Connection configurations (HTTP, database, etc.) - `connector-action` - API operations (GET, POST, etc.) - `transform.map` - Data transformation maps with field mappings and functions - `profile.json` / `profile.xml` / `profile.flatfile` - Data structure definitions - `crossref` - Cross-reference lookup tables - `processproperty` - Configurable process properties - `documentcache` - In-memory document caching - `script.mapping` / `script.processing` - Groovy scripts - `transform.function` - User-defined reusable functions ## Parser Use `prismatic-tools parse-export` to deterministically extract structured data from the export directory. The parser handles all XML parsing and outputs JSON. See `references/boomi-export-parsing.md` for interpreting the output. ```bash # Full output prismatic-tools parse-export <expor...