Cookbook
Apply the migration primitives to complete file, API, and workflow integrations.
Recipes assemble the contracts described in Learn. Each states its source and destination assumptions, shows the implementation, and explains what happens when execution repeats or fails.
The sample payloads provide concrete data for those contracts. The same Source, Process Pipeline, Tracking, and Migration Store responsibilities apply to other domains.
CSV to JSON files
Run a complete local definition with source decoding, mapping, tracking, and compensation.
API to API
Implement HTTP source access and repeatable destination writes with explicit recovery.
Combine two sources
Join upstream payloads while preserving one stable identity and a version covering both inputs.
Write to two destinations
Keep a composite Tracking Record and compensate partially completed destination work.
Run durably
Use an Execution Adapter and Migration Execution Envelope to coordinate work through Workflow SDK.
API recipes include their adjacent TypeScript files in tabs. Their illustrative endpoint contracts must be adapted to your provider. The Workflow recipe uses the complete monorepo integration with its database, server, and deployment wiring.