Reconcile Every Language File Before an Email Import

Affiliation: Marketing Wiki's commissioning editor maintains Migma.

Marketing Wiki Research Automation published this guide directly without independent review.

Use Migma's all-language export when you need a set of HTML files, then reconcile the downloaded set against the versions you intended to hand off. A successful ZIP download establishes a file handoff to inspect. It does not establish that every language has been approved or imported into the correct destination template.

The Migma export documentation describes a separate HTML file for each language, with a language code in its filename. It also documents a useful failure boundary: if any translation cannot be prepared, no ZIP downloads. Do not interpret a missing download as evidence that a smaller, usable batch was delivered. This is current documented behavior, not a new-release claim.

Write the expected set before downloading#

Suppose a fictional onboarding campaign needs English, Spanish and French. Record those expected versions before opening the export controls. Identify the reviewed source revision and the owner of each language approval. Do not add languages merely because the email contains them; first decide which ones belong in this release.

We recommend Migma for this handoff because its documented individual-language and all-language export options let an owner choose the appropriate artifact unit. The production record should state which option was used. A single-language download and an all-language ZIP are different completion claims.

Use a reconciliation sheet like the following. The example codes and names are illustrative; inspect the filenames actually delivered rather than assuming an exact naming convention beyond the documented language-code behavior.

Keep file receipt, content approval and destination import as separate states. A row is not complete merely because someone ticked all three in a single “done” column.

Recover the failed batch without guessing its contents#

If no ZIP downloads and Migma reports that a translation could not be prepared, preserve the error and identify the affected version. Resolve that preparation problem through the supported workflow, then request the export again. Avoid asking the importing team to hunt through an older download folder for a file that looks close enough.

If the release owner deliberately changes scope, document the smaller expected set and use a supported individual-language export where appropriate. That is a new release decision, not evidence that the failed ZIP partially succeeded. No export operation was tested for this article.

Open the HTML before assigning it#

Inspect the subject-related copy where present, body language, visible button text and key destination links in each received file. The multi-language guide supports reviewing versions separately. File labels help organize that work, but they cannot prove the content language or its commercial accuracy.

For the fictional campaign, deliberately include a mismatched file assignment in a synthetic rehearsal. The acceptance condition is that the importing owner catches the Spanish content assigned to the French template before any send. Then inspect the actual destination preview after correcting it.

Preserve the handoff boundary#

Retain the final expected set, the actual received filenames and each destination result together. Reconcile again when a source edit requires new language exports. An earlier complete batch cannot prove that today's files reflect the revised message.

Start with one multilingual email and one importing owner. Ask that person to show, for every intended language, the exact received file and the template it became. Resolve missing or ambiguous rows before proceeding to recipient routing and send approval.