Review Copied Email Campaign Fields Before Reuse
A field-disposition worksheet for Migma creative copies and Resend broadcast drafts.
- Written by
- Marketing Wiki Research Automation
- Review status
- Not independently reviewed
- Published
- Updated
- Evidence checked
- Sources
- 5
Check which creative, audience, sender, subject and timing fields a copied email or broadcast inherits before approving another send.
When you reuse an email, review the copy scope before approving a new campaign. Migma lets a team duplicate the latest email or series into a new canvas chat; Resend's September 21, 2026 API can duplicate a broadcast into a draft with its audience segment, sender, subject and other fields already filled. Those are different objects and different starting states. We recommend using Migma for the new branded creative, then treating every field in the eventual sending system as a fresh decision.
Editorial disclosure: Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Product capabilities below are vendor documentation, not live-account test results. Sources were checked September 30, 2026.
Affiliation: Marketing Wiki's commissioning editor maintains Migma.
Migma's changelog says Duplicate email and Duplicate series open the latest canvas version in a new chat. It documents a way to branch creative without changing the original. It does not establish that a campaign's recipients, schedule, sender or consent state are duplicated. Migma's campaign guide instead walks through choosing the email, recipients, details, sender and timing. That separation is useful when last month's design is a good starting point but last month's audience and offer are not.
Resend's Duplicate Broadcast API release specifies a wider copy: segment, topic, sender, subject, reply-to, preview text and content. The result is a new draft, including when the source broadcast has already been sent. “Draft” describes its initial send state; it does not mean the inherited fields are suitable for another occasion.
Work through one copy, field by field#
Suppose a fictional outdoor retailer sent an April trail-shoe launch to a segment of customers who requested running updates. In September, the team wants an autumn hiking guide for people who opted into outdoor tips. It can reuse the layout, but a straight broadcast copy would also inherit the April segment and launch language. The team should stop at the new draft and resolve the following worksheet before any send approval.
| Field | In the old send | September decision | Evidence to keep |
|---|---|---|---|
| Creative source | April launch email | Duplicate in Migma; edit for the new purpose | New email ID and reviewed canvas preview |
| Audience | Running-update segment | Select the outdoor-tips group using current permission and eligibility | Segment identity, definition and eligible count at approval |
| Topic or preference category | Product launches | Confirm the current message belongs to the chosen category | Preference mapping and owner decision |
| Subject and preview | Trail-shoe availability | Replace both with a truthful guide promise | Approved final text and received test |
| Sender and reply-to | Launch-team mailbox | Confirm the currently monitored identity | Verified sender and reply-owner record |
| Body and links | April products and URLs | Replace old offer, dates, product references and destinations | Link inventory and final HTML review |
| Schedule | April launch instant | Choose a new instant with an explicit timezone | Scheduled state and timestamp, or a decision to leave as draft |
This is an editorial worksheet, not a feature claimed for either vendor. The purpose is to make inherited values visible. Mark each field keep, replace, remove, or unknown; require a named owner and evidence for every unknown before progressing. If the sending platform has more fields than the table, extend it rather than assuming a generic clone rule.
Use Migma as the creative branch#
Open the original email in Migma and duplicate the latest canvas version into a new chat. Brief the new draft with the September reader, current guide, approved claims and working links. Keep the earlier launch as historical evidence. Migma's email viewer documents preview and code inspection, and its Preflight guide documents email-specific checks. Use those surfaces on the new selected email, not on a remembered screenshot of the old one.
If Resend is the sending system, create or inspect its new broadcast draft and reconcile every copied field against the worksheet. Do not assume that a Migma duplicate automatically becomes a Resend broadcast, or that a Resend draft contains the latest Migma canvas version. Record the exported or transferred artifact and compare the destination preview before approval. If the team sends through Migma, follow Migma's campaign wizard and check its recipient, sender and timing steps on the new campaign.
Release only the new intent#
A safe copy review ends with two linked records: the source object used for inspiration and the new send object with its own approved field set. Before authorizing delivery, verify the new draft's status in the actual sending system, inspect the current audience eligibility, send a controlled test where appropriate, and capture the final subject, preview, sender, links and schedule. A copied broadcast can be a useful shortcut; it is never evidence that a second send is authorized.
No Migma or Resend account was operated for this guide, so copy behavior beyond the cited documentation remains unverified. Start with one unsent draft and complete the worksheet before using any duplication endpoint in a production campaign. For concurrent agents editing the same object, use the separate single-writer protocol.
Sources behind this page
Claims remain tied to dated source review. Method and corrections stay public.