SugarCRM is an accessible and customizable social CRM solution bridging the gap between your sales and marketing teams. Important Salesforce and marketing automation, direct lead capturing, and customer support tools are just some of the powerful features this app includes. SugarCRM will allow you to create exceptional relationships with your current and future customers. Below you'll find detailed information, specifically for SugarCRM integrations.
Supported SugarCRM integrations
Unfortunately, we do not support self-hosted SugarCRM instances - only sugarcrm, sugarondemand and sugaropencloud domains are supported!
We need your SugarCRM domain, Username and Password as well your Consumer Key and Consumer Secret. Details about the Winter 18 release can be found here.
If you already authorized SugarCRM accounts in the past or in any other PieSync integration, you'll be able to skip this step and choose from your CONNECTED ACCOUNTS.
Choose your contact type
Distinguish between Contacts or Leads before proceeding to the configuration page.
Supported Conditions/Filters [IF]
INVALID EMAIL YES/NO
OPTED IN/OUT MARKETING
PORTAL ACTIVE YES/NO
FIELDS (INCLUDING CUSTOM FIELDS)
ALREADY EXISTING IN APP YOU SYNC WITH
Supported Conditions [THEN]
UPDATING LEAD SOURCE
UPDATE FIELDS (INCLUDING CUSTOM FIELDS)
Default Field Mapping
Depending on the other app you're syncing with, you'll see a number of standard SugarCRM fields being mapped. For instance, a connection with Insightly will look something like this
PieSync syncs the default name field(s) that come with the apps. Sometimes they have a different structure in both apps you connect. E.g. first and last names are separate in app A and joint in a single field in app B. In the background, PieSync joins first and last names together from app A to B and separates them again from app B to A. Our algorithm is smart about which part it updates in app B.
Customizable Field Mapping
You can custom map your SugarCRM Custom Fields and any additional standard fields that aren't included in the default mapping yet. Bear in mind a mapping between two fields can only exist if the types of fields are compatible, and the particular compatibility will determine the direction of the mapping as well. More information on Customizable Field Mapping here.
The availability of additional sync option is app and connection dependent. If the feature box (screenshots above) is not there to tick, it's simply not possible. We need to be able to detect deletions on one side and at the same time be able to create add a segment 'PieSync Trash' or 'PieSync Unsubscribes' on the other side.
Thanks to the feedback we have already received, we created a list of popular apps that we’re going to work on very soon. By voting them up in our pipeline, YOU decide which connectors we’ll release first. If you don’t see your app on the list or need any further help, drop us a line - email@example.com. Don't forget to read our blog for the latest in productivity, apps, and technology!