by SugarCRM

Real-time, bi-directional synchronization of Marketo data with Sugar Leads and Contacts. Features automatic Lead conversion based on Marketo score; configuration through Sugar's Cloud Connector and support for custom fields. Purchase includes one year of full connector support including all bug fixes and new updates.

Release Notes (for Sugar 6.x customers)

Marketo For SugarCRM 2.1.19

March 4, 2015 Jeff Bickart jeff.bickart@ticomix.com

  • Added additional Marketo Activity Types that can be excluded from downloading to the Activity Logs
  • Corrected an issue where the excluded Activity Types are incorrectly downloaded to Sugar via Scheduler

Marketo For SugarCRM 2.1.12

September 12, 2014 Jeff Bickart jeff.bickart@ticomix.com

  • Removed the delete field from the leads_cstm and contacts_cstm tables so that you can import leads and contacts correctly.

Marketo For SugarCRM 2.1.8

May 12, 2014 Jeff Bickart jeff@neposystems.com

  • Correct issue where Opportunity Date Entered is not properly saving to Marketo.

Marketo For SugarCRM 2.1.4

Mar 25, 2014 Jeff Bickart jeff@neposystems.com

  • When downloading new Leads from Marketo, only process records that posses an email address

Marketo For SugarCRM 2.1.2

Mar 10, 2014 Jeff Bickart jeff@neposystems.com

  • When an update occurs to the email address all existing email address are set to be non-primary addresses

Marketo For SugarCRM 2.1.1

Jan 29, 2014 Jeff Bickart jeff@neposystems.com

  • Correct the details of the Activity Type "Change Status in Progression" to display the same as it does in Marketo

Marketo For SugarCRM 2.1.0

Jan 20, 2014 Jeff Bickart jeff@neposystems.com

  • Corrected the relationships between Leads and Activity Logs and Contacts and Activity Logs so that you can properly report on the relationships.

  • When leads are downloaded from Marketo and matched by Email Address to Contacts or Leads in SugarCRM. Blank fields that are retrieved from Marketo will not overwrite data already in SugarCRM. Instead, SugarCRM will update Marketo with the data values from SugarCRM.

  • Saving SugarCRM Contacts and Leads has been refactored to improve the user experience.

    • Updates to marketo are no longer applied immediately but instead queued. Marketo will be updated on the next Scheduler run. This has been down to improve the user experience and eliminate any waiting for Marketo updates to be applied.
    • When individually saving Contacts or Leads, only the changed fields in SugarCRM will be updated in Marketo. This functionality has not changed. This is just being highlighted to describe the difference with mass updating records.
    • Saving Contacts/Leads using "Mass Update" will send all SugarCRM mapped fields from SugarCRM to Marketo regardless of data changing in SugarCRM.
    • This facility can be used to send all sets of Contacts or Leads to Marketo to seed Marketo or to update Marketo with all of the values from SugarCRM.

Marketo For SugarCRM 2.0.17

Dec 10, 2013 Jeff Bickart jeff@neposystems.com

  • Corrected the manifest.php to correctly install the marketo_sync table

Marketo For SugarCRM 2.0.16

June 12, 2013 Jeff Bickart jeff@neposystems.com

  • When using the SugarCRM WorkFlow engine with ActivityLogs, the Workflow is triggered more than once for each ActivityLog. We have refactored the creation of ActivityLogs sothat the workflow engine only gets triggered once.

Marketo For SugarCRM 2.0.15

June 4, 2013 Jeff Bickart jeff@neposystems.com

  • When you merge Leads or Contacts the ActivityLogs were attempting to be copied from one record to another. This should not occur. Upon merging the ActivityLogs are removed from SugarCRM for the records that are getting deleted.

Marketo For SugarCRM 2.0.14

May 29, 2013 Jeff Bickart jeff@neposystems.com

  • When the connector settings indicted that the connector is disabled, when you went to the detailview of a connected Lead or Contact. Updates were still downloaded from Marketo. This issue has been resolved.

Marketo For SugarCRM 2.0.13

May 13, 2013 Jeff Bickart jeff@neposystems.com

  • WebHooks return a full set of information about the SugarCRM record. This can be used to enrich data from SugarCRM.
  • It is now possible to fast-forward the Activity Log Scheduler so that you do not need to obtain the full set of history from the beginning of time.

Marketo For SugarCRM 2.0.12

May 9, 2013 Jeff Bickart jeff@neposystems.com

  • Bug Fixes

Marketo For SugarCRM 2.0.11

May 03, 2013 Jeff Bickart jeff@neposystems.com

  • Bug Fixes

Marketo For SugarCRM 2.0.10

April 30, 2013 Jeff Bickart jeff@neposystems.com

  • Corrected a bug where Opportunities were not properly updating in Marketo
  • The Sync to Marketo Checkbox on Opportunities can now be properly checked

Marketo For SugarCRM 2.0.9

April 24, 2013 Jeff Bickart jeff@neposystems.com

  • Corrected a bug where a Datetime information from SugarCRM is not being sent to Marketo correctly

Marketo For SugarCRM 2.0.8

April 23, 2013 Jeff Bickart jeff@neposystems.com

  • Corrected a bug where a Marketo DateTime is mapped to a SugarCRM datetimecombo

Marketo For SugarCRM 2.0.7

April 23, 2013 Jeff Bickart jeff@neposystems.com

  • Refactored Opportunity sync so that Marketo for SugarCRM works with SugarCRM 6.7.0
  • Enabled the ability to update the Marketo Lead Score from within SugarCRM.
    • This allows the use of SugarLogic to calculate a value in SugarCRM and then update Marketo
  • WebHooks... SugarCRM can now consume Marketo Webhooks. Documentation will available shortly.
  • Bug Fixes

Marketo For SugarCRM 2.0.6

March 12, 2013 Jeff Bickart jeff@neposystems.com

  • Corrected the output of error messages that appear in the SugarCRM Log

Marketo For SugarCRM 2.0.5

March 6, 2013 Jeff Bickart jeff@neposystems.com

  • Corrected issue with the Marketo Lead Synchronization Scheduler not correctly updating it's scheduler status
  • Added new configuration settings:
    • Only add SugarCRM Leads when the Marketo Lead has met a minimum score requirement
    • It is now possible to tell the Marketo Lead Synchronization Scheduler how many leads to download at a time from Marketo. This is important for memory constrained environments such as Sugar OnDemand.

Marketo For SugarCRM 2.0.4

February 20, 2013 Jeff Bickart jeff@neposystems.com

  • The update to the unsubscribe email didn't take into an account that opportunities uses the same functionality. Opportunities don't have email addresses. This issue has been resolved.

Marketo For SugarCRM 2.0.3

February 14, 2013 Jeff Bickart jeff@neposystems.com

  • The unsubscribe feature had stopped functioning as it was pulled down from Marketo. This has been resolved.

Marketo For SugarCRM 2.0.2

February 6, 2013 Jeff Bickart jeff@neposystems.com

  • Added new configuration setting to set the maximum number of records that can be downloaded from Marketo. This was done do to errors with the scheduler running for too long.

Marketo For SugarCRM 2.0.1

January 2013 Jeff Bickart jeff@neposystems.com

  • Correct issue with writing the labels when downloading custom fields

Marketo For SugarCRM 2.0.0

January 2013 Jeff Bickart jeff@neposystems.com

  • Added Opportunity Syncing
  • For the commercial version of SugarCRM, logic_hooks have been replaced with workflows
  • Added ability to turn off Marketo as a configuration setting

Marketo For SugarCRM 1.2.2

August 6, 2012 Jeff Bickart jeff@neposystems.com

  • Correction of error condition upon import of Leads into SugarCRM.

Marketo For SugarCRM 1.2.1

Oct 1, 2012 Jeff Bickart jeff@neposystems.com

  • Version 1.2.1 introduced a bug where the FirstName and LastName were not properly being synced when they where changed in either a Lead or a Contact. This has been resolved in this release

Marketo For SugarCRM 1.2.0

August 2, 2012 Jeff Bickart jeff@neposystems.com

  • Requires SugarCRM 6.3.0: This version has the extension framework for Schedulers
  • Updated the "Download Activity Logs upon initial sync?" functionality to enable a Scheduler that will download all ActivityLogs. The issue was that ActivityLogs can get updated without effecting the actual lead. For example: Visit Web Page does not actually change the Lead but does store an ActivityLog
  • Added Scheduler and new module to maintain the StreamPosition to keep track of when the last synchronization took place. The new module NEPO_StreamPosition can be accessed in the Marketo section of Admin.

Marketo For SugarCRM 1.1.13

July 3, 2012 Jeff Bickart jeff@neposystems.com

  • Added the ability to save SugarCRM WebToLeadCapture Forms directly from the Web to Marketo
  • Removed Marketo from the Admin->Connectors->Manage Connector Search panel
  • If the company attempting to use Marketo has SugarCRM prior to 6.5 they also need to install the MarketoPre65.zip Module

Marketo For SugarCRM 1.1.12

June 26, 2012 Jeff Bickart jeff@neposystems.com

  • Works for Both SugarOnDemand and Others
  • Can be installed in CE through ULT

Added * Keep In Sync for the Unsubscribed Field from Marketo and the SugarCRM Email Opt-Out Field

Updated * Updated to work SugarCRM 6.5 * replaced the function file_exists with get_custom_file_if_exists. The function get_custom_file_if_exists only exists in SugarCRM 6.5 or greater * Correct a bug that dealt with the how Email addresses are saved the 1st time a Lead is created * Updated the SugarCRM to Marketo synchronization: * Only send to Marketo changed information from SugarCRM * If no information has changed in the SugarBean, then do not send a synchronization packet to Marketo * The Marketo Synchronization Information is now a Menu Item under the Activity Log Tab * Reports properly display Activity Log instead of LBL_ACTIVITY_LOG for both Contacts and Leads * We have submitted to SugarCRM a function to properly save the Connector language definitions inside of Sugar OnDemand instances, the code is in place to take advantage of this new function when it is available.

Installer: * Updated the pre_install.php and post_install.php to work correctly with SugarCRM 6.5 due to a change in the GridLayoutManager * The pre_install.php now checks for the installation of Soap, hash_hmac, and get_custom_file_if_exists if any of these do not exist, we prevent the user from moving forward with the installation

Saving Comment Saving Comment...