Skip to main content
When you migrate an Alteryx workflow to a Prophecy pipeline, the transpiler reads uploaded files and maps the Alteryx tools to Prophecy gems to create ß
  1. a visual pipeline
  2. open-source code.
  3. a visual pipeline
  4. open-source code.
The following tables list the Alteryx components that Prophecy supports, along with the corresponding Prophecy gems mapped after transpilation.
If you don’t see a particular component on this list, you can include custom abilities beyond custom scripting. To learn more, see gem Builder for SQL.

Input and output

The following table lists mappings for Alteryx In/Out tools.

Preparation

The following table lists the mapping for Alteryx Preparation tools.

Join

The following table lists the mapping for Alteryx Join tools.

Parse

The following table lists the mapping for Alteryx Parse tools.

Transform

The following table lists the mapping for Alteryx Transform tools.

Developer

The following table lists the mapping for Alteryx Developer tools.

Documentation

The following table lists the mapping for Alteryx Documentation tools.

Laboratory

The following table lists the mapping for Alteryx Laboratory tools.

In-Database

The following table lists mappings for Alteryx In-Database tools. For the most part, Import processes Alteryx In-Database tools in the same way it processes their standard equivalents. For example, when you import a workflow that uses a Filter In-DB tool, Import converts it to a standard Filter gem; Import preserves filtering logic, but execution does not occur in the original database.
Prophecy workflows always execute in the configured fabric; unlike Alteryx, there is no separate “In-DB” toolset or execution mode.