Ready to get started?

Learn more about CData Sync or sign up for a free trial:

Learn More

Automated Continuous Sugar CRM Replication to Microsoft Access

Use CData Sync for automated, continuous, customizable Sugar CRM replication to Microsoft Access.

Always-on applications rely on automatic failover capabilities and real-time data access. CData Sync integrates live Sugar CRM data into your Microsoft Access instance, allowing you to consolidate all of your data into a single location for archiving, reporting, analytics, machine learning, artificial intelligence and more.

Configure Microsoft Access as a Replication Destination

Using CData Sync, you can replicate Sugar CRM data to Microsoft Access. To add a replication destination, navigate to the Connections tab.

  1. Click Add Connection.
  2. Select Microsoft Access as a destination.
  3. Enter the necessary connection properties. To connect to Microsoft Access, set the following:
    • Data Source: The path to the Access database. The application must have read/write permissions to the database.
    • Provider: The OLEDB Provider. For MS Office 2007 and above, use Microsoft.ACE.OLEDB.12.0.

    Windows Edition

    Connecting to Access as a destination requires the Microsoft Access Database Engine, which can be downloaded from here.

    Be sure to download the correct bitness of the driver as 64bit MS Office only works with the 64bit driver. If using 32bit MS Office, you will need to host DataSync in IIS and and enable 32-bit applications. This can be set in the "Advanced Settings" for you Application Pool. Refer to Configuration in IIS for more information on hosting DataSync in IIS.

  4. Click Test Connection to ensure that the connection is configured properly.
  5. Click Save Changes.

Configure the Sugar CRM Connection

You can configure a connection to Sugar CRM from the Connections tab. To add a connection to your Sugar CRM account, navigate to the Connections tab.

  1. Click Add Connection.
  2. Select a source (Sugar CRM).
  3. Configure the connection properties.

    The User and Password properties, under the Authentication section, must be set to valid SugarCRM user credentials. This will use the default OAuth token created to allow client logins. OAuthClientId and OAuthClientSecret are required if you do not wish to use the default OAuth token.

    You can generate a new OAuth consumer key and consumer secret in Admin -> OAuth Keys. Set the OAuthClientId to the OAuth consumer key. Set the OAuthClientSecret to the consumer secret.

    Additionally, specify the URL to the SugarCRM account.

    Note that retrieving SugarCRM metadata can be expensive. It is advised that you store the metadata locally as described in the "Caching Metadata" chapter of the help documentation.

  4. Click Connect to ensure that the connection is configured properly.
  5. Click Save Changes.

Configure Replication Queries

CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.

Replicate Entire Tables

To replicate an entire table, click Add Tables in the Tables section, choose the table(s) you wish to replicate, and click Add Selected Tables.

Customize Your Replication

You can use the Transform feature to customize your replication. The Transform feature allows you to specify which columns to replicate, rename the columns at the destination, and even perform operations on the source data before replicating. To customize your replication, click the Transform button in the Tables section and customize the replication.

Schedule Your Replication

In the Schedule section, you can schedule a job to run automatically, configuring the job to run after specified intervals ranging from once every 15 minutes to once every month.

Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your Sugar CRM data to Microsoft Access.