by Fanatical Labs

Save Your Team Countless Hours. SugarChimp syncs your lists in both directions so you can work in your preferred app. Segment and group your Mailchimp subscribers based on Sugar data so you can market to the right people at the right time. Compatible with all versions and editions of Sugar and SuiteCRM.

Free Trial

By clicking you consent to share your profile with the developer

#3060 - New field added in MailChimp list does not sync to field mapping in Sugar

Closed Bug? created by David E Kromann Verified Purchase 5 years ago


I have a problem today.

I have on existing mailchimp list which is already syncronized with Sugar added a new field (text), but this field never appears in Sugar in the section 'Field Mapping' so that I can get some content.

How can this be?

I have tried to:

wait update the SugarChimp add-in to latest

no luck.

Thanks for any advise you can give.

Best Regards


  1. fanaticallabs member avatar

    Fanatical Labs Provider Affiliate

    5 years ago

    Hello Lone,

    I'm sorry for the trouble. That process is pretty simple and not something that typically has issues. We'll need to get on a call in order to troubleshoot why that field is not getting into the crm. Can you schedule a time for us to look at it here:

    Thanks for your patience, we'll figure out what's going on and get that field syncing.


  2. fanaticallabs member avatar

    Fanatical Labs Provider Affiliate

    5 years ago

    We were able to clear your sync queue, and find the new field on the field mapping page on a call. I believe the issue arose from changing an old merge tag away from the default 'MMERGE16' after syncing it to Sugar. Then, when adding the new field, it took the merge tag 'MMERGE16' along with the corresponding field mapping.

    This is not intended and something we will look to find a solution on our end. However, it is preventable if you can always relabel your merge tags accordingly before syncing to SugarCRM.

    Thanks for reaching out, and let us know if you have any more questions moving forward! Jon

This case is public. Please leave out any sensitive information such as URLs, passwords, etc.
Saving Comment Saving Comment...