Dostavljivost in higiena email baze

Kako zamenjati email platformo, ne da bi škodovali dostavljivosti

Posted on July 18, 2026 by

Zamenjava email platforme ne sme škodovati dostavljivosti, ker ugled, ki šteje najbolj — ugled vaše pošiljateljske domene — potuje z vami. Kar se spremeni, je vse pod njim: novi pošiljateljski IP-ji, novi zapisi za avtentikacijo, nova infrastruktura, ki je Gmail in Microsoft še nista videla v paru z vašo domeno. Naredite štiri stvari pravilno, po vrsti, in menjava je nedogodek. Avtenticirajte svojo domeno na novi platformi, preden karkoli pošljete. Uvozite svoj seznam za onemogočanje (odjave, trde zavrnitve, pritožnike zaradi neželene pošte) skupaj s stiki. Najprej pošiljajte svojim najbolj angažiranim ljudem. In povečujte do polnega obsega v dveh do štirih tednih, ne čez noč. Preskočite uvoz seznama za onemogočanje in pošiljali boste ljudem, ki so se odjavili pred leti; ta ena napaka povzroči več škode pri selitvi kot vse ostalo na tej strani skupaj.

Kaj se dejansko spremeni, ko zamenjate platformo

Ponudniki nabiralnikov spremljajo dva ugleda: enega za vašo pošiljateljsko domeno in enega za IP naslove, s katerih prihaja pošta. Ugled vaše domene je vaš: odraža leta stopenj pritožb, angažiranosti in kakovosti baze ter pride z vami na novo platformo. IP-ji ne. Na večini platform za spletne trgovine boste pošiljali iz skupnega nabora IP-jev, katerega ugled vzdržujeta platforma in drugi pošiljatelji na njem.

Torej dan po preklopu Gmail vidi znano domeno, ki prihaja z neznane infrastrukture s svežim DKIM ključem. Ta kombinacija sama po sebi ni zaskrbljujoča, a naredi filtre za nekaj tednov občutljivejše kot običajno. Skok pritožb ali skok zavrnitev, ki bi ga vaša uveljavljena postavitev absorbirala, lahko v tem oknu prevesi pošiljanja v mapo z neželeno pošto. Celoten priročnik za selitev obstaja zato, da vaši signali ostanejo dolgočasni, medtem ko si nov par pridobiva zaupanje.

Ena opomba glede razporeda, preden se lotimo česarkoli drugega: tega ne počnite oktobra ali novembra. Selitev želi mirno prodajno obdobje, ker skrbno povečevanje in obseg črnega petka ne gresta skupaj. Pomlad ali sredina poletja je za večino trgovin idealna.

Izvoz, ki se ga nihče ne spomni: vaš seznam za onemogočanje

Vsak se spomni izvoziti stike. Veliko ljudi pozabi, da stara platforma tiho hrani tudi drugi seznam: vse, ki so se odjavili, doživeli trdo zavrnitev ali pritisnili gumb za neželeno pošto skozi vašo celotno zgodovino pošiljanja. Nova platforma ne ve nič o tem.

Izpustite ta izvoz in vaša prva kampanja gre na leta nakopičenih odjav. Pravno je to težava v večini jurisdikcij, saj je treba odjave spoštovati ne glede na to, katero programsko opremo uporabljate. Praktično je še slabše: ljudje, ki so se enkrat odjavili in znova prejeli pošto, se ne odjavijo drugič, temveč pritisnejo “prijavi kot neželeno”. Nekaj sto takih v enem pošiljanju lahko naredi več škode ugledu kot leto normalnih kampanj.

Torej, preden se lotite česarkoli drugega: izvozite odjave, trde zavrnitve in pritožnike s stare platforme in jih uvozite na seznam za onemogočanje nove. Nato naključno preverite deset naslovov, za katere veste, da so se odjavili, in potrdite, da jih nova platforma dejansko blokira.

Nastavite avtentikacijo pred prvim pošiljanjem

Vaša nova platforma vam bo dala DNS zapise za dodajanje, običajno DKIM zapise (pogosto kot CNAME), da so vaši emaili podpisani z vašo lastno domeno, poleg tega pa še vse, kar potrebuje za povratno pot. Dodajte jih, preverite jih znotraj platforme in potrdite, da je vaš DMARC zapis še vedno usklajen, preden gre ven en sam email. Emaili z znane domene, ki nenadoma ne prestanejo avtentikacije, so točno vzorec “znana domena, sumljivo vedenje”, ki ga filtri najstrožje kaznujejo.

Celoten vodnik je v kako avtenticirati pošiljateljsko domeno za spletno trgovino, in če so vam sami akronimi meglen pojem, začnite s SPF, DKIM in DMARC za spletne trgovine. Od leta 2024 Gmail in Yahoo zahtevata, da množični pošiljatelji prestanejo SPF in DKIM ter imajo vzpostavljeno DMARC politiko, Microsoft pa je od takrat uvedel podobne zahteve, zato ta korak ni neobvezna higiena, temveč vstopnica.

Pustite DNS zapise stare platforme na mestu, dokler ta popolnoma ne preneha pošiljati. Če jih odstranite prezgodaj, poškodujete avtentikacijo na emailih, ki še vedno odhajajo med prehodom.

Vrstni red preklopa, ki se izogne dvojnim pošiljanjem

Selitve imajo določeno past, pred katero vas nihče ne posvari, dokler ne stopite vanjo: vzporedno obdobje. Medtem ko sta obe platformi živi, lahko kupec, ki opusti košarico, sproži tok za opuščeno košarico na obeh: dva skoraj enaka emaila, minute narazen, iz iste trgovine. Izgleda pokvarjeno in podvoji vaš obseg pošiljanja točno tistim ljudem sredi nakupa.

Rešitev je strog vrstni red operacij:

Uvozite stike in onemogočanja na novo platformo. Prinesite tudi podatke o angažiranosti, če jih platforma podpira (datum zadnjega naročila, zadnji klik), ker so od tega odvisni spodnji segmenti za ogrevanje.
Znova zgradite svoje tokove na novi platformi, a jih pustite izklopljene. Vsakega preizkusite s svojim lastnim naslovom.
Preklapljajte tokove enega za drugim: izklopite tok za opuščeno košarico na stari platformi, vklopite ga na novi, isto uro. Ponovite za vsak tok. Nikoli ne dovolite, da je isti sprožilec živ na obeh mestih.
Kampanje premaknite nazadnje, začnite z majhnimi angažiranimi pošiljanji, opisanimi v nadaljevanju.
Upokojite staro platformo šele po tem, ko je preklopil vsak tok in je pretekel cel obračunski cikel, ne da bi kaj poslala.

Ogrejte novo platformo s svojimi najboljšimi ljudmi

Prvi dva do štirje tedni pošiljanja so avdicija, zato pošljite svoje uvodne kampanje samo stikom, ki so odprli ali kliknili v zadnjih 30 do 60 dneh. Ti ljudje vas prepoznajo, hitro odprejo in se skoraj nikoli ne pritožijo — točno signali, ki jih želite pripete na novo infrastrukturo. Če angažiranih in neangažiranih stikov še ne ločujete, to zgradite najprej; segmentiranje angažiranih in neangažiranih naročnikov opisuje mehaniko.

Nato postopoma širite: 60-dnevna angažiranost, nato 90, nato vaše običajno polno občinstvo kampanj, s koraki približno teden za tednom in z mirovanjem vsakič, ko zavrnitve ali pritožbe trznejo. Delovni primer: trgovina, ki običajno pošilja 20.000 stikom, bi lahko v prvem tednu poslala 6.000 tistim, ki so bili nedavno angažirani, v drugem tednu 11.000, v tretjem tednu 16.000 in v četrtem tednu celotnemu seznamu (ilustrativne številke; prilagodite svoji bazi).

Da bo meja jasna: to je povečevanje za uveljavljeno domeno na novi infrastrukturi, kar je blažja različica celotnega protokola v kako ogreti novo pošiljateljsko domeno za spletno trgovino. Če menjate domeno in platformo hkrati, raje sledite počasnejšemu razporedu iz tega članka, saj bi začenjali ugled iz nič.

Kaj spremljati med selitvijo in po njej

Spremljajte te vrednosti glede na izhodišče, ki ste ga zabeležili na stari platformi:

Stopnja trdih zavrnitev na kampanjo: naj ostane pod 2 % in blizu vašega starega izhodišča, saj se baza ni spremenila.
Stopnja pritožb zaradi neželene pošte: pod 0,1 %, in vsak skok med vzporednim obdobjem pomeni, da najprej preverite dvojna pošiljanja.
Stopnja odpiranja po ponudniku nabiralnika: če odpiranja pri Gmailu upadajo, medtem ko Outlook drži, se nov par bori specifično z Googlom. Spremljanje te razdelitve je jedro kako spremljati ugled domene za emaile spletne trgovine, kar je vredno vzpostaviti pred selitvijo, da imate podatke pred njo in po njej.
Prihodek toka iz tedna v teden: najhitrejši način, da opazite tok, ki ni preživel ponovne gradnje. Manjkajoč sprožilec za opuščeno košarico se pokaže tu nekaj dni prej, preden ga kdo ročno opazi.

Pričakujte nekaj šuma v prvih štirinajstih dneh. Ukrepajte na podlagi trendov skozi tri ali štiri pošiljanja, ne na podlagi ene mlačne kampanje.

Kje se umešča Omnisend

To selitev sem prestal sam — tako so moje trgovine pristale na Omnisendu, potem ko sem ga preizkusil v neposredni primerjavi s Klaviyom. Deli, ki so v praksi šteli: Shopify sinhronizacija je stike in zgodovino naročil povlekla brez CSV kirurgije, uvozi seznamov za onemogočanje so prvorazredna funkcija in ne zahtevek za podporo, ponovna gradnja tokov pa je vzela popoldne, ker se urejevalnik tokov ne upira. Preverjanje domene z DKIM je voden seznam korakov.

Pošten pridržek: nobena platforma, tudi Omnisend ne, ne more preskočiti ogrevanja ali discipline preklapljanja tokov. Skrbne tedne morate odteči ne glede na cilj. Omnisend je vsak korak le naredil manj zamuden, cenovna razlika glede na Klaviyo pa je bila bonus, ne razlog.

Vaš naslednji korak

Preden se zavežete datumu preklopa, naredite desetminutno različico tega načrta: danes izvozite seznam za onemogočanje s svoje trenutne platforme in potrdite, da so številke videti pravilne. To je korak z najhujšim načinom odpovedi in najlažjim popravkom — in ko je varno v vaših rokah, načrtujte selitev za svoj najbolj miren mesec in se pomikajte po zgornjem vrstnem redu.

Deliverability and List Hygiene

How to Migrate Email Platforms Without Hurting Deliverability

Posted on July 17, 2026 by

Switching email platforms doesn’t have to hurt deliverability, because the reputation that matters most — your sending domain’s — travels with you. What changes is everything underneath it: new sending IPs, new authentication records, new infrastructure that Gmail and Microsoft haven’t seen your domain paired with before. Get four things right, in order, and the switch is a non-event. Authenticate your domain on the new platform before sending anything. Import your suppression list (unsubscribes, hard bounces, spam complainers) along with your contacts. Send to your most engaged people first. And scale to full volume over two to four weeks instead of overnight. Skip the suppression import and you’ll mail people who unsubscribed years ago; that single mistake causes more migration damage than everything else on this page combined.

What actually changes when you switch platforms

Mailbox providers track two reputations: one for your sending domain and one for the IP addresses the mail comes from. Your domain reputation is yours: it reflects years of complaint rates, engagement, and list quality, and it comes with you to the new platform. The IPs don’t. On most ecommerce platforms you’ll be sending from a shared IP pool whose reputation is maintained by the platform and the other senders on it.

So the day after cutover, Gmail sees a familiar domain arriving from unfamiliar infrastructure with a fresh DKIM key. That combination isn’t alarming by itself, but it makes filters more sensitive than usual for a few weeks. A complaint spike or bounce spike that your established setup would have absorbed can, in this window, tip sends into the spam folder. The whole migration playbook exists to keep your signals boring while the new pairing earns trust.

One scheduling note before anything else: don’t do this in October or November. A migration wants a quiet sales period, because the careful ramp-up and Black Friday volume don’t coexist. Spring or mid-summer is ideal for most stores.

The export nobody remembers: your suppression list

Everyone remembers to export contacts. Plenty of people forget that the old platform is also quietly holding a second list: everyone who unsubscribed, hard bounced, or hit the spam button across your entire sending history. The new platform knows none of it.

Miss this export and your first campaign goes to years of accumulated unsubscribes. Legally that’s a problem in most jurisdictions, since opt-outs must be honored regardless of which software you use. Practically it’s worse: people who unsubscribed once and got mailed again don’t unsubscribe a second time, they hit “report spam.” A few hundred of those in one send can do more reputation damage than a year of normal campaigns.

So before touching anything else: export unsubscribes, hard bounces, and complainers from the old platform, and import them into the new one’s suppression list. Then spot-check ten addresses you know unsubscribed and confirm the new platform actually blocks them.

Set up authentication before the first send

Your new platform will give you DNS records to add, typically DKIM records (often as CNAMEs) so your emails are signed by your own domain, plus whatever it needs for the return-path. Add them, verify them inside the platform, and confirm your DMARC record still aligns before a single email goes out. Emails from a known domain that suddenly fail authentication are exactly the “familiar domain, suspicious behavior” pattern filters punish hardest.

The full walkthrough lives in how to authenticate an ecommerce email sending domain, and if the acronyms themselves are fuzzy, start with SPF, DKIM, and DMARC for ecommerce. Since 2024, Gmail and Yahoo require bulk senders to pass SPF and DKIM and to have a DMARC policy in place, and Microsoft has since introduced similar requirements, so this step isn’t optional hygiene, it’s the entry ticket.

Leave your old platform’s DNS records in place until it has fully stopped sending. Removing them early breaks authentication on emails still going out during the transition.

The cutover order that avoids double-sends

Migrations have a specific trap that nobody warns you about until you’ve stepped in it: the parallel period. While both platforms are alive, a shopper who abandons a cart can trigger the abandoned-cart flow on both: two near-identical emails, minutes apart, from the same store. It looks broken, and it doubles your send volume to exactly the people mid-purchase.

The fix is a strict order of operations:

Import contacts and suppressions into the new platform. Bring engagement data too if the platform supports it (last order date, last click), because the warm-up segments below depend on it.
Rebuild your flows on the new platform, but leave them off. Test each with your own address.
Switch flows one at a time: turn the old platform’s abandoned-cart flow off, turn the new one on, same hour. Repeat per flow. Never let the same trigger be live in both places.
Move campaigns last, starting with the small engaged sends described next.
Retire the old platform only after every flow has switched and a full billing cycle has passed without it sending anything.

Warm up the new platform with your best people

The first two to four weeks of sending are an audition, so send your opening campaigns only to contacts who opened or clicked in the last 30 to 60 days. These people recognize you, open quickly, and almost never complain — precisely the signals you want attached to the new infrastructure. If you don’t already keep engaged and unengaged contacts separated, build that first; segmenting engaged and unengaged subscribers covers the mechanics.

Then widen gradually: 60-day engagement, then 90, then your normal full campaign audience, stepping up roughly week by week and holding steady anytime bounces or complaints twitch. A worked example: a store normally mailing 20,000 contacts might send week one to the 6,000 who engaged recently, week two to 11,000, week three to 16,000, and week four the full list (illustrative numbers; scale to your own list).

To be clear about the boundary: this is a ramp for an established domain on new infrastructure, which is a milder version of the full protocol in how to warm up a new ecommerce sending domain. If you’re changing domains and platforms at once, follow that article’s slower schedule instead, since you’d be starting reputation from zero.

What to watch during and after

Track these against the baseline you recorded on the old platform:

Hard bounce rate per campaign: should stay under 2%, and near your old baseline since the list didn’t change.
Spam complaint rate: under 0.1%, and any jump during the parallel period means checking for double-sends first.
Open rate by mailbox provider: if Gmail opens sag while Outlook holds, the new pairing is struggling specifically with Google. Watching this split is the core of how to monitor domain reputation for ecommerce email, which is worth setting up before the migration so you have before-and-after data.
Flow revenue week over week: the fastest way to notice a flow that didn’t survive the rebuild. A missing abandoned-cart trigger shows up here days before anyone spots it manually.

Expect some noise in the first fortnight. Act on trends across three or four sends, not on one soft campaign.

Where Omnisend fits

I’ve been through this migration myself — it’s how my stores ended up on Omnisend after I ran it head-to-head against Klaviyo. The parts that mattered in practice: the Shopify sync pulled contacts and order history in without CSV surgery, suppression imports are a first-class feature rather than a support ticket, and rebuilding flows took an afternoon because the flow editor doesn’t fight you. Domain verification with DKIM is a guided checklist.

The honest caveat: no platform, Omnisend included, can skip the warm-up or the flow-switching discipline. The careful weeks are yours to run regardless of the destination. Omnisend just made each step less fiddly, and the pricing gap versus Klaviyo was the bonus, not the reason.

Your next step

Before you commit to a cutover date, do the ten-minute version of this plan: export the suppression list from your current platform today and confirm the counts look right. It’s the step with the worst failure mode and the easiest fix — and once it’s safely in hand, schedule the migration for your quietest month and work down the order above.