How Warm-up Works
Every Intelligent Golf to GoHighLevel migration must be treated as a reputation-transfer project, not a platform switch. This page explains why that distinction matters, what we are actually building during the warm-up period, and how to judge whether it is working.
Warm Relationship ≠ Warm Infrastructure
A golf club with a ten-year member database, a familiar sender name, and strong historical engagement has a genuinely warm human relationship with its members. That relationship is real and it is an asset. It does not, however, automatically transfer to the new sending infrastructure.
Mailbox providers — Google, Microsoft, Yahoo, Apple — assess trust based on the behaviour of the technical sending identity: the domain, the subdomain, and the IP address. A brand-new sending subdomain (mail.clubname.co.uk) on a fresh GHL sub-account carries zero reputation history. The first emails it dispatches will be scrutinised as if they came from an unknown entity, regardless of whether members have received emails from that golf club for twenty years.
The practical implication: members who would happily read a newsletter from manager@golfclub.co.uk may never see it if the underlying subdomain has not established trust signals with their mailbox provider. Recovery from a bad launch is possible, but it can require weeks of reduced volume and reputation rebuilding. A methodical approach costs the club a short ramp period and prevents that downside entirely.
The single most important framing: we are not warming up an IP address. GHL sends via Mailgun's shared IP pool, which is already warm. What we are building is domain and subdomain reputation — the subdomain has never sent mail before, so mailbox providers have no evidence it is trustworthy, regardless of the IP underneath it.
Why a New Subdomain Starts Cold on a Warmed IP
This is the most commonly misunderstood point in email migration.
GHL routes mail through Mailgun's shared sending infrastructure. Those IPs are actively managed by HighLevel and carry established reputation across many compliant senders. The IP reputation is not the problem.
The problem is subdomain reputation. When mail.highgategc.co.uk sends its first email, Google, Microsoft, and Yahoo have no signal on that subdomain. They will apply maximum scrutiny to early sends. If those sends generate complaints, bounces, or are simply ignored at scale, the subdomain acquires a negative signal that becomes progressively harder to reverse.
Conversely, if the first sends go to genuinely engaged members who open, click, and reply, the subdomain builds a positive track record quickly. That is the entire logic of the engagement-gated ramp: start with the most engaged contacts, earn the right to send to the broader list.
The Myth of the 30-Day Calendar Ramp
The SOP default is an engagement-gated 7–14 day ramp — not a 30-day calendar schedule. The distinction matters.
A calendar ramp advances mechanically on day-of-week regardless of what the data says. An engagement-gated ramp advances when the metrics authorise it. If Day 1 sends land cleanly with spam complaints at 0.04% and hard bounces at 0.2%, you widen volume. If Day 3 shows a spike to 0.18% complaints, you hold and diagnose before advancing.
The 30/60-day schedule is documented as the fallback for genuinely messy situations: stale data, poor engagement history, mixed consent evidence. For a typical Capture club with a clean export from Intelligent Golf, the default is the 7–14 day gated ramp.
Small-List Maths
Our clubs are small. That smallness has direct implications for risk tolerance.
| List size | One complaint | Two complaints | Three complaints |
|---|---|---|---|
| 500 members | 0.20% | 0.40% | 0.60% |
| 700 members | 0.14% | 0.29% | 0.43% |
| 1,000 members | 0.10% | 0.20% | 0.30% |
Google and Yahoo begin rejecting mail outright at 0.30% spam complaint rate. On a 500-person send, two complaints (0.40%) already cross that threshold. There is no volume buffer. Every contact matters.
This is why the ramp starts with the highest-engagement segment only, and why chronically unengaged or consent-unclear contacts are suppressed before the first send rather than after a problem emerges.
Why Opens Are Not the Metric
Intelligent Golf may report 70–80% open rates. Do not quote those figures to clubs as a planning target or a post-migration benchmark. They are not reliable.
Apple Mail Privacy Protection (MPP) pre-fetches tracking pixels automatically for any email displayed in Apple Mail. The "open" is recorded at pixel-fetch time — which happens regardless of whether a human read the email. Apple Mail accounts for roughly 49% of all email opens in the UK market. The true open rate is meaningfully lower than reported figures suggest.
Gmail retired its domain reputation dashboard on 30 September 2025. It no longer surfaces domain or IP reputation scores for third-party monitoring. Google Postmaster Tools remains the authoritative source for spam rate data and authentication pass rates — but it does not report open rates.
The correct scorecard for a migration has nothing to do with opens:
| Signal | Why it matters | Source |
|---|---|---|
| Gmail spam complaint rate | The single most actionable signal | Google Postmaster Tools |
| Hard bounce rate | Indicates list quality and data hygiene | Mailgun analytics |
| Block/deferral rates by provider | Signals throttling or rejection by a mailbox provider | Mailgun analytics |
| SPF/DKIM/DMARC pass rate | Any unexplained drop is a configuration failure | Google Postmaster / MXToolbox |
| Click rate | Real engagement, unaffected by MPP | GHL in-platform |
| Reply rate | The strongest possible positive signal | GHL in-platform |
| Unsubscribe rate | Proxy for content and frequency fit | GHL in-platform |
| Conversions (tee times, events, renewals) | The commercial reason we send | Club CRM / GHL |
Open rate can be monitored as a supplementary data point. It must never drive ramp decisions.
Shared IP Is Correct at This Scale
A dedicated sending IP is not an upgrade for a golf club. It is a liability.
A dedicated IP requires consistent high volume to maintain reputation. HighLevel's own documentation recommends dedicated IPs only for sub-accounts sending ~100,000+ emails per month. A golf club sending two emails per week to a 700-person list sends roughly 6,000 emails per month — far below the dedicated-IP floor.
On a dedicated IP at that volume, the IP cools between sends and does not maintain the reputation required for reliable inbox placement. If the club misses a week for any reason, the IP reputation degrades further. A dedicated IP also amplifies the consequences of a single bad send: on a shared pool, your complaint spike is absorbed across many senders; on a dedicated IP, it is entirely yours.
GHL's shared IP pool — where HighLevel actively manages IP reputation across many compliant senders — is the correct and optimal choice at this scale. It is not a compromise.
Shared IP is not second-best. Dedicated IP at this volume would actively harm the club's deliverability.
Myths vs. Reality
| Myth | Reality |
|---|---|
| "The list is warm, so we can send to everyone immediately." | The members' relationship with the club is warm. The subdomain's relationship with mailbox providers is not. They are separate things. |
| "Intelligent Golf gets 70–80% opens, so GHL should match that quickly." | IG's open rates are inflated by Apple MPP. Comparing the two figures is not a valid migration success test. |
| "Open rate is the main metric to optimise for." | Open rate is the least reliable metric available. Judge by spam complaints, bounces, clicks, replies, and conversions. |
| "A dedicated IP is always better for deliverability." | At under 2,000 sends/week, a dedicated IP cools between sends, amplifies complaint spikes, and harms deliverability. Shared pool is correct. |
| "GHL's built-in warm-up feature handles the warm-up." | GHL's warm-up is a volume cap only — it does not segment by engagement tier, suppress unengaged contacts, or generate any engagement signals. Manual Drip Mode segmentation is required alongside it. |
| "SMS nudges to non-openers improve deliverability." | SMS has no effect on mailbox provider reputation signals. "Non-openers" often opened on Apple Mail — texting them is likely to generate complaints, not fix them. |
| "Sending to fake seed inboxes will warm the domain." | Creating synthetic inboxes to manufacture engagement is an express path to the Spamhaus CSS blocklist. Real aged inboxes used naturally are a diagnostic tool, not a warm-up engine. |
| "Image-heavy HTML looks professional and improves engagement." | In the first 1–3 sends, image-heavy HTML triggers heightened spam-filter scrutiny and Gmail Promotions routing. Plain or lightly-branded HTML is the correct starting point. |
| "Resending to non-openers increases reach." | Non-opener data is noisy due to MPP. Resends during warm-up risk complaints from members who already read the email on Apple Mail. |
| "The new platform fixes or invalidates historical permission." | Permission follows the member, not the platform. Historical consent remains valid. Suppressions from Intelligent Golf must be imported to GHL before the first send — failing to do so is a direct PECR breach. |
| "A dedicated subdomain fully and permanently protects the root domain." | A subdomain provides reputation separation in most scenarios, not a perfect firewall. It is still mandatory — it is the most important structural protection available — but present it accurately. |
| "This is an IP warm-up." | The Mailgun shared IP pool is already warm. This is domain/subdomain reputation building. Calling it an IP warm-up is technically inaccurate and leads operators to apply the wrong mental model. |
What We Are Actually Building
The migration process achieves two things in sequence:
- Technical credibility — the new sending subdomain passes SPF, DKIM, and DMARC checks and behaves like a legitimate, authenticated sender. This is the gate, not the goal.
- Behavioural signals — real members open, click, and reply to early sends, training mailbox provider algorithms to treat future sends favourably. This is the warm-up.
Authentication must be complete before the first send. Engagement signals accumulate over the ramp. Both are required; neither substitutes for the other.
The full process — compliance audit, authentication, list segmentation, Step 0 trust priming via Intelligent Golf, the Trust Bridge send, and the engagement-gated ramp — is documented in the Operator Runbook. Volume schedules and advancement gates are in the Ramp Schedule.
Email Warm-up & Migration (Operator Guide)
The click-by-click operator guide for safely migrating a golf club's member email list onto Capture, authenticated subdomain, engagement-gated ramp, and the Prime, then Prove model. The concept and decision tree live in Email Deliverability, the Whole Process.
Step 0: Prime From the Old Platform
Why pre-announcing from Intelligent Golf is the highest-leverage action before a single GHL email is sent, and the exact copy for all three priming channels.