The easiest way to replicate our Dynamics 365 CRM data on premise

We use Tibco Scribe to bring the data from our Dynamics 365 CRM Cloud environment to our on-premise data warehouse. We use this data in our BI environment, where our business users use it to create dashboards and reports. The sync is done on a daily basis using a manually selected set of Dynamics 365 CRM entities.

We started using Tibco Scribe when we moved to Microsoft Dynamcis 365 CRM, we previously had no need for such a tool. But we found it extremely easy to use and setup synchronization jobs. It was a no-brainer to create and maintain the jobs and schedules to keep our on premise database in sync the our CRM production environment.

Our reporting is dependent on the correct synchronization of the Microsoft Dynamics 365 data to our on premise database.
We learned that sometimes Tibco Scribe is not up to date when it comes to changes in the REST api or changes Microsoft implements on the database, which caused the synchronization to fail. And it is not always easy to figure out what is the exact cause of the failure.
But Tibco Support was of great help in those cases.

The integrator we worked with proposed this tool to fulfill a need we had on getting the data from our Dynamics 365 CRM environment on premisse for our reporting needs.What I like the most about the product is that it mitigates the need for us to develop the logic to do updates or inserts of data. We have an ETL tool in house, but it would cost us quite some time and money to develop and maintain the stuff that Tibco's product does out of the box.

The market and the needs change over time, we might focus a little more on user friendlyness of the product. Some things take quite some time specially if one wants to make a selection of which fields someone wants to synchronize from a very large table for instance.
And the relationship the supplier has with the products it connects to, will also have a bigger role. This last aspect to prevent there arise problems with synchs because of changes on the source application (in our case MS Dynamics 365 CRM)

We use the cloud solution of Tibco scribe to synchronize our Microsoft Dynamics 365 environment to our on premise Microsoft SQL server for business reporting purposes. The only on premise component we had to install was the agent on the Microsoft SQL server machine that is the destination of the synchronization jobs we created. It's zero effort once it is installed, it updates itself when a new version is released.

We don't have any further integrations with Tibco Cloud integration (Scribe). We purely use it to have a local copy of ourt Dynamics Customer Relationship Management tool which also runs in the Cloud. The copy of the data is stored in our Microsoft SQL server and consumed using our reporting tool (Qlik Sense).

We recently used it, with help of our current Microsoft Dynamics 365 partner, to migrate data from the Salesforce environment from one of our subsidiaries. Our partner took care of the complete setup and execution of the job. But the end result was what we expected and the leadtime from analyzing to final migration was short (a little more than a month).

Tibco Scribe is a very user-friendly solution to integrate and replicate your cloud data. Both for cloud-to-cloud as for cloud-to-on premise integrations or replication. It's extremely easy to setup and configure, and it can be managed by users with very little IT skills.
But also be prepared to accept that it not always is up to date when it comes to API or database model of the source application and that it can take some time to resolve that kind of issues.

I have not used the community that often to find resolutions for my problem, but they often pointed me in the right direction to formulate the problem in the right wording to pass on a ticket to Tibco Support.
So to be honest I've got very little experience with the Tibco Community, on the other hand we haven't had that much issues with the solution either.

As probably mentioned earlier, we have had some issues with the API not being up-to-date and causing our synchronization of our Microsoft Dynamics 365 CRM to fail. Which in turn caused our management dashboards and KPI's to not refresh with the most recent data.
This is one aspect users of the Tibco Cloud integration solution need to keep in the back of their head.

We started using Tibco Cloud Integration (more specifically Scribe) on the proposal of our partner that assisted us in the migration from Siebel CRM to Microsoft Dynamics 365 CRM at the time. And since then we also did the exercise to map our application landscape and enterprise architecture. So we probably would check if we can consolidate on one integration solution to do the kind of work that Tibco Scribe does, which in the end could be to stick to Scribe or move to another solution we might already have.

We only use it to replicate our Microsoft Dynamics 365 CRM data to our on premise Microsoft SQL server database. We currently don't have other use cases for the tool. And I don't think this will change in the near future, for internal replication and integration jobs we have another tool that we use extensively.

None

No real opninion

We have not needed any training. The User interface is self explanatory and makes training unnecessary.
Mainly because there's a small number of steps needed to create a replication job in Tibco Cloud Integration (Scribe). Manually selecting the entities to be replicated from our Microsoft Dynamics 365 CRM was the most labour intensive part.

No, no specific recommendations. Just set up the basic components like connections to your source and destination systems and create a job. Then select the entities you need to replicate or integrate. Save the job and schedule it to do it's thing. Nothing more, nothing less.
It really is that easy to setup and get started.

No, we did no customization

My most recent ticket was one such situation. It initially was picked up by a first level support engineer but because of holidays it was put on hold. Then "out of the blue" a French second level support engineer took over the case and we had a screen sharing session to have look to our on premise agent installation. There he immediately a possible cause for the issue we had, and he was spot on.
He was an extremely friendly person who really helped me out at that time and resolved my case in a very short time. I was very pleased with the way this case was handled.

We only used it for replication

We did not negotiate with Tibco directly

No, since we did not negotiate with Tibco directly