How to forward emails so that forwarded emails do not have “FWD:” in their subject and metadata is preserved

NOTE: If you’re looking to install the Multi Email Forward Chrome extension, please read Getting Started with Multi Email Forward.

Table of Contents

  1. Introduction
  2. Important notes about email metadata
  3. Example use cases
    1. Forward old emails to HubSpot
    2. Forward emails to Clio Maildrop

Introduction

This support note explains how to use cloudHQ Multi Email Forward to forward multiple emails as separate messages while preserving the subject line and metadata. Because the metadata is preserved, you can forward emails to your CRM (Salesforce, Zendesk, etc.).

The emails will look the same in the target inbox as they do in your inbox. They will not have “FWD:” in the subject line. To, Cc, Bcc, and other metadata will be preserved.

Important notes about email metadata:

  1. The original FROM header is not preserved. The original FROM value is saved in RESENT-FROM. The FROM header will show the original sender’s name, but the email address will be your address (the address of the account doing the forwarding). Salesforce and other major CRMs support this, so emails attach to the correct records.
  2. The received date is not preserved.
  3. The DATE header is preserved.
  4. The REPLY-TO header is preserved.
  5. The CC, TO, and BCC headers are preserved.
If you enable “preserve metadata,” we will add fake headers. The emails are NOT Bcc’d or Cc’d. They are normal sent emails with fake headers.

Example use cases

Forward old emails to HubSpot

For detailed instructions on how to forward emails to HubSpot, see this support note: How to use Multi Email Forward to log old emails to HubSpot