Protect permission and sending identity, stage the cutover, interpret reports, and diagnose failures without guessing.
Migrate in stages: inventory, clean, map, test a consented segment, reconcile results, and cut over only after the critical journeys pass. Keep the old system available until rollback is no longer needed.
Reach a controlled first send and keep the system explainable after launch.
Read the starting guide →Start with the question that can change your decision. Each summary below gives the current bottom line and opens a complete guide with evidence, limits, and practical next steps.
Migrate in stages: inventory, clean, map, test a consented segment, reconcile results, and cut over only after the critical journeys pass. Keep the old system available until rollback is no longer needed.
Work through this decision →Import only people with a valid permission basis and preserve records that should remain suppressed. A clean file is not proof of consent.
Work through this decision →Use the exact records shown in your MailerLite account and edit DNS only at the authoritative host. Preserve existing SPF mechanisms instead of publishing a second SPF record.
Work through this decision →Most failures reduce to wrong authority, altered names or values, duplicate SPF policies, or propagation. Change one variable at a time and compare against the records in the live account.
Work through this decision →If you are beginning from scratch, this sequence moves from overall fit to the details most likely to alter cost, risk, or implementation. If you already know the basics, jump directly to the guide that resolves your remaining uncertainty.
Inventory subscribers, fields, groups, forms, templates, automations, domains, reports, and integrations before a staged cutover.
Prepare CSV data, map fields and groups, retain consent, avoid purchased lists, handle rejected records, and prevent accidental automation entry.
Add the records supplied by MailerLite, avoid duplicate SPF records, verify DNS ownership, understand propagation, and document the sending setup.
These pages are deliberately separated when they answer different buyer questions. Related links reconnect the parts without forcing you through a fixed reading order.
Inventory subscribers, fields, groups, forms, templates, automations, domains, reports, and integrations before a staged cutover.
Read the guide →Important limitationsPrepare CSV data, map fields and groups, retain consent, avoid purchased lists, handle rejected records, and prevent accidental automation entry.
Read the guide →Practical guideAdd the records supplied by MailerLite, avoid duplicate SPF records, verify DNS ownership, understand propagation, and document the sending setup.
Read the guide →Practical guideWork through incorrect hosts, changed values, duplicate SPF records, lookup limits, propagation, and edits made at the wrong DNS provider.
Read the guide →Practical guideUse authentication, consent, list quality, cadence, complaint handling, monitoring, and gradual change to support reliable email delivery.
Read the guide →Practical guideReview delivery, clicks, unsubscribes, complaints, automations, acquisition sources, and business outcomes without mistaking dashboards for conclusions.
Read the guide →Practical guideDiagnose missing subscribers, silent automations, failed imports, broken forms, unexpected sends, reporting gaps, and integration delays.
Read the guide →