Mailchimp Queue Items are internal records that Mailchimp for Salesforce creates when someone edits a Salesforce record that has mapped fields or email address changes relevant to Mailchimp. Rather than sending each individual edit to Mailchimp the moment it happens, the app stores these changes as Queue Item records and processes them asynchronously in small batches. This means your edits, like updating a mapped field value, changing an email address, or adjusting a subscription preference, are collected and then sent to Mailchimp in the background without slowing down your day-to-day work in Salesforce.

Queue Items are short-lived. Once the batch job picks them up and processes the change, the record has done its job and is no longer needed. If you see them in your recycle bin, that's completely normal.

A Note for Developers and Admins Familiar with Apex

The reason Queue Items exist comes down to a Salesforce platform constraint: sending data to an external service like Mailchimp requires an HTTP callout, and callouts cannot be made synchronously from certain contexts (like triggers). The standard practice in Salesforce is to hand off this kind of work to an asynchronous batch job, which runs in its own execution context where callouts are allowed.

These batch jobs don't always run instantly. Salesforce places asynchronous Apex jobs into a Flex Queue, which controls the order and timing of when they execute based on available platform resources. It's worth knowing that the Flex Queue is shared, so other installed apps and custom Apex in your org also compete for the same queue slots. If you notice Queue Items sitting for longer than expected, it may be because the Flex Queue is busy.

For more on how Salesforce manages asynchronous job execution, see Salesforce's documentation on the Apex Flex Queue and Monitoring the Apex Flex Queue.

Your Mailchimp for Salesforce subscription is linked to your current Salesforce org. When you need to move to a new org, whether due to a company merger, system consolidation, or org restructuring, you'll need to reinstall the integration and reconfigure your settings to ensure data continues syncing properly.

The Solution

Moving to a new Salesforce org requires reinstalling our app and reconnecting to Mailchimp. Here's what you need to know:

Install the app in your new Salesforce org and complete the standard setup process. This creates a new license and starts a 14-day free trial of our premium features. The setup process will also update your Contact, Lead, and Person Account page layouts in the new Salesforce org.

We recommend using the time within the 14-day free trial to ensure you're ready to cancel the license in your old Salesforce org. After you connect our app to your new Salesforce org, Mailchimp data will flow into Salesforce just like before. This includes audiences, audience members, tags, groups, and campaign tracking statistics.

You'll need to reconfigure these settings in the new org:

Audience Configuration and Field Mappings - Mailchimp uses audience-to-Salesforce object mappings. You must recreate your primary audience selection, field mappings to Salesforce, tag mapping rules, and double opt-in configuration if you were using it. These settings control how data syncs between systems.

Sync Settings - Recreate your Salesforce to Mailchimp mapping rules, Mailchimp to Salesforce member sync settings, batch job frequency and filtering, and error handling preferences.

Query Builder or Segment Sync - If you were using Query Builder to push Salesforce segments to Mailchimp, recreate those saved queries in the new org.

Data Wizard - Recreate any Import Wizard schedules you had configured for bulk data imports.

Process Builder and Flow Automations - Any automations relying on Mailchimp for Salesforce objects need to be recreated in the new org.

Apex Triggers or Customisations - If you have custom code referencing Mailchimp for Salesforce fields or objects, redeploy that code in the new org.

Once you're confident that your new Salesforce org is working correctly, purchase a new license and contact us to cancel the old license.

Important notes about your Mailchimp account: If you're not changing your Mailchimp subscription, there's no need to worry about moving templates, campaigns, or other Mailchimp-only assets. These continue to be stored in Mailchimp, separately from Salesforce. When you connect the new Salesforce org to Mailchimp, it will show all your Mailchimp data in that new Salesforce instance.

Related Articles

Why Doesn't Mailchimp for Salesforce Appear as a Connected App?

Our Mailchimp for Salesforce package operates natively in your org by making outbound, authenticated HTTPS callouts from Salesforce to Mailchimp. This architectural approach makes it much more secure than traditional middleware integrations.

What This Means

Because our integration runs natively and only makes outbound calls, it will not register as a Salesforce Connected App to access Salesforce data. As a result, it won't appear on the Connected Apps OAuth Usage page in your Salesforce org.

Do I Need to Take Action?

No action required. You don't need to worry about Salesforce's "Trusted Connected Apps" policy changes, as these restrictions aren't applicable to our integration.

Salesforce Connected Apps Policy (September 2025)

In September 2025, Salesforce announced a significant change to Connected Apps: restricting the use of uninstalled connected apps. You may have received an email requiring you to review your connected accounts and those of apps and integrations.

Why Mailchimp for Salesforce Is Not Affected

Mailchimp for Salesforce does not use Salesforce Connected Apps, so no action is required for our integration. Here's why:

Native Operation: Our integration runs entirely within your Salesforce org
Outbound Authentication: We make authenticated callouts from Salesforce to Mailchimp
No Inbound Access: We don't require external apps to access your Salesforce data

Connected Apps are most often required for inbound integrations (like middleware tools such as Zapier or Cazoomi) that need to access Salesforce data from external systems.

Our Security Architecture

Our native approach provides several security advantages:

✅ No third-party data access - Data never leaves your Salesforce org except through controlled, authenticated API calls
✅ No OAuth tokens to manage - No external authentication credentials that could be compromised
✅ Full Salesforce security model - Leverages your existing field-level security, profiles, and permission sets
✅ Transparent operation - All code runs within your org where you have full visibility

Learn more about Mailchimp for Salesforce's evolved security approach.

Quick Reference

Question	Answer
Will Mailchimp for Salesforce appear in Connected Apps?	No - it operates natively, not as a Connected App
Do I need to whitelist it as a "Trusted Connected App"?	No - this policy doesn't apply to our integration
Is this less secure than using a Connected App?	No - native operation is actually MORE secure
Do I need to take action after Salesforce's Sept 2025 policy change?	No action required for Mailchimp for Salesforce

Connecting Multiple Mailchimp Accounts to One Salesforce Org

Yes, you can connect more than one Mailchimp account to the same Salesforce org. On our settings page, you'll find a Connected Accounts table, which allows you to add and manage multiple Mailchimp accounts. Once connected, each of those accounts will be automatically synced with Salesforce.

Licensing & Pricing

There's no additional license required to connect multiple accounts. However, our pricing is tier-based and depends on the number of active subscribers synced from each connected Mailchimp account.

An active subscriber is any email address with an active status on a Mailchimp audience — unsubscribed, deleted, or cleaned addresses do not count. Our billing engine automatically calculates which tier you fall into based on your total active subscribers across all connected accounts. This tiered approach ensures you only pay for the level of usage you actually need.

Connecting Multiple Salesforce Orgs to Mailchimp

Yes, you can connect more than one Salesforce org to Mailchimp.

Production Orgs

If you maintain more than one production org, a separate paid license is required for each org. Each production environment needs its own subscription.

Sandbox Orgs

If you have a production installation and an active license, you're entitled to install the package in your Salesforce sandboxes at no additional cost. However, there are important considerations:

Sandboxes are typically used for development or testing
Connecting a sandbox to a live Mailchimp account should be done with caution to avoid inadvertently impacting live customer data
Best practice: Link your sandbox environment to a free Mailchimp account for testing purposes

This provides a safe and controlled setup for evaluation and development without any risk to your production data.

Quick Reference

Scenario	License Required?	Best Practice
Multiple Mailchimp accounts → One Salesforce org	No (included)	Monitor total subscriber count for pricing tier
One Mailchimp account → Multiple production orgs	Yes (each org)	Separate license per production org
One Mailchimp account → Production + Sandbox(es)	No (sandboxes free)	Use free Mailchimp account for sandbox testing

Your connection. Your settings.

In this article

Next Steps

FAQs

Field Mappings

Partners

Legal

Product

Resources

How can we help?

Your connection. Your settings.

In this article

Next Steps

FAQs

What are Mailchimp Queue Items?

How do I move to a new Salesforce Org?

Can I create my own reports?

How do I change admin users in Mailchimp for Salesforce?

Why doesn't Mailchimp for Salesforce appear as a Connected App?

Can I connect multiple Mailchimp accounts and Salesforce orgs?

What does a remote site error mean when connecting a Mailchimp account?

What happens if a I delete a Salesforce Contact or Lead?

What happens when I disconnect a Mailchimp Account?

What are the Mailchimp Queue Items in my recycle bin?

How does migration work?

How do I change the Salesforce Sync User?

Do you support ICU Locale formats?

Why does the error Storage Limit Exceeded mean when connecting my Mailchimp Account?

Why can't I see sync settings?

How Beaufort 12 Apex Jobs Run Without Impacting Your Salesforce Org Performance

What time zone is my Mailchimp data in?

How do I connect Salesforce to Mailchimp

How do I reconnect a Mailchimp account?

What is GDPR and how does it affect the integration?

What happens when the application expires or is suspended?

What happens when I delete a campaign in Mailchimp?

Is my data safe?

Understanding How Managed Packages Operate in Your Salesforce Org

Do I have to sync archived members to Salesforce?

Can I connect more than one Mailchimp account?

How do assignment rules work?

What does the advanced section do?

What reports can I run on my data in Salesforce?

Can I use Salesforce Integration User?

How can I manually add Mailchimp to my page layouts

Field Mappings

Partners

Legal

Product

Resources