Integrating data on Slyncy (or in fact on any data integration platform) needs some careful consideration. When more than one of your systems already contains data, here is a checklist of things to consider:

Tax Codes

Matching is done on the tax code identifier. Each system’s tax codes should be aligned before attempting an integration.

When you finalise your integration with Slyncy, you can contact us to discuss tax code alignment if necessary. If the source system has more tax codes than the destination system, then new tax codes may need to be created in the destination system. If the sync is two-way, then both systems may need new tax codes.

If any tax codes are not matched up and they are used, then the sync process will not have a tax code to translate to.

Financial Accounts

Matching is done on ledger codes. Each system’s ledger codes should be aligned before attempting an integration.

When you finalise your integration with Slyncy, we will discuss financial accounts alignment if necessary. Financial accounts mapping is similar to tax code mapping.

Parties

Most connectors allow you to do email based matching for contacts. However, since emails are not always unique and are not always filled in, this is not a recommended way of working.

If more than one of your systems already contains Party data, a manual integration process may need to be done.

Note that it is not always a good idea to leave the matching option turned on. Matching data from untrusted systems can result in ‘data spiking’. An eCommerce system which may not enforce strict identity checking rules may introduce a contact; – however, a hacker could also introduce invalid data, which may get matched to one of your important contacts and update your valid data.

Inventory Items

Inventory items are matched on catalogueItemIdentification. The inventory item of each system should be aligned before attempting an integration.

Transactions

No matching is done on transactions. You should set the financial start date of the end point to match the first date of the data you would like to start bringing across.

Payments

No matching is done on payments. You should set the financial start date of the end point to match the first date of the data you would like to start bringing across. If any payments are created whose transactions are not transferred yet (for example, due to a financial start date cut-off), then the payment transfer will fail and you will be notified.

Manual Integration

In cases where the migration cannot be done by you, you can contact Slyncy support (support@slyncy.com) to arrange a quote to integrate your data.

Browser not supported