> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/guides/marketing/email-deliverability/switching-email-platforms-without-hurting-deliverability.md).

# Switching Email Platforms Without Hurting Deliverability

Switching email platforms can temporarily impact your deliverability. This is normal and expected.

### **Why Deliverability Drops**

When you switch platforms:

* Your sender reputation resets
* You may be using a new sending IP
* Email providers no longer recognize your sending behavior

### **Impact on Your Contacts**

You may see:

* Lower open rates
* Emails landing in spam
* Reduced engagement

### **How to Prevent Issues**

#### **1. Clean Your List**

Remove:

* Inactive contacts
* Invalid emails
* Spam traps

#### **2. Start with Engaged Contacts**

Send to people who already recognize and interact with you.

#### **3. Warm Up Gradually**

Increase your sending volume slowly over time.

#### **4. Reintroduce Yourself**

Send a simple email like:“You’ll be hearing from me here moving forward.”

#### **5. Monitor Performance**

Watch:

* Open rates
* Click rates
* Spam complaints


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rechat.com/guides/marketing/email-deliverability/switching-email-platforms-without-hurting-deliverability.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.