The easiest way to replicate our Dynamics 365 CRM data on premise
Guy DeBacker profile photo
Updated December 06, 2019

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

Score 8 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with TIBCO Cloud Integration (including BusinessWorks and Scribe)

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.
  • The setup of both the sending as the receiving side is easy, you don't really need expert skills to set up the "technical" part.
  • We don't need a complicated ETL tool to extract the data from the Cloud environment.
  • The overall management of what needs to be synchronized is straight forward.
  • Thanks to the specific SCRIBE fields in the receiving database we have a track of deleted records (for which we don't have anything in the CRM database).
  • The synchronization is not fast and seems to do some unnecessary work.
  • Selecting the entities to synchronize is quite tedious, you need to scroll through quite a big list (especially when you have a lot of custom entities) a filter would be welcome.
  • You need to manually update the metadata of the sending connection to see newly created entities, it would be nice if you could schedule those tasks too.
  • We already had quite some situations where MS changed things in the data model of CRM that caused issues in the sync tasks.
  • We didn't need to invest resources in setting up something similar in a more complicated ETL tool.
  • We don't need to worry about keeping this environment up to date, very little maintenance from our end.
  • Sync the data of our Dynamics 365 CRM data to on premise database for reporting
  • batch migrate data from legacy systems after go-live
1 - I'm the only user and as the IT application engineer, I'm responsible to keep our production applications up and running. And Scribe is one of the applications in our BI environment. Together with the SQL databases and Qlik Sense, which we use for reporting and dashboarding of our KPI's.
Both for our management and our Sales team.
Scribe was proposed by our partner assisting us in the migration from Siebel CRM to Microsoft Dynamics 365 CRM, to do the database sync of the information stored in our Cloud CRM system. Talend we use for our internal ETL and API development, the tools are complementary.
They both have their strengths and weaknesses.
  • Existing Relationship with the Vendor
We we're unfamiliar with software to integerate cloud environments with our on premise environments, so we trusted our migration partner to help us with finding the best solution for the case at hand. They had experience with Tibco Scribe so we went for their proposal to use this solution to get the Dynamics 365 data in our on premise database for reporting.
  • migrate Salesforce data into a live production MS dynamics 365 environment
  • Self-taught
As mentioned earlier, setting up a SCRIBE environment is extremely easy, you don't need any technical skills to setup the "technical" part of the setup. You do need some knowledge of the source environment to determine which tables or enities you need to select for the integration purpose you have in mind. But is not related to the Tibco tool.
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.
It is a great tool to quickly set up synchronization between an on-premise data warehouse and a cloud solution as MS Dynamics 365 Customer engagement (CRM), which was our specific use case. Most of the issues we ran into could be worked around without any special technical skills.

When you need more specific control (field level) of what needs to be synchronized, you need to look to a more specialized tool to do the data integration.

TIBCO Cloud Integration (including BusinessWorks and Scribe) Feature Ratings

Pre-built connectors
8
Support for real-time and batch integration
5
Monitoring console
8

Learnings and Advice

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.
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.

Using TIBCO Cloud Integration core features

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.

Using TIBCO Cloud Integration (including BusinessWorks and Scribe)

1 - I'm the only user and as the IT application engineer, I'm responsible to keep our production applications up and running. And Scribe is one of the applications in our BI environment. Together with the SQL databases and Qlik Sense, which we use for reporting and dashboarding of our KPI's.
Both for our management and our Sales team.
Even though I have an IT background, I don't find it a pre-requisite to use Scribe.
  • other replications
Since everything is running as it should be, we currently don't have plans to change the application used to do the kind of work we use Tibco Cloud integration for the moment. It does what it needs to do in a way that currently asks very little maintenance and management from our end. So you could say the TCO of this solution is at an acceptable level.

Evaluating TIBCO Cloud Integration (including BusinessWorks and Scribe) and Competitors

TIBCO Cloud Integration (including BusinessWorks and Scribe) Implementation

Implementation is a no-brainer, it's just installing the agent on our Microsoft SQL server environment. Linking it to the Tibco Cloud Integration platform and then setting up the connections to the source and destination systems. Once those steps have been done, it's just setting up the jobs using the connections and selecting the data we needed to be replicated.
Change management was minimal - None, we had no prior use case. So this was the initial setup for what we needed to do. And also for us this a backend solution it is hidden from the end users. They only want to see the most recent data in their dashboards and KPI's and how the data is fetched from the source system is not their concern.
  • Setting up the list of entities to sync

TIBCO Cloud Integration (including BusinessWorks and Scribe) Training

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.
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.

Configuring TIBCO Cloud Integration (including BusinessWorks and Scribe)

As mentioned already a few times in the previous sections. The user interface is self explanatory and very easy to use to setup the environment, and prepare for first use. The configurability is just right for this type of product and absolutely not too limited or too complex to prepare for use.
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 have not done any customization to the interface
No - we have not done any custom code

TIBCO Cloud Integration (including BusinessWorks and Scribe) Support

My current experience with the support for Tibco Cloud Integration has been very positive. I always worked with skilled support engineers who knew the product well and most of the time understood my problem from the start. They also needed little time to resolve my cases and until now I have not needed to escalate tickets to second level support.
ProsCons
Quick Resolution
Good followup
Knowledgeable team
Problems get solved
Kept well informed
No escalation required
Quick Initial Response
None
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.

Using TIBCO Cloud Integration (including BusinessWorks and Scribe)

As mentioned in the previous sections, setup and maintenance is extremely easy. We don't have many issues for which we need support and there is no need for deep technical skills to use Tibco Cloud Integration platform.
The solution provides everything we need for our specific use case, being the replication of our Microsoft Dynamics 365 CRM data to our on premise database for reporting.
ProsCons
Relatively simple
Easy to use
Technical support not required
Well integrated
Consistent
Quick to learn
Convenient
Feel confident using
Familiar
None
  • Basic setup of jobs
  • selecting the MS Dynamics entities we needed synhronization for to on-prem
  • Debugging when something goes wrong

TIBCO Cloud Integration (including BusinessWorks and Scribe) Reliability

We have not yet needed to scale the solution for which we use Tibco Cloud Integration. As mentioned earlier, we only use it to replicate our cloud hosted Microsoft Dynamics 365 CRM environment. We don't have any plans to use the tool more extensively in the future.
In the three years we use Tibco Cloud Integration platform Scribe, we have not yet experienced any outages. The only issues we had were with Microsoft changing the Microsoft Dynamics 365 REST API which caused our replication jobs to fail.But for the time being we have not yet had any real downtime impacting our scheduled replication jobs.
TIBCO Cloud Integration (including BusinessWorks and Scribe)'s performance of the user interface are not to be complained about. The user interface is swift and is a pleasant user experience. The replication jobs take some time to finish but that is because the number of records to be updated/created on a daily basis is quite big. I did split up the jobs between highrunners (entities with a lot of changes) I update on a daily basis and quite stable entities that I update weekly. That solved my issue of a way to long replication.

Integrating TIBCO Cloud Integration (including BusinessWorks and Scribe)

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.
  • Microsoft Dynamics 365 CRM
It was a very simple data replication we needed for internal reporting on the Microsoft Dynamics 365 CRM data.
We only used it for replication

Relationship with TIBCO Software Inc.

Our partner that assisted us in our migration to Microsoft Dynamics 365 CRM took care of the purchase process. We were not involved in it so I can not rate this part.
Our renewals are done by ourselves (more specific our purchasing department) and so far we have not had any issues related to that either. Transferring the administration to us after we stopped the collaboration with the initial partner was also very easy and went without any hassle.
We did not negotiate with Tibco directly
No, since we did not negotiate with Tibco directly

Upgrading TIBCO Cloud Integration (including BusinessWorks and Scribe)