Sugar Integrations with Bedrock Data

by Paul Scondac on August 30, 2016

Bedrock Data is a data management platform that lets businesses synchronize and manage their data, fast and easy.

The Bedrock Sugar integration lets you bi-directionally sync lead, contact, account and opportunity data from Sugar to other systems you are integrating with. It will also automate the creation and updating of leads and contacts in the Sugar system, and it’s compatible with all Sugar versions.

In this blog post, we will show you how to setup the Sugar connector, and look at other useful Sugar integrations inside of Bedrock.

Getting Started with Sugar in Bedrock

From the Bedrock Data main screen, go to Connectors, and select Sugar CRM. Enter your Sugar CRM admin user account name, password, and API URL (instructions on how to generate an API URL can be found here).

What Sugar Data Can Be Synced?

What Objects and Actions Are Supported?

ObjectBedrock Object NamePermissionsCustom Field SupportRelationships*Required Fields**
UserOwnerReadYes--- 
Contact/Lead

Contact

Read/
Update/
Create (Lead Only)
YesUser
Company
Opportunity
First Name
Last Name
Email
CompanyCompanyRead/
Update/
Create
YesPerson
Opportunity
User
Company
Name
OpportunityOpportunityRead/UpdateYesUser
Contact
Company
Name
Expected
Close
NoteActivity

Read/
Update/
Create

NoUser
Contact/Lead
Title
Date Created

* Relationships can be used to map fields from related Objects. Learn more about how to map fields from related Objects.

* Where a 1-to-Many relationship exists between related objects, we do not recommend mapping fields. Learn more here.

** Required fields must be mapped in Bedrock for records to sync as expected. Learn more about how to best manage required fields here.

Important Functionality Notes

ObjectImportant Notes
Opportunity
  • Must have close dated ASSIGNED in order for the Deal to be paired up with another opportunity-type record in another system.
Contact
  • Bedrock can only create contact type records as leads.
Activity
  • In most Sugar CRM system's there is a required field for Display In Portal? This field needs to be mapped with a single line mapping and a default value of 1 to allow activities to sync, as seen below.

Auto-Generate Your Mappings

The most common objects that you'll be mapping in Bedrock are the contact-type objects. Bedrock also works with many other object types such as opportunity (deals) and company. 

The easiest way to know if an object will be available to map in a given integration you have setup is to use the Auto-Generate Mappings functionality in the Mappings section of your Bedrock portal.

The steps for mapping all of the available objects is the following: 

  1. Go to the Mappings home screen
  2. Click on Auto-Generate Mappings

That’s it! You will automatically see mappings for all of the available objects between the connected systems. As noted above, the majority of the systems will only have a Contact Mapping. However, through the Contact Mapping, you will likely be able to access data on related objects (Company, Opportunity, etc.).

After you’ve auto-generated your mappings, the next step is to go into each mapping and review the fields that were automatically mapped. Make sure they are fields you want to keep, delete or perhaps add additional fields to the mapping.

What are Other Useful Sugar Integrations?

    Sugar - Eventbrite

Sync with Attendees, Events and Order Objects

    Sugar - Cvent

Sync with Event, Registration and Contact Objects

    Sugar - Shopify

Sync with Customers and Order Objects

    Sugar - Salesforce

Sync with Accounts, Contacts, Opportunities, Cases, Tasks, Leads and User Objects

Give Bedrock Data a try and let us know what you think. To learn more visit www.bedrockdata.com

Find similar articles in these categories:

PRODUCT: SugarCRM

AUDIENCES: Administrators End Users

Paul Scondac
Marketing Manager at UpCurve Cloud
More From This Author »