Skip to main content

How Many CRMs Do You Need?

Source: Microsoft.com

Managing relationships with people is the heart of a Customer Relationship Management (CRM) system, whether they are customers, vendors, business partners, constituents or other people. So in that sense, there is hardly any organization that doesn't do CRM even if they don't own CRM software such as Microsoft Dynamics CRM or Salesforce.  The most common way to manage people is in your email such as Outlook contacts, or Excel spreadsheets with lists of people to whom you send mail or emails.

What we often find that our clients inadvertently end up with more than on CRM, because the same information on people is tracked in multiple systems.  Universities, for instance, may have separate systems for applicants, students, alumni, donors, and parents even though over time these may be the same people. Similarly, organizations that recruit members or employees end up tracking the same people over a long period of time.  The more overlapping CRM systems you maintain, the greater the risk of data inconsistency.

If your CRM consists of Outlook and Excel, ask yourself when you might outgrow this approach. Moving to a mature CRM product gives you much greater control over your data and provides the ability to do automated marketing outreach, sales tracking and much more than you can expect from a spreadsheet.

If you have multiple CRM systems that overlap, ask yourself whether the benefits of consolidating and standardizing these systems is worth the cost and the effort.  You could potentially save on software licensing as well as reduce the cost of training and support by moving to a common CRM platform.


Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do