Current State:
The Classic system currently integrates with Salesforce using a custom integration stack called Plum Sync. This job runs every five minutes, extracting Account and Contact details from Classic and syncing them with Salesforce. However, Plum Sync lacks validation and duplicate checks, resulting in significant data duplication. As a consequence, 80% of duplicate accounts in Salesforce originate from Plum Sync.
Future State Proposal:
To address these issues, we propose introducing an enterprise integration platform to redesign and architect the sync process, ultimately retiring Plum Sync. The enhanced Salesforce sync will follow a two-step approach:
Validate records against business rules, including duplicate checks.
Execute an UPSERT API call to insert or update records in Salesforce.
What is the problem?
The Classic system currently integrates with Salesforce using a custom integration stack called Plum Sync. This job runs every five minutes, extracting Account and Contact details from Classic and syncing them with Salesforce. However, Plum Sync lacks validation and duplicate checks, resulting in significant data duplication. As a consequence, 80% of duplicate accounts in Salesforce originate from Plum Sync. |