Automated migration results
When Import detects an Alteryx RegEx tool:- It generates a Regex gem in Prophecy.
- The selected Alteryx operation (Match, Parse, Replace, or Tokenize) is mapped directly to the corresponding Regex gem action.
- The regex pattern is copied exactly, except in a small subset of cases where Alteryx’s regex patterns differ from Prophecy’s regex patterns.
- Capture groups are expanded into output columns when using Parse.
- Because Prophecy’s Replace does not overwrite existing columns, in these cases Prophecy adds a downstream Reformat gem to remove replaced columns.
Manually replicate in Prophecy
To reproduce Alteryx RegEx behavior manually:- Add a Regex gem to the canvas.
- Select column to parse.
- Select the Output strategy that matches the Alteryx configuration:
- Match
- Parse
- Replace
- Tokenize
- Specify regex pattern.
- Configure output columns (for Parse, Replace, or Tokenize) as needed.
Configuration options
In Alteryx (RegEx tool)
- Select column to parse.
- Enter or configure regular expression: Perl-compatible regex pattern.
- Choose whether or not to use case-insensitive matching.
- Select output method: Match, Parse, Replace, or Tokenize.
- For Replace, enter replacement string.
- For Parse/Tokenize, configure output fields.
In Prophecy (Regex gem)
- Select column to parse
- Select output strategy: Match, Parse, Replace, or Tokenize
- Enter Regex pattern manually (Prophecy provides common patterns for reference).
- Choose whether or not to use case-insensitive matching.
- Configure names and options for output columns, depending on output strategy.
Output behavior
- Alteryx output structure varies by mode.
- Prophecy always produces a single output dataset with added or expanded columns depending on the selected operation.
Known caveats
- Boolean vs numeric flags: Match results differ in type (Boolean vs 1/0). To mimic Alteryx behavior, cast to Boolean in a downstream gem.
- Overwrite behavior: Replace operations append new columns in Prophecy; Alteryx workflows may overwrite fields.
- Regex entry: Prophecy does not provide a regex builder UI; you enter regex manually using drawing on common reference patterns provided in the gem.
- Regex engine differences: Alteryx uses Perl Compatible Regular Expressions (PCRE); Prophecy uses Java regular expressions.
Example
Goal: Extract phone-number components from a string like"(212) 555-0199".
Alteryx RegEx tool (Parse)
- Choose column with phone number.
- Enter or configure regular expression:
(\d{3})[)\s-](\d{3})[-](\d{4}). - Choose Parse for Output Method.
AreaCode, Exchange, Number
Prophecy equivalent (Regex gem)
- Select column to parse.
- Select Parse for Output strategy.
- Enter Regex:
(\d{3})[)\s-](\d{3})[-](\d{4}).
| New column name | Type | Regex Expression |
|---|---|---|
area_code | String | (\d) |
exchange | String | (\d) |
number | String | (\d) |

