The Great Migration: Part 2, The Integrations

Remember this table from Part 1?

Total Database size 285GB
Number of Users 120
Number of Email Router Users 20
Number of integrations 6
Number of custom entities 72
Number of customised entities 4
Number of Workflows 146
Number of custom Workflow Activities 36
Number of Plugins 18

We just ignored that Number of Integrations bit but we really shouldn’t have as it could easily ruin all our plans.  Let see what is hiding behind that innocent looking 6.


Much more intimidating, lets take a quick look at each of them and then over the next few posts we will look at how we are planning on handling them

PA Event Feed

This is actually a small console application the runs on a schedule, checks an FTP site for available XML files, downloads the files and converts the contents in to CRM Entities then uses the CRM Service to insert them in to the CRM Database.

The records are inserted into CRM so users can make amendments before the MB Webservice converts them into a different XML format and pushes them to the Explore database using a plugin.

Twitter Monitor

This is another console application running as a WebJob in Azure.  It periodically queries a list of Twitter feeds and uses the @names to check if they mention Accounts in CRM, if they do the Tweet is saved to CRM and attached to the Account.

CommuniGator is a third party marketing automation tool, the product is capable of a wide variety of marketing tasks and has some very useful, advanced abilities.  Here it is just used to send eNewsletters to marketing lists created in CRM and to track the open and click through rates.

MB Webservice

This is a nasty old SOAP endpoint that exposes 2 methods, this first simply allows the caller to request an image resource by ID, these are passed to Explore by a plugin every time one of 6 custom entity types are modified or created.

The second accepts an XML document and maps the data to CRM entitles, primarily used for registering newsletter subscription requests and setting the relevant flags on the contact entity and for converting ‘Contact Us’ information in to Cases in CRM.


This is used to manage images related to the custom entities that feed Explore.  Each record in CRM has a folder on SharePoint to hold its files and an iFrame allows users to view these in CRM.

Project Management System

This is an internally created tool – an ASP.NET MVC site actually – that is used to manage projects the organisation is working on and bidding for.  It links to CRM to associate the Account with the finance and time management systems used for billing and activity management.

So, that’s the Scary Six.  In later posts we will look at how we are going to handle each of these without breaking the existing functionality.


Author: Stuart

Crazy Person

2 thoughts on “The Great Migration: Part 2, The Integrations”

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s