VBA Move Columns in Excel — Reposition Columns With Cut and Insert (EntireColumn)

TL;DR — Moving a column is moving a row on the other axis: cut the whole column and Insert it, do not paste it. Columns("C").Cut Destination:=Columns("F") pastes on top of column F and wipes it out. Columns("C").Cut then Columns("F").Insert opens a gap before F, drops the column in, and closes the hole at C — nothing is lost. Two rules keep it clean: cut the EntireColumn (never a partial range), and remember the move is a shift, so cutting a column left of your target pulls the target one column to the left.

Sub MoveColumn()
    Dim ws As Worksheet
    Set ws = ThisWorkbook.Worksheets("Report")
    ws.Columns("C").Cut                       ' pick up the whole column
    ws.Columns("F").Insert Shift:=xlToRight    ' INSERT before column F, shifting the rest right
    Application.CutCopyMode = False
End Sub

Moving a column is the horizontal twin of moving a row, driven by the same Range.Cut. Everything you know from the row case carries over — insert instead of paste, mind the shift, move a block in one call — you just cut columns and they slide sideways instead of down.

What you'll learn

• Why you cut the EntireColumn, and what happens when you cut a partial range by mistake
• The number-one bug — Cut Destination:= pastes over the target column and loses its data
• Why moving a column right shifts your target column left by one (the same shift trap, sideways)
• How to reorder several columns into a fixed layout without them landing in the wrong order
• Why references follow a moved column instead of breaking into #REF!

The mental model: cut the whole column, then insert

A column move is two motions, exactly like a row move. You pick the column up with Columns("C").Cut, then you put it down — and the choice between paste and insert is the whole game:

• Paste (Cut Destination:=Columns("F")) lands column C's cells on top of column F and overwrites everything F held.
• Insert (Columns("C").Cut then Columns("F").Insert) opens a gap before column F, slots the cut column in, and closes the hole back at C. The other columns slide right to make room.

To move a column into a layout, you always insert. Pasting is for overwriting an empty column, not for rearranging. This is moving rows rotated ninety degrees: the grid opens and closes horizontally, and columns to the right renumber.

Cut the EntireColumn, not a partial range

A column move only makes sense on whole columns. Cut a partial range and try to insert it as a column and you either tear the grid or get nothing useful:

ws.Range("C1:C50").Cut                        ' WRONG - a partial range, not the column
ws.Range("F1:F50").Insert Shift:=xlToRight     ' shifts only 50 rows; row 51 down is now misaligned

That shifts fifty cells sideways and leaves the rest of column F where it was — the data below row 50 no longer lines up with the rows it belongs to. Move the whole column so every row travels together:

ws.Columns("C").Cut                            ' RIGHT - the entire column, all rows in step
ws.Columns("F").Insert Shift:=xlToRight

When you locate the column by its header rather than a letter, still resolve it to the whole column with .EntireColumn:

Dim col As Range
Set col = ws.Rows(1).Find("Region", LookAt:=xlWhole)   ' find the header cell
col.EntireColumn.Cut                                    ' cut the WHOLE column it sits in
ws.Columns("B").Insert Shift:=xlToRight

This mirrors the insert-column rule: structural column operations act on Columns / .EntireColumn, never on a partial range.

The shift trap, sideways: moving right shifts your target left

The same shift that renumbers rows renumbers columns. Cut column C and insert it at column F, and the gap at C closes as part of the move, so columns D through F each slide left by one — the column that was F is now at E, and your cut column lands relative to the shifted grid.

Move by header lookup, not by column letters, and the shift cannot bite you, because Find locates where the column is after everything has settled:

ws.Columns("C").Cut
ws.Rows(1).Find("Total", LookAt:=xlWhole).EntireColumn.Insert Shift:=xlToRight
Application.CutCopyMode = False

If you insist on letters, moving a column left (source to the right of the target) leaves the target letter intact; moving it right (source to the left) shifts the target one column earlier.

Reordering several columns into a fixed layout

Reordering columns one Cut/Insert at a time is where layouts scramble: every move shuffles the letters of the columns you have not placed yet. The reliable pattern is to stop chasing moving letters and place each column by header name against the order you want, working left to right so each placed column becomes a stable anchor for the next:

Dim wanted As Variant, k As Long
wanted = Array("Date", "Region", "Product", "Amount")   ' the order you want, left to right
For k = LBound(wanted) To UBound(wanted)
    Dim src As Range
    Set src = ws.Rows(1).Find(wanted(k), LookAt:=xlWhole)
    If Not src Is Nothing Then
        src.EntireColumn.Cut
        ws.Columns(k + 1).Insert Shift:=xlToRight        ' place it in slot k+1, then move on
    End If
Next k
Application.CutCopyMode = False

Because each step targets a fixed slot number and finds the source by name, the shifting letters never throw the layout off.

Cut moves references; delete breaks them

As with rows, Cut + Insert is safe because Excel follows it. A formula reading =Report!C2 is rewritten to track column C to its new position, so it keeps reading the same data after the move. That is the opposite of deleting a column, where a formula pointing into the removed column collapses to =#REF!. Moving relocates the data and carries its references along; deleting destroys the data and orphans them.

How ExcelMaster helps

Reordering columns hides the same three traps as rows, sideways — insert versus paste (data kept or destroyed), the shift that renumbers the columns you have not placed yet, and cutting the whole column rather than a partial range — and each one fails without an error: a target column silently overwritten, a layout scrambled one letter off, or half a column left misaligned below row 50.

ExcelMaster lets you say the layout you want — "put the columns in the order Date, Region, Product, Amount" — and it cuts each whole column, finds it by header so the shifting letters cannot confuse it, and inserts into place instead of pasting over what is there. You keep the workbook and the code.

Frequently asked questions

How do I move a column in VBA without losing data?

Cut the whole column and Insert it: ws.Columns("C").Cut then ws.Columns("F").Insert Shift:=xlToRight. The Insert opens a gap and shifts the other columns right, so nothing is overwritten. Columns("C").Cut Destination:=Columns("F") pastes on top of column F and destroys it — use it only when F is empty.

Why do my columns shift when I move one?

Because a move is a shift. Cutting column C removes it and closes the gap, so the columns to its right slide left by one before your cut column is inserted — the target you named by letter is now one column earlier. Insert relative to a header you find with Find, not a hard-coded letter, and the shift stops mattering.

How do I reorder columns into a specific order in VBA?

Find each column by its header name and insert it into a fixed slot, working left to right: Rows(1).Find("Region").EntireColumn.Cut then Columns(2).Insert, and so on. Targeting a stable slot number while locating the source by name means the shifting letters never scramble the layout.

Can I move a partial column range instead of the whole column?

You can, but it misaligns your data: cutting Range("C1:C50") and inserting it shifts only those fifty cells sideways and leaves the rest of the grid behind, so rows below 50 no longer line up. For a real column move, cut Columns("C") or .EntireColumn so every row travels together.

Should I use Cut or Copy to move a column?

Use Cut. It empties the source column once the column lands, so you end with one copy in the new position. Copy leaves the source in place and you would have to delete it yourself — an extra step that is easy to get wrong. See VBA Cut for the full move-versus-duplicate mechanics.

Tested in

Tested in: Excel 365 (Windows 11), VBA 7.1 — last verified 2026-09-17.

Related guides: VBA Move Rows · VBA Cut · VBA Insert Columns · VBA Delete Columns · VBA Copy Paste