Navigation

Build a Data Transformation Pipeline

Use the Transform Builder to create complex, multi-step data transformation workflows without writing code.

Last updated:

Real-world data rarely arrives in the format you need. The Transform Builder lets you visually build multi-step transformation pipelines that rename, reshape, and enrich your data โ€” all without code.

๐Ÿšฉ The Scenario

You receive user data from a third-party CRM and need to transform it for your internal system:

Source (CRM export):

[
  {
    "FIRST_NAME": "alice",
    "LAST_NAME": "johnson",
    "EMAIL_ADDRESS": "ALICE.JOHNSON@GMAIL.COM",
    "SIGNUP_DATE": "1706832000",
    "SUBSCRIPTION_LEVEL": "premium",
    "PHONE": "5551234567"
  }
]

Target (your internal format):

[
  {
    "fullName": "Alice Johnson",
    "email": "alice.johnson@gmail.com",
    "signupDate": "2024-02-02",
    "tier": "Premium",
    "phone": "(555) 123-4567",
    "id": "a1b2c3d4-..."
  }
]

๐Ÿ› ๏ธ Step-by-Step

  1. Open the Transform Builder.
  2. Paste or upload your source JSON.
  3. Click Magic Map to auto-detect all source fields.
  4. Configure each mapping:
Source FieldTarget KeyOperations Applied
FIRST_NAME + LAST_NAMEfullNameTemplate: {{FIRST_NAME}} {{LAST_NAME}} โ†’ Title Case
EMAIL_ADDRESSemailLowercase
SIGNUP_DATEsignupDateDate Format (unix โ†’ YYYY-MM-DD)
SUBSCRIPTION_LEVELtierCapitalize
PHONEphoneCustom Script (format as phone number)
(generated)idUUID v4
  1. For the phone field, add a Custom Script:
return value.replace(/(\d{3})(\d{3})(\d{4})/, '($1) $2-$3');
  1. For the fullName field, use the Template operation:
{{FIRST_NAME}} {{LAST_NAME}}

Then chain a Title Case operation.

  1. Preview the result in real-time in the right panel.
  2. Export the transformed JSON or download the mapping config for reuse.

โ›“๏ธ Chaining Operations

Operations execute in sequence (left to right). For example:

FIRST_NAME โ†’ Trim โ†’ Capitalize โ†’ Template โ†’ Title Case โ†’ fullName

This ensures whitespace is removed first, then the name is properly cased.

๐Ÿ’พ Saving & Reusing Configs

  • Export Config: Save your mapping rules as a .json file.
  • Import Config: Load a previously saved config to apply the same transformation to new data.
  • Workspace Persistence: When used in a workspace, your mappings are auto-saved.

๐Ÿ’ก Pro Tips

  • Test with small data first: Build your pipeline on a small sample, then apply it to the full dataset.
  • Use the Code Export: Generate the equivalent JavaScript code to run your transformation programmatically in a Node.js script.
  • Combine with Convert: After transforming, switch to the Convert Tool to export in your target format (CSV, SQL, etc.).

๐Ÿš€ Try it now

Open the Transform Builder and click Magic Map to auto-generate your first transformation pipeline.