Map what you already have
List the email communications your church sends regularly: the main newsletter, volunteer updates and ministry invitations. Next to each, write where the audience is maintained and who owns it.
The aim is to make the current arrangement understandable before changing it. A new spreadsheet may help with a one-time review, but avoid making it another live contact list that someone must maintain every week.
Give each change a clear home
Decide who handles a corrected email address, a change in ministry membership and an email preference question. Tell the team where each request goes.
Keep an operational note that explains the agreed process. “Ask the office team to correct the source profile” is more useful than “Keep both systems updated.” The right process depends on the connections your church has actually configured.
Write down each sync pair
CCBChimp connects selected Church Community Builder sources to Mailchimp destinations. It does not automatically send every person in your database to Mailchimp.
For each existing connection, record:
| Item | What to write down |
|---|---|
| Purpose | Which communication this connection supports |
| Source | The specific campus, group or saved search |
| Destination | The Mailchimp audience and relevant group or tag |
| Direction | Which way this pair is configured to sync |
| Owner | Who reviews changes and errors |
| Check | When the team last verified the destination |
Use the actual configured names. Do not infer a connection from two items having similar labels.
Review overlap before adding another destination
If two ministries reach many of the same people, pause before creating another audience or another manual export. Review the existing setup and decide how those communications should be organized.
CCBChimp’s available group and tag options depend on the plan. Reverse syncing is optional, and some source types are one-way. Check the setup guide for the specific pair before assuming a change in one system will travel back to the other.
Pay attention to shared email addresses. Different CCB profiles can use the same address, while Mailchimp identifies an email address within an audience. The resulting counts may differ. Investigate the relevant profiles rather than promising that an integration will merge every duplicate correctly.
Check a small, known example
Before relying on a changed connection for a larger email, choose a small set of appropriate existing records your team is authorized to review. Confirm that the intended source and destination match, run the normal sync process, and review its result.
Allow the sync to finish. Compare a few expected records and look into errors through the normal support workflow. Do not respond to a mismatch by repeatedly importing the same list or creating additional pairs without understanding the cause.
Keep a short pre-send check
- The communication has a clear audience and owner.
- The source and destination match the documented connection.
- Sync direction and available options have been checked.
- The latest sync has completed and relevant errors have been reviewed.
- Shared-address or profile mismatches have been investigated.
- The sender verifies the intended recipients in Mailchimp before sending.
A useful contact process is one your next teammate can understand. Start with a clear map, then reduce repeat work one connection at a time.