In the first two parts of this series we have installed SuiteCRM locally, imported its model into the Vertabelo database, and created relationships based on assumptions. In Part 3 we took a closer look at the most important parts of the CRM, how to use them, and how the data is stored in the database. This article will continue where Part 3 ended and will close the series. We’ll take a closer look to other modules of SuiteCRM including campaigns, opportunities, projects, documents and users, and roles administration.
Previously in this series, we imported SuiteCRM’s database model into Vertabelo and showed how to use Vertabelo’s features to organize it. In this article, we’ll see how common CRM data is stored in its database. We’ll also check the assumptions made in Part 2 about the relations between tables and their functions. If needed, we’ll make modifications to the model. What Do We Currently Have? In Part 1, we installed SuiteCRM locally using the Bitnami installation pack.
In Part 1 of this series, we successfully imported the SuiteCRM database structure into our online database modeling tool. That’s when we saw that the model contains 201 tables without relationships between them. We got a wild bunch of tables that looked really messy. In this article, I will show you how you can organize such a large model. Just after importing to Vertabelo, the SuiteCRM database model looks as follows:
Customer Relationship Management applications (CRMs) have been around for some time. We could argue a lot about their advantages and disadvantages when comparing them to each other. In this series, we’ll take a look at the database behind one popular open-source CRM: SuiteCRM. We will also show how to install everything we need. In upcoming articles, we’ll organize the data model and see how it reacts to changes made on the user interface.