The friction we found with Mageplaza's integration for Magento Salesforce is twofold, concerning the quality and organization of data as it is synchronized.
Data synchronization and system integration is not just about having reliable information; it's also important how you are empowered to use it. The friction we found with Mageplaza's integration for Magento Salesforce is twofold, concerning the quality and organization of data as it is synchronized. We'll unpack that in context below.
Custom conditional synchronization rules limit data transfer based on configured exclusions. For example, with conditional sync a user can limit order synchronization to orders greater than $500. This presents a unique data integrity issue. That's because when data is mirrored between systems, it is always a best practice to have the data flow through first and then configure it for your specific business needs. Filtering prior to synchronization compromises data integrity, by design.
Definitely a "don't."
As we got into it, our dev team offered a technical perspective by reviewing the demo experience. Soon, you'll be able to find the companion article on our blog about this, but to keep it high level, here's the TL;DR Quick and Dirty rundown of the defects that they found.
Uses app API to sync, no Bulk API
This means that you'll hit limits resulting in slow sync time and potentially timeout errors. Also, if Salesforce goes down (like it did last week), there is no queue to "retry" the sync. Instead, you'll need to manually configure and queue.
Many of the field mappings leave critical decisions (that should be based on best practices) to the end-user — a precarious endeavor for any technician that is supporting an eCommerce client. We solve for this systematically with built-in logic.
Reporting sync errors
The plugin says records failed to sync but not why, so you have to find the record, then try to troubleshoot what the problem could be.
No deduplication logic (pertains to the item above) for data integrity
The user can add multiple Magento fields to one Salesforce field, but there aren't separators to parse data.
Since Magento fields can be sent to Salesforce with "many-to-one" relationships (multiple fields synced into one field; e.g. City, State), bidirectional sync will never be possible. Therefore, know that you're going in with an unnecessary constraint.
Missing logic adequately linking "Opportunities" to "Accounts/Contacts."
(e.g customer returns to retrieve an "abandoned cart.")
When the order is placed, the order is mapped over. There is no logic to connect this order to the existing Salesforce Opportunity instead of creating a new record. This issue must be manually reconciled.
Our final word is one of caution when it comes to set-up. As we were looking through the reviews on Mageplaza's sales page, one user noted the barrage of set-up instructions that was completely overwhelming. If you aren't a developer, this may be darn near impossible to implement, especially without clear support options.