Design then export means you finish the layout in a separate studio, send a Test, then hand your ESP export-ready HTML or MJML, or a Zoho Campaigns draft. The ESP still owns the list and the send. Stay in the ESP builder only when stock blocks and weekly edits are enough.
Use it when you need brand control across campaigns, the same file in more than one sending tool, or an Outlook-safe layout the ESP's blocks won't give you.
When the ESP builder is enough
Stay in the ESP when speed matters more than pixel control. A one-column promo, a welcome note or a short newsletter built from stock blocks rarely needs a separate design pass.
ESP builders also make sense when marketers edit the same template every week and never want to see raw HTML. Drag-and-drop regions, locked brand modules and the platform's merge tags all stay editable inside the tool you send from.
When design-then-export is the better fit
Move the design out of the ESP when you need a layout its drag-and-drop editor won't give you, or when the same file has to go to more than one sending tool. If you're choosing a tool for that, standalone email builders that export to your ESP compares Stripo, Beefree, Milo Email Studio and others.
Common cases:
- Brand and agency handoff. Designers finish the proof, and marketers import the HTML without rebuilding every section.
- Several ESPs or agency clients. One source file can go to several lists.
- Outlook-safe structure you want to control. Nested tables, button cells and MJML compile steps are easier to manage in a proper email studio than in a locked block palette.
- Sign-off before anyone touches the list. A read-only preview link and a Test to your own inbox catch copy and layout problems before the campaign even exists in the ESP.
Side by side
You design inside the tool you send from. Marketers who never open HTML can keep editing. Your layout options are whatever blocks that platform gives you. Moving the campaign to another ESP usually means a rebuild. Proofing and sending happen in one place.
You design and test in a studio, then export HTML or MJML (or push a draft into a connected ESP, where that's an option). The ESP gets finished HTML instead of a canvas you rebuild from scratch, and you keep one source of truth for the layout. Marketers who only know drag-and-drop will edit less after import, unless the ESP supports hybrid modules. The list and the send stay in the ESP.
A practical design-then-export path
Done well, design then export takes work away at each stage rather than adding a step.
Brand once, not per campaign. Your palette, type and button styles sit in a brand kit, so new blocks inherit them. There's no reason to re-pick hex values for every campaign.
A canvas that already suits the inbox. The offer goes in as real text, not just in a banner, in one column around 600px. If you're writing HTML by hand, build buttons as table cells, or use MJML components that compile to that shape.
Problems caught before the ESP sees them. A read-only preview link covers anyone who needs to approve. A Test to an address you control, checked with images off, in dark mode and on a phone (and in classic Outlook if it's on your list), catches the rest.
A file the ESP can take as it is. Most ESPs want compiled HTML. Some teams keep MJML as the editable source and compile it before uploading. If the file doesn't already include the platform's unsubscribe and merge tags, add them after import.
The ESP keeps the send. Upload the HTML through the ESP's custom or code path, or push a draft if your studio and ESP support it (for Milo Email Studio and Zoho Campaigns, see design and push a Zoho Campaigns draft). Preview it again inside the ESP, then send from there as usual. For a file import into your ESP, see design a branded email and export. For HubSpot, see how to import custom HTML into HubSpot.
What usually breaks after import
Merge tags and unsubscribe links. Swap the tags your destination ESP expects before you save the imported template. Many ESPs will reject an HTML upload for marketing email if it hasn't got an unsubscribe tag.
Editable regions. After a full HTML import, you're often editing in code. If marketers need to drag blocks around later, use the ESP's hybrid or module system, or accept that the file gets revised in the studio and re-exported.
File size. Inlined styles and long legal footers push you towards Gmail's clip at around 102KB. Cut something before you add another image. See the HTML email checklist.
Where the handoff usually breaks
When the brief lives in one place, the design in another, the builder in a third and the ESP in a fourth, copy drifts, merge tags get left behind and nobody is sure which file is current. Design then export collapses that: one canvas for brand, layout and sign-off, a Test before the list exists, then one handoff (export-ready HTML or MJML, or a Zoho Campaigns draft). The ESP stays the place you send from.
Questions
Can I build in my ESP's drag-and-drop and still own the HTML?
Only if that path exports reusable HTML. Many drag-and-drop templates never leave the platform. Design then export gives you a file (or a Zoho draft) you can take with you.
Should I export MJML or HTML to my ESP?
Export HTML when the ESP only accepts a compiled file. Keep MJML when your team edits the shorter source and compiles before upload. Either way, the inbox always receives HTML. See why MJML helps.
Does a preview link replace a test send?
No. A preview link is a browser proof for approvals. A test send shows you how the message lands in a real inbox, including image blocking and dark mode. When the stakes are high, use both.
Prefer a head start on the blocks? Ask Milo's AI designer to draft them on the canvas, then finish the proof and hand off.