migrating-to-zero-yaml

To migrate a Nango project from nango.yaml to TypeScript, you generate a Zero YAML project skeleton including models.ts and index.ts, then wrap existing scripts in createSync() or createAction() without altering business logic.

Zero YAML migration replaces legacy nango.yaml configurations by defining Nango syncs, actions, and models directly in TypeScript files like models.ts and index.ts, ensuring type safety without changing existing behavior.

Yes, Nango Zero YAML migration preserves existing behaviors including sync types and trackDeletes, ensuring the migrated project compiles and behaves exactly as it did before the mechanical refactor.

When moving away from nango.yaml, you scaffold Nango scripts by generating a central index.ts and wrapping your existing logic with createSync(), createAction(), or createOnEvent() functions to register them.

A mechanical Nango YAML migration requires manual inspection of the original YAML and code updates to ensure the project compiles, meaning it focuses strictly on structural translation rather than optimizing or changing business logic.