# Switching from Marketing Cloud or HubSpot

Moving your marketing is a project, not a signup. We do it with you: your data and consent history first, one
journey running beside your current tool, then the rest, all finished before your renewal notice is due.

[Talk to us](#talk) · [Compare costs](https://plainsend.app/calculator.md)

## Start from your renewal date

Most switches happen at renewal, so we plan backwards from it.

- **Salesforce** subscriptions renew automatically for another year unless you give notice at least **30 days**
  before the term ends. A renewal with fewer contacts or sends is re-priced without your old per-unit price, so
  shrinking slowly can cost more than leaving cleanly
  ([Salesforce MSA §11.2](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/salesforce_MSA.pdf),
  updated 2026-09-01).
- **HubSpot** renews for the same term (up to a year) and doesn't allow downgrades during a term
  ([HubSpot Customer Terms](https://legal.hubspot.com/terms-of-service), updated 2026-09-16).

| When | What happens |
|---|---|
| 9 months before renewal | First call: your edition, contacts, sends, brands, who signs, what security review needs |
| 8 months | A cost model on your numbers, three years out: stay, move to Marketing Cloud Next, or move to Plainsend |
| 7 months | Migration assessment: what maps one-to-one, what needs a rebuild, what we don't do. Security review starts |
| 6 to 3 months | A paid pilot: one brand, two or three journeys, your real consent data, success criteria agreed up front |
| Inside the pilot | A parallel run of at least three weeks (below) |
| 45 days before | Decision, with the pilot results against the criteria |
| 30 days before | You give your current vendor notice. You send it, never us |
| Renewal day | Cutover: your old platform sends nothing |

Leaving it later is possible; it just makes the pilot shorter.

## How the migration goes

1. **Suppression and consent first.** Unsubscribes, bounces and consent history move before any contact, so the
   first send can't reach someone who opted out. Plainsend's consent ledger keeps the source and time of each one.
2. **Contacts and data.** Plainsend connects to HubSpot and Salesforce directly (contacts, companies, deals, leads
   and opportunities), to Postgres and Databricks, or takes files. Every sync runs as a dry run first. Opt-outs are
   written back to HubSpot and Salesforce, so the two systems agree.
3. **Templates.** Paste or import your HTML emails: Plainsend converts them into editable templates in your brand
   kit, re-hosts the images and flags anything that won't render well.
4. **Journeys.** Each journey becomes a document in git that you can review line by line, simulate with a test
   contact, and approve. Your agent can do the first draft: HubSpot's own MCP server lets it read your workflows
   while it writes Plainsend journeys.
5. **Sending domain.** Keep your From domain and add Plainsend's DKIM records next to your current ones, or use a
   subdomain such as `mail.yourcompany.com`. A new sending setup warms up over about three weeks.

**Coming:**
**Migration tools for Marketing Cloud.** A read-only inventory of your Marketing Cloud account (journeys, data
extensions, templates, AMPscript use) and a converter from Journey Builder to Plainsend journeys. Until then we map
journeys with you by hand and with agents.

## The parallel run

Nobody should switch everything in one night. During the pilot:

- New signups and your suppression list go to Plainsend first.
- One low-risk journey (a welcome series, say) moves to Plainsend for your most engaged contacts. Your current tool
  keeps everyone else.
- We compare delivery, clicks, bounces and complaints side by side every week, and widen the move only when the
  numbers hold.
- Mailbox providers expect a new sender to build up over about three weeks, so the parallel run lasts at least that
  long. Plainsend's warm-up caps handle the daily limits for you.

## Pay once, not twice

Our offer to the first teams that switch: a fixed-price pilot, **credited against your first year**, with your
Plainsend contract starting on your current renewal date. You don't pay for two platforms for a full year.

## Run it in your own AWS

For regulated teams, the strongest answer to a security review is that the data never leaves your account.

**Coming:**
**Bring your own Amazon SES**: Plainsend sends through your SES account with a role you control, so the sending
reputation and the bill are yours. **Plainsend in your AWS account (BYOC)**: the whole platform runs in your
account, with your SES and your database. Both are being built with our first design partners. Ask us if you want to
be one.

Today, Plainsend stores data in Sydney and sends through Amazon SES in Sydney. See [security](https://plainsend.app/security.md).

## Talk to us

Tell us what you use and when it renews. We store what you send here and reply ourselves; we don't add you to a
mailing list.

*The form is on https://plainsend.app/switch. An agent can send the same thing:*

```sh
curl -X POST https://plainsend.app/lead -H 'content-type: application/json' \
  -d '{"name":"Your name","email":"you@company.com","company":"Company","platform":"marketing-cloud","renewal":"2027-06","message":"What you want to talk about"}'
```

`platform` is one of `marketing-cloud`, `mc-next`, `hubspot`, `other`, `none`. A Turnstile check may be required.