Before asking whether a migrated campaign performed better, establish what was actually migrated. A copied campaign can retain familiar names and assets while operating under different allocation or bidding conditions. For an overseas marketing team working with a Chinese supplier, the handover should describe the effective new campaign, not simply report that the old one was duplicated successfully.

TikTok's October 2026 duplication guidance describes a conversion into the upgraded Smart+ experience, available progressively to selected accounts. It identifies settings that are retained and others that require review or re-entry. Lead-generation advertisers may be offered a choice between upgrading and creating another manual campaign. Availability and the objective-specific conversion rules therefore belong at the beginning of the decision.

Accept the resulting configuration before scheduling delivery

The documented removal of an existing split-test setting is a particularly important example. A copied campaign does not automatically remain part of the experiment that the source campaign was created to run. Budget and bidding rules also require attention. It is safer to inspect the converted draft than to infer continuity from matching names, videos or destination URLs.

Start with the way money is allocated. Record whether the effective budget belongs to the campaign or an ad group, and whether its period and allocation rules changed. Two configurations showing the same amount can give operators different control over individual ad groups. Use the conversion table for the relevant objective rather than borrowing rules from a different campaign type.

Then inspect the optimization action and the bidding configuration together. A familiar event label is not enough if another control was reset during conversion. Where a field needs to be completed, revisit the reason for the old setting. A restriction intended to protect a service-market boundary should not be replaced casually with a broad default just because that default allows the draft to be saved.

An original export or a short set of screenshots is useful here because it preserves what the operator intended to move. Compare that reference with the resulting draft and mark each material item as retained, changed or unresolved. This is a migration acceptance exercise, not an invitation to redesign every aspect of a working account. If the team also wants a new strategy, describe that as a separate decision.

Check launch timing as well. The schedule is part of the effective configuration, particularly when a campaign is being prepared by an agency in another time zone. An intended handover date, a saved draft and an active delivery state are different milestones. The sales team needs to know which milestone has actually occurred before interpreting incoming leads as traffic from the new setup.

Do not inherit an experiment merely by inheriting its name

A before-and-after comparison may describe the outcome of a migration, but it does not isolate the contribution of automation. Time, budget allocation and bidding conditions may have changed together. If the original split-test setting was removed, calling the duplicate the “test group” does not restore the missing experimental design. Report the observed change with the configuration changes that accompanied it.

The source campaign can remain a reference without necessarily remaining live. Running both is a separate operational choice involving budget and potentially overlapping delivery. Keeping both active solely to obtain a comparison can create a different question from the one the team meant to answer. If a controlled test is needed, design it deliberately using the platform capabilities currently available to the account.

Creative compatibility deserves its own check. For example, planning Spark and non-Spark assets separately addresses an identity constraint that a copy action cannot resolve by itself. The existence of an asset in the source account is not evidence that every intended combination can be deployed in the destination campaign.

For supplier-agency collaboration, the useful completion note is short: identify the source and destination, the material changes, any unresolved control, and the intended activation point. Sales colleagues do not need the entire conversion table. They do need to know if the conditions behind a familiar campaign name have changed. Where an essential restriction cannot be expressed in the new mode, retaining the manual campaign or delaying migration is a clear outcome, not a failed attempt to automate.

Sources