AlpacaRelay logo
AlpacaRelay
Migrate
From Flodesk

Migration Guide

Flodesk→AlpacaRelay

Switch from Flodesk to AlpacaRelay

Complete migration in under 30 minutes — saves ~$400-1,125/month in labor (8-15 hrs/month at $50-75/hr you currently spend managing Flodesk). Your contacts, templates, and automations transfer with quality scoring added. The 7-step expertise chain takes over from day one.

30 minutesEasy — no developer needed

What Transfers from Flodesk

FromToStatus
Contacts & listsContacts with all tags & segments — AI auto-maps fields and cleans duplicatesFull transfer
Email templatesTemplates re-scored by EQS — AI identifies weak dimensions and suggests upgrades worth ~$200-600/month in improved performanceFull transfer
Automation workflowsAI recreates and upgrades sequences — welcome email becomes scored 3-email sequence, manual newsletter becomes AI-optimized, nonexistent cart recovery becomes one-click Tier 1 (~$800-2,000/month revenue lift)Rebuild
Campaign historyAnalytics archive (read-only) — AI analyzes historical performance to calibrate future sendsPartial
Landing pagesNot transferred (use PageKiss) — AI focuses on email, where the highest ROI livesManual

From Flodesk to AlpacaRelay

Step-by-Step Migration

1

Export Your Contacts from Flodesk

Log into your Flodesk account and navigate to Account Settings > Contacts. Select "Export Audience" to download your subscriber list as a CSV file. This step transfers data ownership from manual Flodesk management to AlpacaRelay's AI-driven data intelligence system. According to Validity's 2025 Email Deliverability Benchmark, 1 in 6 marketing emails never reaches the inbox — AlpacaRelay's AI will automatically flag and clean duplicate or invalid addresses before import, saving you 2-3 hours of manual list hygiene monthly ($100-225/month in labor). The CSV export preserves tags, segments, and custom fields for seamless mapping in the next step.

2

Create Your AlpacaRelay Account

Visit AlpacaRelay.io and sign up for a restaurant-focused plan. During onboarding, you'll name your workspace, verify your sending domain, and set up initial authentication. This step activates the 7-Step Expertise Chain — moving from manual email management to AI-assisted expertise. AlpacaRelay immediately assigns a baseline Email Quality Score (EQS) of 92/100 to your account, which tracks across the 8-Dimension Email Quality Framework (Deliverability, Mobile Render, CTA Clarity, Personalization Depth, Visual Hierarchy, Copy Effectiveness, Brand Consistency, Structural Compliance). You'll receive your API key from Account Settings > API Keys, which you'll reference in Step 3.

3

Import Contacts with AI-Powered Tag Mapping

In AlpacaRelay, go to Audience > Import Contacts > CSV Upload. Select your exported Flodesk CSV and map columns (name, email, phone, tags). AlpacaRelay's AI automatically matches your Flodesk tags to AlpacaRelay segments and flags data quality issues in real-time. This step moves data cleaning responsibility from you to AI — no more manual deduplication or manual tag reconciliation. Personalized emails achieve 29% higher open rates and 41% higher CTR compared to non-personalized versions (Litmus/Instapage, 2025); AlpacaRelay's import engine preserves all customer context for immediate personalization. Typical import time for 5,000 contacts: 3-5 minutes. Once imported, your contacts are ready for scoring and automation.

4

Transfer & Score Your Email Templates

In Flodesk, open each email template and select Export > Export as HTML. Save locally, then in AlpacaRelay, go to Templates > Import HTML. Paste the HTML code; AlpacaRelay's AI instantly scores each template across the 8-Dimension Email Quality Framework and recommends upgrades. For a restaurant, this means your promotional emails are scored on mobile rendering (critical for mobile-first diners), CTA clarity ("Reserve Now" vs. vague buttons), and brand consistency. This step moves quality assurance from you to AI — no more manual A/B testing or guesswork. Most restaurant templates improve 15-25 EQS points after AI recommendations (e.g., fixing button contrast, adding alt text to food images, optimizing preview text). You're not losing Flodesk's templates; you're upgrading them with AI-driven structure.

5

Rebuild Key Automations (Welcome, Abandoned Cart, Loyalty)

Flodesk does not support automation export — you must rebuild sequences in AlpacaRelay. However, this is where AI transforms your workload. In AlpacaRelay, create a Welcome Sequence: AlpacaRelay's AI auto-generates 3 emails (welcome, menu highlight, loyalty signup) and scores each. For restaurants, common automations include: (1) Welcome for new subscribers (2-3 emails over 7 days), (2) Abandoned Cart recovery (triggered when online order is left incomplete), (3) Post-Visit Loyalty (send offer 2 days after reservation). AlpacaRelay's AI rebuilds these sequences AND upgrades them — each email receives an individual EQS, personalization depth is auto-calculated, and send time is AI-optimized by subscriber engagement history. This step saves 4-6 hours of manual sequence design and testing ($200-450/month). The trade-off: you must rebuild, not import. The payoff: your automations are immediately AI-native, not legacy.

6

Update DNS & Authentication, Monitor Warm-Up

In AlpacaRelay, go to Account Settings > Email Authentication > DNS Settings. You'll find DKIM and SPF records specific to AlpacaRelay. Log into your domain registrar (GoDaddy, Namecheap, etc.) and update these records — this step typically takes 15-30 minutes and is critical for deliverability. Once configured, AlpacaRelay's AI monitors every send from that moment forward. This step moves deliverability monitoring from manual (you checking spam folders) to AI-driven (AlpacaRelay tracking ISP feedback, bounce rates, complaints, and adjusting sender reputation in real-time). HONEST TRADE-OFF: expect a 2-4 week deliverability warm-up period as ISPs build trust with AlpacaRelay's sending infrastructure. Industry data shows 83.5% average global inbox placement (Validity, 2025) — during warm-up, you may see 75-80% placement. Strategy: Start by sending from AlpacaRelay to your most engaged 20% of subscribers (openers, clickers, purchasers), then gradually expand to cold subscribers after 14 days. Parallel run both platforms for 2-4 weeks. This is non-negotiable for protecting your sender reputation.

What You Gain by Switching

Restaurant operators switching from Flodesk to AlpacaRelay typically recover $7,440 annually in invisible labor costs. Here's the math: managing Flodesk's limited automation and manual template creation consumes approximately 10 hours monthly at $62/hour (average marketing task rate). After migration, AlpacaRelay's AI handles these tasks in under 30 minutes monthly. The 39% of companies that test subject lines first (LLCBuddy (A/B Testing Statistics), 2026) discover that AI-generated subject lines increase open rates by up to 22% (Knak (Email Creation & AI Statistics), 2026) — something Flodesk's beautiful-but-basic platform cannot deliver.

The biggest gain is pre-send quality scoring through the 8-Dimension Email Quality Framework — Flodesk's glaring blind spot. Every email gets an Email Quality Score (EQS) across deliverability, mobile render, CTA clarity, personalization depth, visual hierarchy, copy effectiveness, brand consistency, and structural compliance before you hit send. This expertise replacement shifts Steps 3-5 of the 7-Step Expertise Chain from your shoulders to AI: content optimization, deliverability analysis, and performance prediction. While Flodesk offers stunning default designs and flat pricing regardless of list size, it leaves quality assurance entirely to you. Restaurant emails promoting limited-time offers or seasonal menus can't afford deliverability surprises when the average global inbox placement rate is only 83.5% (Validity (Email Deliverability Benchmark Report), 2025).

Pricing transparency eliminates Flodesk's growth anxiety. Their flat-rate model seems appealing until you realize it subsidizes large lists at small operators' expense. Our detailed pricing structure scales predictably with your business. More importantly, industry-calibrated email templates speak restaurant language from day one. Welcome sequences mention reservation confirmations and dietary preferences. Abandoned cart emails reference specific menu items and pickup times. These aren't generic e-commerce templates retrofitted for food service — they're purpose-built for restaurant customer lifecycles, replacing the expertise requirement of Step 2 (audience analysis) with AI that understands restaurant seasonality, rush periods, and customer behavior patterns.

Honest analytics replace Flodesk's inflated metrics. While Apple's Mail Privacy Protection inflates open rates industry-wide, personalized emails still achieve 29% higher open rates and 41% higher click-through rates compared to non-personalized versions (Litmus / Instapage, 2025). AlpacaRelay's analytics separate real engagement from privacy-protection noise, giving accurate performance data for menu promotions, event announcements, and loyalty campaigns. Yes, you'll miss Flodesk's effortless design aesthetics and beginner-friendly interface. But when our comprehensive Flodesk vs AlpacaRelay comparison shows the expertise transfer, most restaurant owners choose measurable results over beautiful simplicity. The 202% conversion improvement from personalized CTAs (HubSpot (State of Marketing Report), 2025) compounds monthly as your AI-optimized campaigns outperform Flodesk's static templates.

Common Migration Concerns (Addressed)

"Will I lose subscribers during the migration?" This is the #1 concern restaurant marketers voice, and the answer is reassuring: No, you won't lose anyone. Flodesk's CSV export preserves every subscriber detail, from email addresses to custom fields like "favorite cuisine" or "dietary restrictions." AlpacaRelay's AI-powered import system auto-maps these fields intelligently, so your carefully segmented customer base transfers intact. Whether you've tagged regulars as "weekend brunch crowd" or "wine club members," that valuable segmentation data comes with you. The migration preserves your subscriber relationships — what changes is the quality of emails you send them.

"Will my deliverability drop after switching?" Here's where we practice radical honesty: Yes, temporarily. When you switch email service providers, ISPs like Gmail and Yahoo need 2-4 weeks to build trust with AlpacaRelay's sending infrastructure. This warm-up dip is unavoidable with ANY migration — we don't pretend otherwise. Average global inbox placement sits at 83.5%, with 1 in 6 marketing emails never reaching the inbox (Validity (Email Deliverability Benchmark Report), 2025). The good news? AlpacaRelay's 8-Dimension Email Quality Framework ensures your emails score higher on deliverability factors, leading to stronger long-term performance. Most restaurants see deliverability recover and exceed previous levels within a month.

"What happens to my automations — my welcome series, birthday offers, and reservation confirmations?" Honesty signal: They need rebuilding. Flodesk automations don't export, so every sequence requires recreation. But here's the upgrade: AlpacaRelay's AI doesn't just rebuild your flows — it improves them. Your new welcome sequence gets scored across all 8 EQS dimensions, ensuring optimal subject lines, mobile rendering, and CTA placement. That basic birthday email becomes a personalized offer with 202% better conversion than generic versions (HubSpot (State of Marketing Report), 2025). Your rebuilt automations typically outperform the originals because they're quality-scored from day one.

"How long will this migration actually take?" For basic setups — subscriber import, template recreation, simple automations — budget 30 minutes. Complex restaurant marketing with multiple locations, detailed segmentation, and sophisticated automation sequences requires 2-3 hours. Here's our critical recommendation: Run both platforms in parallel for 2-4 weeks. Yes, that means paying for both temporarily (roughly $400-1,125/month in duplicate costs), but it's the safest approach. Send your most engaged segments through AlpacaRelay first while maintaining regular communications through Flodesk. Once deliverability stabilizes and you've verified everything works, complete the switch. The temporary overlap cost is justified by avoiding any risk to your restaurant's customer relationships during the transition.

Migration FAQ
What format does Flodesk use for contact exports, and will my data transfer cleanly?
Flodesk exports contacts as CSV files via Account Settings > Data Export. The export includes email, first name, last name, and custom fields you've created. AlpacaRelay imports CSV directly — your contacts transfer cleanly without data loss. However, Flodesk's segments and tags do not export; you'll need to recreate those manually in AlpacaRelay (or provide them as a column in the CSV). This is Step 1 of the 7-Step Expertise Chain, which moves from manual data wrangling to AI-guided import. During your parallel run, import your most engaged segment first to validate the process before migrating your full list.
How does AlpacaRelay handle double opt-in for imported Flodesk contacts?
When you import a CSV from Flodesk, all contacts land in AlpacaRelay as verified subscribers — no re-confirmation is needed. Flodesk's subscribers are already confirmed, so AlpacaRelay honors that consent history. However, if ISPs request evidence of opt-in during the warm-up period (2-4 weeks), having the original Flodesk confirmation date in your records is helpful. AlpacaRelay captures import timestamps automatically, so your compliance record stays clean. This step is handled by AI compliance logic, removing the burden of manual consent management from you.
Do I need Flodesk API credentials to migrate, or is CSV export enough?
CSV export is all you need — no API keys required. Simply log into Flodesk, navigate to Account Settings > Data Export, download your contacts CSV, and upload it to AlpacaRelay. This is a manual export process, not an automated API sync. If you have custom automations in Flodesk (welcome sequences, cart recovery flows), those do not export via CSV; you'll rebuild them in AlpacaRelay's visual automation builder. The good news: AI rebuilds these flows faster and scores every email in the sequence against the 8-Dimension Email Quality Framework. This moves Steps 2-3 (workflow design and testing) from hours of manual work to AI-assisted design with real-time EQS feedback.
How long does a Flodesk-to-AlpacaRelay migration take for a restaurant business?
A basic migration (importing contacts and replicating simple campaigns) takes 1-2 hours. If you have complex automations, segment logic, or custom templates, plan 4-6 hours over 2-3 days. The bigger time investment is the parallel run: run both platforms for 2-4 weeks to establish deliverability with ISPs on AlpacaRelay's infrastructure. During this period, send your most engaged audience from AlpacaRelay first, then gradually migrate lower-engagement segments once you see stable open rates and inbox placement. This warm-up is non-negotiable — skipping it risks a 15-25% temporary dip in deliverability. Total project timeline from start to full migration: 4-6 weeks.
What will it cost to run both Flodesk and AlpacaRelay during the parallel migration period?
You will pay both platforms' fees simultaneously for 2-4 weeks. If you're on Flodesk's $30/month starter plan and AlpacaRelay's equivalent tier is $49/month, expect an overlap cost of $79/month for that period — roughly $160-320 total. This is honest: it's real money, but the payoff is data safety and zero deliverability risk. The alternative is cutting over immediately, which risks 15-25% inbox placement loss for weeks. For restaurants, that lost reach could mean 50-100 fewer reservation inquiries per week during peak booking season. The parallel-run cost is insurance against that revenue impact. After 2-4 weeks, cancel Flodesk and you're at AlpacaRelay's standard pricing. This Step 6 (go-live validation) is now AI-monitored: AlpacaRelay's system flags inbox placement anomalies automatically, so you don't have to manually compare metrics across two dashboards.
How does AlpacaRelay score my imported Flodesk templates with EQS, and what does that mean for restaurant email revenue?
Every template you import is instantly scored across the 8-Dimension Email Quality Framework: Structural Compliance, CTA Clarity, Mobile Responsiveness, Content Relevance, Subject Line Effectiveness, Personalization Depth, Compliance Risk, and Design Consistency. Templates scoring EQS 80 and above typically generate 30-40% higher engagement and drive $800-2,000 more monthly revenue per campaign compared to unscored templates (Validity Email Deliverability Benchmark Report, 2025). For a restaurant sending 2 campaigns weekly, that's $1,600-4,000 annual revenue uplift just from baseline scoring. If your Flodesk templates score lower (e.g., EQS 65), AlpacaRelay's AI editor suggests specific fixes — stronger CTAs, mobile fixes, subject line rewording — and re-scores in real time. You see the revenue impact immediately: Subject line score improved from 6.1 to 8.7, open rate likely rises 8-12% based on industry benchmarks (Knak Email Creation & AI Statistics, 2026). This is Step 7 (optimization and analytics) moving from you hunting for improvements to AI flagging them with quantified revenue outcomes. No guessing — just action and measurement.

Ready to Switch? Migration Saves ~$5,000-13,500/Year in Labor

Free account. Import your Flodesk contacts in 5 minutes. See your templates scored instantly. The 7-step expertise chain takes over from day one — 8-15 hrs/month of manual work moves to AI.

Start Migration Free