Skip to main content
Matillion orchestration and transformation components map into Planasonix nodes and control-flow constructs. Treat the converted graph as a draft: Matillion often embeds environment semantics and vendor-specific SQL that you must revalidate on the target warehouse.
See Import and convert for artifact upload, connection mapping, and promotion practices.

​
Job export

1

Export the job or project

From Matillion ETL, export the orchestration job or project package your administrator allows for migration (JSON/XML export varies by product line and version). Include shared jobs and metadata dependencies referenced by orchestration.
2

Gather connection metadata

Collect environment names, OAuth details, and warehouse sizing notes separately—exports rarely include secrets, and you should not embed them in files.
3

Upload to Planasonix

Start the Matillion profile in the import wizard, upload the archive, and select the default warehouse dialect Matillion targeted (Snowflake, Redshift, Delta on Databricks, BigQuery, etc.).

​
Component mapping

Matillion patternPlanasonix direction
Table Input / QuerySource or SQL source node
Calculator / Filter / AggregateColumn/row transform nodes
Join / UnionJoin and union nodes
Rewrite / LoadDestination or merge/upsert patterns
Orchestration tasksSequences, branches, and error handlers on the canvas
Open Matillion’s component tree side by side with the Planasonix conversion report. Resolve yellow warnings before you tackle optional cosmetic rearrangements on the canvas.

​
Environment variable translation

Matillion environment variables and project parameters become Planasonix pipeline variables or environment-scoped overrides.
Normalize names (MATILLION_WH → warehouse_role) when imports produce awkward identifiers. Keep a mapping sheet for operators who still search legacy names in runbooks.
Move passwords and API keys into Planasonix credential stores. Keep non-secret defaults (bucket prefixes, file masks) in variables for readability.

​
Orchestration and error handling

Matillion orchestration success and failure paths may map to Planasonix branch nodes or try/catch patterns depending on feature parity.
Python scripts and orchestration scripts in Matillion are not guaranteed to have one-to-one equivalents. Plan manual rewrites for complex control scripts and file operations.

​
Validation checklist

Re-run row counts and key uniqueness checks for every converted job. Matillion components sometimes hide implicit DISTKEY/SORTKEY or clustering assumptions that change performance after migration.

Control flow nodes

Branching, iteration, and error paths on the canvas.

Destinations

Load patterns and merge semantics.