Suite CRM Integration
Suite CRM is used primary to transmit the necessary documentation required to process a student's enrollment. The application is also used to track new 'homeroom' customers, or new businesses that want to open classrooms. Because we want to market the PEMS as a stand alone product, see the Product Marketing Strategy. This integration must be structured as optional.
The approach is used to map the data architecture between PEMS and Suite CRM.

Homeroom (classroom location)
The master list of homerooms is managed in PEMS. However, the Homeroom record first enters the universe through Suite CRM because a Homeroom is a potential client of the School.
PEMS can enter the homeroom directly when the Suite CRM is not used, but if Suite CRM is implemented, then the homeroom comes from Suite into PEMS.
The homeroom is a account record with type = "homeroom"
The homeroom record is created in PEMS when an opportunity record with type = "Homeroom" that is linked to the account is closed.
Student (Enrollment)
PEMS sends the information from an enrolled student to Suite CRM. Student leads go into PEMS from the website, but untill the student is accepted, there is to transmission of information to Suite CRM.
Opportunities records in Suite CRM represent student enrollments in PEMS. They are created only after the enrollment form submitted on the website.
Student Name > Opportunity Name
The opportunity type for a student enrollment being entered from PEMS is "Enrollment." The opportunity TYPE field and options are shown below:
The remaining terms is imported in to Suite CRM so that the total revenue from the enrollment may be calculated. The customer field "Remaining Terms" has been created in Suite CRM.
Parents are contacts in SuiteCRM, so when a new student is entered from PEMS into Suite, the primary parent in only created if a contact record is not found.
Other Schools (Previous School)
In order to create an esign pdf from SuiteCRM, the previous school must also be an account record in Suite CRM. A contract record is created that is linked to the previous school account, the parent contact, and the student opportunity. From this contract, the data in the records request can be entered into the merge pdf.
The list of Previous Schools (Other Schools) in PEMS must be synchronized with the set of Account records that are type of registrars.
PEMS is to be sold as an add-on module to Moodle, and it should not require a CRM to function. Therefore, the list of previous schools must be self-contained in PEMS. When the student is accepted in PEMS, the user must select the correct name from the other schools table based on the text field completed in the enrollment form. The other school record must be entered in the enrollment process in PEMS before the student may be accepted.
When the SuiteCRM integration point is implemented, when every and opportunity record is created for a new student record, then the new other school must also be created as an account record with type = "Registrar". If the record exists already in Suite CRM, then no new other school record will be created.
The following fields are in the PEMS for other schools and should be mapped into the respective SuiteCRM fields.
The Name is mapped to the Suite CRM Account Name.
The Registrar name is mapped to the Suite CRM custom text field "Registrar Name"
The address is mapped to SuiteCRM Shipping address.
The email is added as the primary email (email1).






