Alteryx Migration Readiness Checklist

Use this checklist before importing Alteryx workflows into PlaidCloud. A complete package helps PlaidCloud create Advanced workflows, macro workflows, Document-backed dependencies, and controlled runtime inputs with minimal follow-up.

Note

For large portfolios, run this checklist once for the portfolio and again for each high-priority workflow family.

Collect Workflow Files

Collect every workflow file that belongs to the migration:

1. Standard workflows: .yxmd.
2. Analytic apps: .yxwz.
3. Macros: .yxmc.
4. Nested or shared macros referenced by other workflows.
5. Workflow versions that are still used in production.

Keep related workflows and macros together when they call each other. PlaidCloud uses those relationships to generate macro workflows and connect macro input and output ports.

Collect Data Dependencies

Package the files that the workflows read, write, or inspect:

• CSV, TSV, fixed-width, JSON, XML, Excel, Access, YXDB, and database extract files.
• Folders used by Directory or Dynamic Input tools.
• Expected output files for validation.
• Report assets such as images, PDFs, templates, and map layers.
• Lookup tables and rule tables used by joins, formulas, replacements, and matching.

If a workflow references a local desktop path, include that file or folder in the import package and choose the Document path where PlaidCloud should store it.

Collect Spatial Sidecars

Spatial file formats often require multiple files to stay together. Include every sidecar file in the same folder:

• Shapefile groups such as .shp, .shx, .dbf, and .prj.
• MapInfo groups such as .tab, .map, .id, and .dat.
• KML, GeoJSON, and other standalone spatial files.
• Projection or coordinate reference files used by the workflow.

Missing sidecars are a common source of spatial validation differences.

Capture Runtime Inputs

For analytic apps, record the values users normally provide:

1. Text, numeric, date, file, and folder inputs.
2. Drop-down, radio button, check box, list, and tree selections.
3. Defaults used for scheduled or repeatable runs.
4. Values that trigger conditions, warnings, or errors.

PlaidCloud converts these inputs to controlled workflow variables.

Choose The Target Location

Before import, decide:

1. Target PlaidCloud project.
2. Target Document account.
3. Target Document folder for imported files.
4. Naming convention for converted workflows and macros.
5. Whether the first import is a staging import or production import.

For portfolio migrations, use a dedicated migration folder in Document so dependencies remain easy to audit.

Choose Validation Evidence

For each workflow, choose the validation level:

• Structural validation confirms the workflow converts into a runnable PlaidCloud DAG.
• Output parity validation compares schema, row count, and row values against trusted Alteryx outputs.
• Artifact validation reviews reports, PDFs, images, charts, maps, or model outputs.

Store expected outputs with the migration package whenever output parity is required.

Import Readiness Checklist

Before importing, confirm:

• Workflow, app, and macro files are present.
• Referenced macros are present.
• Input files and folders are present.
• Spatial sidecars are grouped together.
• Expected outputs are available when parity validation is part of the migration plan.
• Runtime input values are known for analytic apps.
• Target project and Document path are selected.
• Credentials or external connections needed by the workflow are available in PlaidCloud.

Related Guides

• Migrate Alteryx Workflows
• Package Alteryx Dependencies
• Validate Converted Alteryx Workflows