Businesses are complex and there are many disparate systems out there which you might have chosen to work with. You may have an e-commerce platform for your online ordering, CRM for customer management, separate accounting software, and many more. Even though systems usually deal with same resources (order, customer, product, …) each platform is completely different when it comes to storing and managing records. Platforms may use different formatting of dates, one platform can store customer’s middle name where another does not, stock on hand can be part of a product resource in one system but separate in another etc etc. To bridge the differences between these platforms and to seamlessly transfer data from one system to another you need to transform the data on the fly to a format which your platforms understand and that’s exactly why DSYNC developed the Mapping/Transformation Engine.
To understand where Mapping Engine fits, we need to look at the overall process of data transfer. At its’ core, the DSYNC process consists of three main stages:
- Get Data from Source Endpoint
- Map/Transform Data
- Send Data to Destination Endpoint
This documentation focuses solely on the second step – Mapping and Transformation of Data. It does not talk about getting data into DSYNC and sending data out to target locations.