What a transfer does
A transfer starts from a campaign that already exists. You pick the source platform, ad account and campaign, choose which ad sets and ads to bring, and pick the destination platform. Whathead fetches the whole tree, translates each field into the destination platform's own values, and drops the result on the builder canvas as new campaign, ad set and ad nodes.
Nothing is published at that point. You open the nodes, check the mapped values, fix anything the transfer flagged, and then publish to the destination ad account you choose. The source campaign is never changed.
- Whole campaign, selected ad sets, or selected ads only
- Several campaigns in one transfer, each keeping its source name so canvas nodes stay traceable
- A warning list for every field that had no exact match, such as an objective with no direct equivalent or a city that was dropped
- "Reset to original" on each mapped node, because the source values are stored with it
Routes and where you can run them
| Route | In the Whathead app | From Claude or ChatGPT (MCP) |
|---|---|---|
| Meta to TikTok | Yes | Yes |
| Meta to Snapchat | Yes | Yes |
| TikTok to Snapchat, Snapchat to TikTok | Yes | Yes |
| TikTok or Snapchat to Meta | Yes (Snapchat to Meta can prefer Story assets) | Yes |
| Same platform, different ad account | Yes | No (MCP transfer needs two different platforms) |
| Meta, TikTok or Snapchat to Google Ads | No | Yes, as a destination |
What carries over and what you set again
| Part of the campaign | What happens |
|---|---|
| Objective and optimization goal | Mapped through Whathead's objective and goal tables |
| Budget, budget type, dates | Carried over; budget level adjusted where the destination requires it |
| Age and gender | Converted to the destination format and clamped to its limits |
| Countries | Carried over by ISO code |
| Cities and regions | Dropped with a warning, because each platform uses its own geo IDs |
| Interests | Category names mapped; IDs must be picked again |
| Custom and lookalike audiences | Not transferred; they belong to the source account |
| Pixel, conversion event IDs, app and catalog IDs | Cleared; event types are mapped, IDs are chosen at publish |
| Ad copy, headline, URL | Carried over and checked against destination limits |
| Call to action | Mapped to the closest destination button |
| Images and videos | Downloaded from the source and uploaded to the destination account |
How to run a transfer
Open the transfer modal in the builder
Choose the source platform, ad account and campaign. Search by name or ID.
Select ad sets and ads
Fetch ads for the ad sets you want, or leave the selection open to bring everything.
Pick the destination platform
Rename the campaign if you are transferring one. For Meta multi-asset ads, choose whether each asset becomes its own ad.
Review the mapped draft
Read the warnings, re-pick interests, cities and audiences, and adjust budget or objective.
Publish
Choose the destination ad account, pixel and page, profile or identity, then publish.
Transfer from an AI assistant
With the Whathead MCP server connected to Claude or ChatGPT, the same transfer runs as the cross_platform_transfer operation of the Whathead core gateway. It defaults to a dry run that returns the mapped plan without touching the destination. A live run creates the destination campaign, ad sets and ads paused unless you explicitly ask for publish after confirmation.
Frequently asked questions
Does a transfer change or pause the original campaign?
No. Whathead reads the source campaign and creates new entities on the destination. The source stays exactly as it was.
Which platforms can I transfer between?
In the app: Meta, TikTok and Snapchat in any direction, plus copies between ad accounts on the same platform. Through the MCP tool, Google Ads is also supported as a destination.
Do my custom audiences and pixel come across?
No. Audiences, pixels, conversion event IDs, app IDs and catalog IDs belong to the source account. Whathead maps the event type (for example Purchase) and asks you to pick the destination pixel and audiences before publishing.
What happens to creatives that are the wrong shape?
From Meta to TikTok or Snapchat, Whathead looks for a 9:16 Story or Reels version of each ad. When there is none, it tells you which ads fell back to the feed asset or were skipped, so you can add a vertical file.
How many transfers are included?
Live transfers per month: 10 on Builder, 20 on MCP Actions, 50 on Operator Bundle and 100 on Agency. Extra live transfers cost $3 each. Dry runs and drafts are not counted.
Is there a time saving figure?
The Whathead homepage demo estimates 32 seconds for its sample transfer. Real time depends on how many ads and videos the campaign has, since every asset is downloaded and uploaded again.
Run it from one workspace
Every plan starts with a 14-day free trial. Only successful live work is metered.