Supported source platforms
The import service maps external metadata into Planasonix nodes and edges. Coverage depends on the artifact you supply and the platform version; treat the first converted graph as a draft you harden with preview runs and peer review.Importers translate intent, not always line-for-line behavior. Always run validation jobs and compare row counts, keys, and business metrics against the legacy system.
Import wizard steps
1
Choose source platform
Select the originating tool. The wizard adjusts required uploads or API connections.
2
Provide artifacts or credentials
Upload export files (for example,
.dtsx, Alteryx .yxmd, dbt project archive) or connect read-only credentials where a live scan is supported.3
Map connections
Match imported logical connections to Planasonix connections. Name alignment reduces manual edits in each node.
4
Review conversion report
Open the report for warnings (unsupported features), approximations (changed semantics), and manual tasks (scripts, custom components).
5
Generate the pipeline
Planasonix creates a draft graph in your selected project or folder. Nothing runs against production until you configure schedules and destinations.
6
Validate and harden
Preview data, fix red nodes, replace placeholders, and add variables for environment-specific values.
Bulk import
When you bring many artifacts at once:- Batch upload multiple files of the same type; the wizard queues conversion jobs and emails or notifies when reports are ready.
- Naming conventions: Apply a prefix (
ssis_,alteryx_) so search and permissions stay manageable. - Ownership: Assign a default project and technical owner for the batch so follow-up work does not stall in an unassigned queue.
After import
Pipeline canvas
Edit graphs, preview data, and debug runs.
Templates
Save a vetted post-import pattern for the next wave of migrations.