migration-framework

# Migration Framework ## Standard Integration Schema The intermediate JSON format that all platform parsers produce. See `references/standard-integration-schema.md`. Key sections: - **metadata** — Source platform, confidence score, migration notes - **integration** — Name, description, systems summary - **flows** — Trigger type, step sequence with operations - **api_profiles** — Request/response field definitions with nesting structure - **systems** — Source and destination with connection details - **data_transformations** — Field mappings and transformation functions - **scripts** — Groovy scripts with full source code for TypeScript translation - **error_handling** — Strategy (retry, fail, ignore) - **config_variables** — Overrideable configuration values - **migration_notes** — Manual review items, unsupported features ## Schema-to-Spec Mapping The `schema-to-answers` script maps schema fields to the integration YAML spec items. See `references/schema-to-requirements-mapping.md`. **Pre-populated** (from parsed export — confirmed by user via proposal): - `systems`, `trigger_type`, `schedule_value`, `data_flow` - `source_system`, `destination_system` - `transformations`, `error_handler_type`, `error_retry_*` - `additional_requirements` (includes Groovy scripts for translation) **Left for live discovery** (requires platform interaction): - `source_component`, `destination_component` — live registry search - `*_connection_type`, `*_connection` — live connection search ...