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 →Practical guideAuthentication works when the current DNS records are correct, non-duplicative, aligned, verified, and monitored after change. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideStart with permissioned engaged recipients, consistent identity, expected volume, monitored results, and slow changes based on evidence. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideDefine inactive, invalid, risky, suppressed, and valuable contacts separately before removing or excluding anyone. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideSeparate hard, soft, policy, temporary, and configuration failures before changing the list or sending setup. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideInvestigate list source, promise, sender recognition, frequency, content, authentication, and complaint concentration without hiding the signal. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideHonor the request promptly, preserve suppression, avoid re-importing, and analyze patterns without obstructing departure. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideThe flow needs clear consent, recognizable sender, deliverable confirmation, expiry or retry behavior, and a record of completion. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideA permission record should show who consented, when, where, to what, and how later changes or withdrawals are handled. Use a practical, source-bounded process to verify the fit.
Read the guide →Important limitationsThe tool supports part of compliance; the operator still owns lawful basis, notices, retention, requests, contracts, and configuration. Use a practical, source-bounded process to verify the fit.
Read the guide →Important limitationsA compliant sending process needs accurate identity, non-deceptive content, a valid address, a functioning opt-out, and monitored vendors. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideChoose a practical starting window, respect time zones and expectations, then compare matched sends with a predefined metric. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideA resend should target a defined non-response, change a justified element, respect frequency, and measure incremental value and complaints. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideOpens and clicks are platform signals; revenue, qualified leads, and durable behavior need their own source records and limitations. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideSave subscriber fields, groups, segments, suppression state, templates, reports, and configuration evidence before migration or bulk edits. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideA sending incident needs a fast pause path, severity rule, evidence capture, owner, correction, subscriber communication, and prevention review. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideA dependable newsletter process covers purpose, audience, content, links, consent, QA, sending, replies, and a post-send decision. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideRe-engagement should define inactivity, offer a meaningful choice, protect suppression rules, and remove or reduce sending when no response follows. Use a practical, source-bounded process to verify the fit.
Read the guide →Practical guideA suppression record should prevent sending when a person unsubscribes, complains, hard-bounces, or meets another documented exclusion rule. Use a practical, source-bounded process to verify the fit.
Read the guide →