Move Columns
Infoveave Data Automation — Column Operations
Drag columns into the order you need — the data stays exactly the same, just arranged the way downstream systems expect it.
When data lands from multiple sources — APIs, exports, sensor feeds, spreadsheet uploads — the column order is rarely consistent. Downstream database inserts, Excel templates, API payloads, and visualization layers all expect a fixed field sequence. Move Columns fixes the order once in your workflow, so every dataset that flows downstream arrives with the layout those systems need — without anyone manually rearranging columns in the file before processing.
What Move Columns does
Reorder columns in a dataset by specifying their desired sequence in Infoveave workflows. Standardize column layouts across multiple sources for consistent downstream processing.
When to use Move Columns
- You are combining datasets from multiple sources with inconsistent column orders before joining or stacking them
- You need to align column order with a target database schema before an insert or export step
- A downstream API, export template, or report expects columns in a specific positional sequence
- You want to put key identifier columns first for easier readability and debugging in intermediate workflow outputs
When to avoid it
- You also need to remove some columns — use Select Columns, which reorders and subsets in one step
- You need to rename column headers rather than reorder them — use Rename Columns for that
- You want to sort the rows of the dataset — use Sort Column for row-level ordering
Where it fits in your Infoveave automation
Move Columns is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Move Columns
Real scenarios where this transformation saves hours of manual work.
Align Multi-Source Sensor Logs to Standard Column Layout
A plant integration team pulls sensor logs from three different production lines. Each line's export tool produces columns in a different order — some put the timestamp first, others put the machine ID first. Move Columns reorders each feed to a common layout — ID, Timestamp, Line, Metric, Value — before the feeds are stacked and processed together in the workflow.
Match Target Database Schema Before Bulk Insert
A retail data team loads daily transaction records into a PostgreSQL table with a fixed column order defined by the schema. The source export does not guarantee column sequence. Move Columns reorders the fields to match the target schema on every import run, preventing positional insert errors and eliminating the need for a manual step between export and load.
Standardize Patient Record Columns for Multi-System Integration
A healthcare integration team receives patient record exports from three different EHR systems. Each system produces fields in a different sequence. Move Columns reorders every feed to a canonical layout — Patient ID, Admission Date, Discharge Date, Diagnosis, Consultant — so downstream merging, reporting, and audit steps all operate against a consistent column structure regardless of which source the record came from.
See Move Columns in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
Original: id, name, lastAccess, dob, graduationDate, enrollmentDateid, dob, name, graduationDate, enrollmentDate, lastAccessInput Data
| id | name | lastAccess | dob | graduationDate | enrollmentDate |
|---|---|---|---|---|---|
| 1 | Alice Brown | 01/15/2023 | 2000-05-10 | 2026-05-15 | 01/15/2023 |
| 2 | Bob Green | 15-Feb-2023 | 2002/04/12 | 2027-05-20 | 02/15/2023 |
| 3 | Charlie Blue | 01/01/2023 | 1995-06-15 | 2025-05-30 | 01/01/2023 |
Output Data
| id | dob | name | graduationDate | enrollmentDate | lastAccess |
|---|---|---|---|---|---|
| 1 | 2000-05-10 | Alice Brown | 2026-05-15 | 01/15/2023 | 01/15/2023 |
| 2 | 2002/04/12 | Bob Green | 2027-05-20 | 02/15/2023 | 15-Feb-2023 |
| 3 | 1995-06-15 | Charlie Blue | 2025-05-30 | 01/01/2023 | 01/01/2023 |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Column Map
Specify the desired column sequence by providing the full list of column names in the order you want them to appear in the output. All columns from the source must be included — Move Columns reorders the complete set rather than selecting a subset. To also remove columns, combine with Drop Columns or use Select Columns instead.
All Columns Required
Unlike Select Columns which drops unlisted columns, Move Columns expects all columns to be listed — it reorders the full set. If you want to reorder and remove in a single step, Select Columns handles both operations simultaneously by including only the fields you want in the order you want them.
Frequently asked questions
Everything you need to know about Move Columns in Infoveave.
Also in Column Operations — and what runs before & after
Transformations in the same family as Move Columns, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Move Columns is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
