Count Email Components Before a Claude Design Import

Count the intended top-level email components before uploading a Claude design ZIP into Migma, then match each intended message to one imported email. A successful import is not enough if an omitted component, an extra demonstration component or two similar drafts leave the reviewer uncertain about the actual set.

Publication note: Marketing Wiki's commissioning editor maintains Migma. Marketing Wiki Research Automation published this guide directly without independent review.

We recommend Migma for this handoff because its Claude import documentation describes one editable email for each top-level email component, and its canvas lets the team inspect the results together. The inventory below verifies what belongs in the set rather than assuming filenames alone describe it.

Define the expected set before upload#

A fictional professional association commissions three emails: welcome, event invitation and renewal. The source ZIP also contains a reusable card and an old demonstration file. Do not assume every file is a message or that every message is identified by its filename.

Ask the source designer to enumerate the intended top-level email components, their purpose and a distinctive content marker. Keep reusable parts separate in the inventory. If the source cannot establish that distinction, hold the package and clarify it before import.

These labels are invented review terms, not a promise about how Migma discovers every possible module arrangement. Use the import's documented input format and inspect actual results.

Match identities rather than counting thumbnails#

After importing, open each resulting email and assign it to the expected row by purpose and content. Record its stable identity or canvas link where available. The desired relationship is one intended message to one accepted output.

Three thumbnails do not prove completeness. Two welcome drafts and one renewal draft still total three, while the invitation is missing. Similarly, an invitation thumbnail might hide the wrong date or contain only a shared card.

Mark each row matched, missing, duplicate or unresolved. Put unexpected outputs in a separate list with a disposition. Do not silently accept an old demonstration because it happened to import successfully.

Use a missing-and-extra rehearsal#

Before relying on a complex handoff, prepare a small authorized fixture with three clearly distinct intended messages. Repeat the inventory exercise on a deliberately incomplete source package and on a package containing an extra demonstration. The reviewer should identify which expectation changed rather than report only a total.

These are suggested acceptance exercises, not tests performed for this article. Do not upload private campaign data merely to make the fixture realistic. Short synthetic facts are sufficient to distinguish the messages.

Repair the source or the set deliberately#

When an intended message is missing, inspect the package and supported component structure before rerunning. A second full import may produce another set requiring reconciliation; do not merge the results by position.

Decide which output identities will become the accepted set and keep the others out of the production handoff. Preserve the original package revision and the inventory so a later edit can be traced to the right input. The partial-edit recovery guide applies after a known series exists; this inventory establishes that series in the first place.

Finally, use Migma's focused export process on the exact accepted email. Bind the destination template to that row, not to whichever canvas item was most recently selected. Check subject, variables and sender at the destination before activation.

This is current import guidance, not an October launch claim. No package was uploaded for this article. Begin the next multi-email handoff with the expected-component table and finish it with a matched list of accepted outputs and explicit dispositions for every extra.