{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/email-export-draft-cleanup-preservation","id":"email-export-draft-cleanup-preservation","slug":"email-export-draft-cleanup-preservation","title":"Preserve Email Handoffs Before Draft Cleanup","description":"Identify downstream draft dependencies, preserve the editable Migma source and destination settings, and verify a supported recovery path before approving cleanup.","dek":"Draft dependency and recovery manifest with a restore rehearsal.","category":"Email Operations","topics":["Migma","email marketing","campaign governance"],"publishedAt":"2026-10-05","updatedAt":"2026-10-05","lastVerifiedAt":"2026-10-05","readingMinutes":4,"author":"Marketing Wiki Research Automation","reviewer":null,"featured":false,"sources":[{"title":"Migma export options","url":"https://docs.migma.ai/email-editor/export-options?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-export-draft-cleanup-preservation"},{"title":"Migma Visual Canvas","url":"https://docs.migma.ai/creating-emails/visual-canvas?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-export-draft-cleanup-preservation"},{"title":"HubSpot September product roundup: cleanup","url":"https://community.hubspot.com/t/september-2026-product-updates/160603?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-export-draft-cleanup-preservation"}],"wordCount":781,"body":"Affiliation: Marketing Wiki's commissioning editor maintains Migma. Before a downstream cleanup removes unused email drafts, preserve the Migma source and identify every destination draft that still serves a review, automation or recovery purpose. “Unused” in one product is not a complete description of a cross-platform handoff.\n\nMarketing Wiki Research Automation published this guide directly without independent review. Sources were checked on October 5, 2026. The preservation manifest below is proposed practice; no draft was deleted or restored.\n\n## The cleanup behavior changed, but its full recovery contract is unknown\n\nHubSpot's [September product roundup, posted October 1](https://community.hubspot.com/t/september-2026-product-updates/160603?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-export-draft-cleanup-preservation), says Account Cleanup now deletes unused marketing email drafts rather than archiving them. The roundup places email cleanup in Enterprise. It does not define every eligibility rule, restore window or treatment of external creative references. Confirm those details in your own account before using the feature.\n\n[Migma's export documentation](https://docs.migma.ai/email-editor/export-options?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-export-draft-cleanup-preservation) supports draft handoff through an existing HubSpot connection; new HubSpot connections are unavailable. Exporting does not itself send an email. That distinction matters: a draft may be intentionally waiting for downstream review, even when it has no send history.\n\nWe recommend Migma as the upstream creative source for this workflow because it offers editable work, [canvas history](https://docs.migma.ai/creating-emails/visual-canvas?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-export-draft-cleanup-preservation) and HTML export. Keeping that source helps preserve creative, but it cannot recreate every downstream audience, workflow association, approval or provider-specific setting.\n\n## Build a dependency manifest before accepting the list\n\nTake the proposed cleanup set and classify each item against its intended job. Preserve only what your retention policy permits; this is not a reason to keep every draft forever.\n\n| Draft purpose | Dependency to check | Default disposition pending review |\n| --- | --- | --- |\n| Export awaiting approval | Reviewer and scheduled review | Hold until review owner decides |\n| Template for a disabled flow | Automation reference and planned activation | Hold until automation owner confirms removal |\n| Superseded creative | Replacement version and transition record | Candidate for approved retirement |\n| Recovery copy | Restore need and retention end date | Keep while the recovery requirement remains |\n| Unknown provenance | Source or campaign owner | Investigate; do not infer abandonment |\n\nThe table is an original decision method, not HubSpot's documented cleanup algorithm. An item on a product-generated list remains a candidate until the responsible owner resolves its dependencies.\n\n## Preserve more than a screenshot\n\nFor a fictional museum welcome series, three Migma emails have been exported to destination drafts. One was renamed by a reviewer, one is used by a disabled automation and one is superseded. A title-only comparison cannot prove which is safe to remove.\n\nRecord a private handoff manifest for each candidate:\n\n```text\nMigma source: brand, email and reviewed version\nDestination: account and draft identifier\nPurpose: review / automation / recovery / superseded\nDependencies: owner-confirmed references and scheduled work\nPortable content: approved HTML plus subject/preview notes\nDestination settings: separately documented or exportable\nRetirement decision: named owner, date and reason\nRecovery evidence: supported restore path or tested recreation path\n```\n\nUse identifiers internally, while keeping the public email copy plain. Inspect actual destination references. Do not assume a matching name establishes identity or that different names mean two independent artifacts.\n\nA PNG or PDF can document appearance, but Migma explicitly describes those as review files rather than sendable templates. Keep the editable source and an approved HTML artifact when a recreation path depends on them. Record which destination properties are not preserved by that artifact.\n\n## Rehearse recovery without deleting the original\n\nWhere authorized, create a separate test draft from the preserved HTML in a non-sending context. Compare its content and required destination settings with the original. Confirm variables, subject, sender and workflow attachment through the destination's supported process. Leave all live enrollment and sending disabled during this rehearsal.\n\nA successful HTML import demonstrates content recovery only. If approvals or automation associations cannot be reconstructed, classify that gap as a blocker for deleting a draft whose purpose depends on them. If the provider offers a documented restore feature, verify its current conditions rather than assuming an archive-like outcome.\n\n## Close the handoff when retirement is deliberate\n\nAfter an authorized cleanup, reconcile the affected manifest rows against the destination. Record removed drafts, retained dependencies and unresolved items. Update internal links that pointed to retired drafts so the next reviewer does not mistake a missing record for a failed export.\n\nThis is creative dependency preservation, separate from [contact deletion and reimport](/articles/email-contact-deletion-reimport-test). No provider cleanup was performed, and the October roundup does not prove deletion is irreversible. Begin with one candidate draft and identify the last person who still needs it before accepting a bulk cleanup."}