Loopi
PricingPlaybooks

Playbook · Mail

Migrate your email list to Loopi — without burning your sending domain.

Export your subscribers from Mailchimp, ConvertKit, or a CSV. Import them into Loopi in minutes. Then let the ramp do the work: your most-engaged subscribers get the first email, your domain builds a clean reputation, and your full list gets the welcome by day seven — all scheduled by Iris before a single send fires.

Hand this page straight to Iris. Open your Loopi account, go to the Agents tab, and paste the prompt below to her — say "run the migration for me." She imports your list and schedules the warm-up ramp. You review the plan before anything sends.

What it does for you

Moving your list to a new email platform is the step most business owners skip — or do badly and end up in spam. This play does the whole thing: import, tag, ramp, send. Iris handles the tedious parts. By the end you'll have:

  • Your entire subscriber list inside Loopi — deduped, unsubscribes honored, and your most-engaged subscribers tagged separately so the ramp can start with them.
  • A sending domain with a clean reputation — because the ramp starts with your openers and clickers on day one, giving inbox providers the engagement signal they need before the full list sees any email.
  • A seven-day warm-up scheduled and approved before it fires — you see the dates and subscriber counts, say yes, and Iris handles the rest.
  • No spam folder surprises — the most common reason a migration goes wrong is sending your whole list from a cold domain on day one. This play prevents that.
Is it worth the effort? The import and ramp scheduling takes Iris about two minutes once your CSV is ready — the same work takes most people an afternoon of copy-pasting in a dashboard. The warm-up ramp is what almost every migration skips, and it's what separates a clean sender reputation from a domain that quietly lands in spam for months. Set it up once; every future send goes to a healthy list from a trusted domain.

Four steps, start to finish

Nothing is hidden here. The first two steps are one-time setup. Steps three and four Iris runs from a single prompt.

1 · Export your CSV

From Mailchimp, ConvertKit, or your old tool

→

2 · Set up your sending domain

So the reputation you build is actually yours

→

3 · Import your list

Iris bulk-uploads subscribers, tags engaged ones

→

4 · Warm-up ramp fires

Engaged first, full list by day seven

Export → domain → import → ramp. Steps 3 and 4 run from one prompt to Iris. You approve the schedule before anything sends.

1. Export your CSV

Pull a subscriber export from your current tool — Mailchimp, ConvertKit, ActiveCampaign, or whatever you use. The only columns Iris needs areemail, subscribed (true/false), and tags (so she can identify your engaged subscribers). Everything else can stay in the export; she ignores what she doesn't need. Save the file and keep it open — you'll paste it into the prompt in step four.

2. Set up your sending domain first

A warm-up ramp only works if the emails come from your own domain, not a shared Loopi address. Set up your sending domain — it takes about ten minutes, and Iris confirms it's ready before she starts importing. If you skip this step, your emails send from mail.loopi.social and the reputation you build belongs to Loopi's shared domain, not yours — which defeats the purpose of a ramp.

3. Run one prompt

Paste the prompt below to Iris in your Agents tab, with your CSV appended at the bottom. She creates your list, imports subscribers in batches of 100, tags your engaged subscribers, writes the welcome email, and schedules the two-broadcast ramp. She tells you the plan — dates, counts — before anything sends.

tell Iris
I'm migrating my email list to Loopi.

Step 1 — Create a list.
Create a list called "main list". If a list already exists on this
profile, use that one.

Step 2 — Import subscribers from my CSV.
My CSV has columns: email, first_name, last_name, subscribed, tags.
Parse it and split into two groups:
  - Engaged: rows where subscribed=true AND tags contains "opener" or "clicker"
  - Everyone else: rows where subscribed=true AND NOT in the engaged group
Skip rows where subscribed=false — those are unsubscribes from my old tool.

Import the engaged group first, tagged "engaged".
Then import the everyone-else group with no tag.

Step 3 — Warm-up ramp.
Draft a short "welcome to the new home" email: personal tone,
first-person, one sentence about why I moved, one call to action
back to my site.

Then schedule two broadcasts:
  - Day 1 (tomorrow at 10am): send only to the "engaged" tag
  - Day 7 (seven days from now at 10am): send to everyone

Tell me the scheduled dates, subscriber counts in each group, and how
many were skipped as unsubscribed — before you confirm anything.

My CSV:
[paste CSV here]

Open your Agents tab and run this migration tonight →

The warm-up ramp

Two broadcasts. Day one goes only to your engaged subscribers — the people most likely to open and click. That engagement signal tells inbox providers your domain is trustworthy. By day seven, the full list gets the welcome email to a domain with a clean reputation behind it.

Engaged subscribers only

Day 1

Tagged 'opener' or 'clicker' from your old tool

Domain builds reputation

Days 2–6

Inbox providers register your open rates

Full list

Day 7

Domain established — every subscriber gets the welcome

Two sends, seven days apart. The gap is where the reputation is built. If your engaged group is fewer than 20 people, collapse the ramp to three days.

If your CSV doesn't have engagement tags, import everyone in one batch and skip the ramp — or set day one to a hand-picked list of 20 people you know will open it. The principle is the same: engaged subscribers first.

What Iris does

You provide

You get back

Your CSV export

Emails, subscribed flag, engagement tags

Verified sending domain

Confirmed before the import starts

A Loopi account

Free to start — the only prerequisite

→

Iris

Your Loopi agent, in the Agents tab

→

List created and imported

Subscribers in batches of 100, deduped

Warm-up scheduled

Two broadcasts approved before anything sends

Domain reputation building

Engaged-first send earns inbox trust

Three inputs in, three things running. Iris handles the batching, tagging, and scheduling behind the scenes.

What Loopi handles for you

  • Deduplication on import. Loopi dedupes by email address. Sending the same address twice in different batches is safe — it's marked already subscribed, not duplicated.
  • Unsubscribe suppression. Iris skips rows marked unsubscribed before importing. Addresses that previously bounced or complained are blocked at the Loopi layer and stay suppressed — they're never resurrected even if they appear in a future import.
  • Tag-based ramp targeting. Iris imports your engaged subscribers under one tag and targets that same tag for the day-one broadcast. Day seven sends to everyone. You don't manage segments manually.
  • Compliance on every send. Every broadcast Loopi sends carries a compliant unsubscribe link, List-Unsubscribe headers, and a CAN-SPAM-required footer. You write the welcome; Loopi wires the rest.
  • Schedule confirmation before send. Iris reports scheduled dates and subscriber counts. Nothing fires until you say so.

What the result looks like

After running the prompt on a 1,200-subscriber Mailchimp export, Iris reported back:

  • 1,147 subscribers imported — 53 skipped (48 unsubscribed, 5 invalid addresses)
  • 214 tagged "engaged" — subscribers carrying the "opener" or "clicker" tag in the export
  • Day 1 broadcast: scheduled for tomorrow at 10 am, targeting the "engaged" tag only — 214 recipients
  • Day 7 broadcast: scheduled for seven days from now at 10 am, full list — 1,147 recipients

Iris wrote a two-paragraph welcome email in the owner's voice, linked back to the site, and confirmed both broadcasts. The owner approved in one reply. Total time from pasting the prompt to approved plan: under three minutes.

Your list is already an asset. Move it tonight.

Open your Agents tab and let Iris handle the import, tagging, ramp scheduling, and compliance. The whole migration — CSV to confirmed schedule — takes one prompt.

Get started with Loopi →
loopi
PrivacyTermsloopi.social · 2026