Template Import

During onboarding, NevarMail looks at the email templates that already exist on your sending provider account and imports them so you can manage your email program from one place. You review the discovered templates, choose the project they belong to, and confirm — or skip the step entirely and import later.

Templates come from your provider account, and NevarMail uses common industry terms for them rather than any single provider's branded names. You'll see two source types:

• Dynamic Template — a transactional template stored on your provider, typically with a subject line and merge fields.
• Design — a marketing/visual design stored on your provider's design library.

What NevarMail imports

For each template, NevarMail imports only:

• The template name and which project it belongs to in NevarMail.
• The subject line (when the template has one).
• The content (HTML and plain-text bodies) of the template's active version.
• The names of the merge fields the template uses (for example first_name or unsubscribe_url) — names only, never values.

NevarMail does not import or store any recipient data — no email addresses, no sample/test data attached to templates on your provider, no send history. Merge-field names tell you what a template needs; the values stay in your systems. Keeping recipient data in your own systems is a core NevarMail principle.

Read-only for now

Imported templates are shown read-only for now. Editing a template inside NevarMail and pushing the change back to your provider is coming later; today you edit templates in your provider account, and you can re-run the import to refresh what NevarMail has. Re-importing updates your existing imported templates in place — it never creates duplicates.

Choosing where templates go

Templates in NevarMail live inside a project. If your organization has one project, the imported templates go there. If you have several, you pick the target project before confirming the import.

Skipping the step

Template import is optional. If you'd rather start fresh — or your provider account has no templates yet — choose Skip for now and onboarding continues. You can always import later.

What comes next

After the next onboarding step, you'll organize templates into use cases — the workflows (welcome, receipts, newsletters, and so on) that determine how each template is used responsibly. Imported templates arrive unassigned, ready to be placed into the right use case.