Data migration · Campaigns

Campaign Member Statuses look like a picklist and behave like records. Every Campaign has its own set, each with its own ID, and you can’t rename one once members are in it. Here is how to migrate them before the members arrive.

Campaigns → Statuses → MembersThe load order
Campaign ID + Sort Orderthe key that matches old to new
1 upsertupdates Sent and Responded, creates the rest
18‑minute videoThe full walkthrough
On this page
  1. The problem
  2. Clean up names
  3. 1 · Export statuses
  4. 2 · New Campaign IDs
  5. 3 · Build the key
  6. 4 · Pull the IDs
  7. 5 · Upsert file
  8. Upsert and check
  9. Gotchas and FAQ
Watch on YouTube ↗
The problem

They look like a picklist. They aren’t.

Campaign Member Statuses are records, one set per Campaign, each with its own ID. That changes how you migrate them, and it means they go in before a single Campaign Member does.

Every new Campaign gets two statuses automatically: Sent (the default) and Responded. Then people add Invited, Registered, Attended, RSVP No… per Campaign. “Invited” on one Campaign and “Invited” on another are two different records that happen to share a label.

And once members are sitting in a status, Salesforce won’t let you rename or delete it until you move every one of them out. So get the statuses right first. The load order is Campaigns → Campaign Member Statuses → Campaign Members.

Prefer to read? Everything in the video is written out below.

Before you start

Clean up the names first.

Reports and automation match status labels exactly. RSVP-Yes, RSVP Yes and RSVP  Yes are three different things.

  • Pick one spelling for each status and use it on every Campaign
  • Watch spaces and punctuation: a double space or a hyphen creates a “new” status nobody can see
  • Fix it in the spreadsheet, before members are attached and renaming gets painful
Step 1

Export the statuses from the new org.

The new org already has a Sent and a Responded on every migrated Campaign. You need their IDs.

  1. In Data Loader click Export and tick Show all Salesforce objects. Campaign Member Status is hidden otherwise.
  2. Choose Campaign Member Status, select all fields and finish.

The file gives you each status’s Id, its CampaignId, Label, SortOrder, IsDefault and HasResponded. Keep it: it’s the reference for everything that follows.

Step 2

Swap old Campaign IDs for new ones.

The source statuses point at the old org’s Campaigns. Point them at the new ones.

Campaigns have to be loaded already. VLOOKUP each legacy Campaign ID in the source file against the Campaign success file (or a legacy External ID on Campaign) to get the new Campaign ID.

Excel workbook with source Campaign Member Status rows next to their legacy Campaign IDs and the new Campaign IDs looked up from the Campaign success file
Old Campaign ID on the left, new one looked up beside it.
Step 3

Build a key: Campaign ID + Sort Order.

A label alone isn’t unique, because every Campaign has a Sent. Campaign plus sort order is.

Add a Key column to both the source file and the new-org export:

=CONCATENATE(A2, B2)    // A2 = new Campaign ID, B2 = Sort Order
Campaign IDSort OrderKey
701…AAA1701…AAA1
701…AAA2701…AAA2
701…BBB1701…BBB1
Step 4

Pull the new status IDs across.

VLOOKUP the key into the new-org export and bring back its Campaign Member Status ID.

=VLOOKUP(D2, NewExport!A:F, 6, FALSE)

Rows that find a match are statuses that already exist in the new org (positions 1 and 2, Sent and Responded), so the upsert will update them to match the old org. Rows with no match (your Invited, Registered, Attended) come back blank, and the upsert will create them.

Step 5

Build the upsert file.

Six columns, clean values, no helper columns.

ColumnHolds
IdThe new-org status ID from Step 4. Blank for statuses that don’t exist yet
CampaignIdThe new Campaign ID
LabelInvited, RSVP Yes, Attended…
IsDefaultTRUE for the one default status per Campaign
HasRespondedTRUE if this status counts as a response
SortOrderDisplay order within the Campaign

Replace any #N/A that should be blank, rename a New Campaign ID column to CampaignId so Auto-Match catches it, and delete the Key and lookup columns.

The load

Upsert on Id, then check a Campaign.

Upsert updates the rows that have an Id and inserts the ones that don’t.

  1. In Data Loader click Upsert, choose Campaign Member Status and your CSV.
  2. Match on Id.
  3. Map the six columns (API-name headers Auto-Match cleanly) and finish.

Then open a migrated Campaign and look at its Campaign Member Statuses related list: names, default, responded flags and order should match the old org. The success file holds the IDs of the statuses it created. Keep it with the rest of the migration files. Now you can load Campaign Members.

Gotchas

The questions people ask.

Why can’t I treat them like a picklist?
Because each status is its own record on its own Campaign, with its own ID. There’s no shared value list to update.
Why do statuses have to go before Campaign Members?
Once members are in a status, you can’t rename or delete it until you move them all out.
I can’t find Campaign Member Status in Data Loader
Tick Show all Salesforce objects on the export screen.
What has to exist first?
The Campaigns, in the new org. Statuses can’t exist without one.
Why Campaign ID + Sort Order as the key?
Labels repeat across Campaigns and can be renamed. Campaign plus position is unique in both orgs.
My upsert failed on some rows
Check for leftover #N/A values and Campaign IDs from the old org. The common Data Loader error codes cover the rest.
Data Migration Masterclass

Campaigns are a three-object job.

The Masterclass walks through the whole migration in load order, including Campaigns, their statuses and the members and history that hang off them.

Know someone migrating Campaigns into a new org?

Share on LinkedIn
Doing this for a whole org, not just one object?

One CSV is a tutorial. Forty objects, 15 years of history and a go-live date is a project. That’s the part I do for a living.

See how I run migrations →