

How it Works¶

Migrate all records from BFUS to Lime CRM¶

To get Lime CRM synchronized with BFUS a migration of all data has to be done. The migration is built for the two cases described below.

You have an empty Lime CRM application and you want to fill it with customers from BFUS.
There are already companies in Lime CRM. They have the correct customer number (or other key) according to BFUS, and you want to overwrite their information with data from BFUS.

It is possible to limit the migration in different ways. For example to only migrate customers with an active contract.

Update or create a customer in Lime CRM and send it to BFUS¶

This is an add-on of it's own, which complements the integration. It makes it possible to send customer updates to BFUS.

Synchronize all changes from BFUS for the configured objects¶

Changes made in BFUS triggers a message to be send to a custom endpoint in Lime CRM. The messages are put on a queue in BFUS and are sent one at a time to Lime CRM. If Lime CRM are not available the messages will remain in the queue. When received in Lime CRM the correspondig object will be updated.

Logging¶

All message sent from BFUS to Lime CRM are stored in a log table. Processed- or Failedmessage depending on if it was successful or not.

Jump to BFU/MFU¶

From an object in Lime CRM it is possible to jump to the corresponding object in BFUS. In the actionpad of the current object their is a link which will take you to the corresponding object in BFU/MFU. Technically it works the same one as a bookmark in BFUS, we create a bookmark and opens it.

Removal from Lime through BFUS integration¶

If an object is deleted in BFUS a message with the operation type "deleted" that tells Lime to “delete” a specific object is sent. Considering that Lime rarely deletes objects from the database, the integration follows this practice and therefore only change the status of the concerned object. This is most often done through changing an option list status to Deleted or set a Yes/No-field indicating that the objected is “deleted”. For more information about anonymization see the GDPR section.