ChMS - MinistryPlatform Follow
Focus Missions integrates with MinistryPlatform through a series of Apis creating a bi-directional sync with the thought that majority of the work would continue to happen in Focus Missions with that data being moved to MinistryPlatform.
Setup
In order to setup the integration between Focus Missions, head over to the Settings section in Focus Missions by navigating to Admin < Settings < Software Integration < MinistryPlatform. This will give you detailed instructions on how to setup the MinistryPlatform Api User inside of MinistryPlatform.
With the Focus Missions screen open for MinistryPlatform, open a new tab and navigate to the MinistryPlatform instance.
Navigate to Adminstration < API Clients. Click on Add New to start the creation of a new user.
Using the information that is on the Focus Missions Software Integration screen, input the values from Focus Missions to MinistryPlatform.
Because of the areas that Focus Missions interacts with MinistryPlatform, it is recommended that the Client User assigned to the API Client has the role of "Administration" in MinistryPlatform.
After the API Client is created in MinistryPlatform based on the values that are presented in Focus Missions, return to Focus Missions and add the domain for the MinistryPlatform instance. EX: https://partner.ministryplatform.net
Make sure that it is only the domain which will most likely end with a .org or .com
Click Verify once the url is present. This will communicate with MinistryPlatform on your behalf to make sure the credentials have been inserted correctly.
Global Settings
After setup is complete, Focus Missions will ask for some global variables to help sync data between MinistryPlatform and Focus Missions.
Focus Missions will rely on these global settings to determine how to send data to MinistryPlatform.
1. Household Source: When a new household is created in MinistryPlatform from Focus Missions, select the household source to attach to the household.
2. Household Congregation: Otherwise known as campus. when a new household is created in MinistryPlatform from Focus Missions, select the household congregation to attach to the household.
3. Team Member Participant Type: In MinistryPlatform, a contact also has a Participant Record. The Participant Record allows for individuals to be added to events and for donor records to be created in order to create pledges. When a participant record needs to be created for a Team Member, select the Participant Type to attach to the participant record.
4. Donor Participant Type: In MinistryPlatform, a contact also has a Participant Record. The Participant Record allows for individuals donor records to be created. When a participant record needs to be created for a Donor select the Participant Type to attach to the participant record.
5. General Person: When donations happen on the trip itself online from Focus Missions, Focus Missions will record that donation in MinistryPlatform. In order to record the donation, it is required that the donation has a donor record which requires a contact record. Type in the Contact ID from MinistryPlatform for the "General Person" inside MinistryPlatform.
6. Internal Transfers Person: When donations are moved in Focus Missions that originated online, those moves are recorded in MinistryPlatform. MinistryPlatform suggests having an Internal Transfer Person in MinistryPlatform where a positive / negative donation distribution offset can be present to show the move. This field is used to provide the Contact ID of the Internal Transfer Person in MinistryPlatform.
7. Notes: When data is moved to MinistryPlatform from Focus Missions, Focus Missions will add notes to that data so it is possible to identify how the data originated in MinistryPlatform. Focus Missions gives default content for the note but it is editable and its possible to alter the note content.
8. For the notes, what entities should the note be added to. There are many records in MinistryPlatform that the note can be added to.
9. Once all the information is provided, click save.
When the MinistryPlatform verification is successful, Focus Missions will create multiple Webhooks inside MinistryPlatform. Please do not delete these webhooks. If they are deleted, Focus Missions will recreate them. The image below shows an example of the webhooks that Focus Missions can create.
Trip Management
Import Trip From MinistryPlatform
It is possible to import a mission trip from MinistryPlatform into Focus Missions. When doing this, all pledge campaign / event data will be moved from MinistryPlatform to Focus Missions along with any pledges and donations associated with those pledges.
For admins that have the ability to manage / create trips, a new menu under Trips will be displayed called "Import From MP"
Clicking "Import from MP" will list all the mission trips that are visible in MinistryPlatform. A mission trip in MinistryPlatform is a pledge campaign that has an event tied to it. The list will show all mission trips and also specify if the mission trip has already been imported to Focus Missions. For any trip that needs to be imported, click the "Import" button next to any pledge campaign that needs to be imported.
In order for the import to start, you must specify the City and Country that this trip is for. This field is required when creating trips in Focus Missions which is why it is required in order to import. Once the fields are populated, click on "Queue to Import"
Trip Creation
Focus Missions interacts with MinistryPlatform around Trip Management by creating and maintaining the trip data from Focus Missions to MinistryPlatform. When creating a trip in Focus Missions, there will be a section for MinistryPlatform Options. These options will provide Focus Missions with a way to create the necessary data in MinistryPlatform for the trip.
1. Event Type: Focus Missions will create an event for each trip that is created in Focus Missions. Select the event type that should be attached to the event in MinistryPlatform.
2. Congregation: Focus Missions will create an event for each trip that is created in Focus Missions. Select the congregation that should be attached to the event in MinistryPlatform.
3. Donation Program: When a donation is made online either to a trip or a team member, a donation distribution is created for that donation. Select the Program to attach to that donation distribution.
4. Participant Program: When a payment is made online by a team member, a donation distribution is created for that donation. Select the Program to attach to that donation distribution. This is useful if payments are not to be tax deductible.
Creating a trip in Focus Missions will create an Event in MinistryPlatform. If the trip has a price associated with it, a Pledge Campaign will be created in MinistryPlatform.
Below is the mapping of data fields from Focus Missions and how they are populated in MinistryPlatform
| Event | |
| MinistryPlatform Field | Focus Missions Value |
| Event Title | Trip Name (first 75 characters) |
| Event Type | Event Type selected under MinistryPlatform Event Options |
| Congregation | Congregation selected under MinistryPlatform Event Options |
| Description | Description (first 2000 characters) |
| Program | Donation Program selected under MinistryPlatform Donation Options |
| Primary Contact | Contact of the person who created the trip in Focus Missions |
| Participants Expected | Maximum Headcount |
| Event Start Date | Travel Start Date |
| Event Date Date | Travel End Date |
| Registration Start | Registration Start Date |
| Registration End | Registration End Date |
| External Registration Url | Trip Public Short Url |
| Pledge Campaign | |
|
MinistryPlatform Field |
Focus Missions Value |
| Campaign Name | Trip Name (first 40 characters) |
| Campaign Type | The MinistryPlatform Config Setting Value for 'MissionTripCampaignTypeID' |
| Description | Description (first 450 characters) |
| Campaign Goal | MaximumHeadCount * Trip Price |
| Start Date | Date the trip was created in Focus Missions |
| End Date | 30 days after Travel end Date |
| Fundraising Goal | MaximumHeadCount * Trip Price |
| Registration Deposit | Trip Initial Deposit |
When searching for individuals to add to a trip from an admin perspective, Focus Missions will search MinistryPlatform for the person based on first name and last name. If the individual exists in MinistryPlatform, the information about the individual is displayed to be selected.
People Management
Focus Missions will add people to MinistryPlatform when they do not exist and will update person information when information about the person is updated in Focus Missions.
MinistryPlatform currently cannot inform Focus Missions when changes to person information is changed in MinistryPlatform.
Below is the mapping of data fields from Focus Missions and how they are populated in MinistryPlatform for a contact.
|
MinistryPlatform Field |
Focus Missions Value |
| Household Information | |
| Household Name | Last Name |
| Household Source ID | Global Household source ID from Settings |
| Congregation ID | Global Congregation ID from Settings |
| Address | Person Address (Address is stored on household in MinistryPlatform) |
| Contact Information | |
| First Name | First Name |
| Middle Name | Middle |
| Nickname | NOT USED |
| Last Name | Last |
| Display Name | Last Name , First Name |
| Gender | Gender |
| Date of Birth | BirthDate |
| Contact Status | MinistryPlatform Default Config Value for 'ContactStatusID' |
| Mobile Phone | Phone |
Team Member Management
Focus Missions assigns event participants to the event in MinistryPlatform for team members going on the trip. These team members can be seen in MinistryPlatform by selecting the event and then looking at the participants tab at the bottom.
If the trip has a price then Focus Missions will assign a Pledge record to the Pledge Campaign that Focus Missions created in MinistryPlatform when the trip was created in Focus Missions.
When an individual applies for a trip, the process starts to add that person to the event in MinistryPlatform. Depending on the rules set on the trip in Focus Missions, the event participant is added in one of three participation Statuses.
- Interested (if the individual applied and has not been accepted to the trip yet in Focus Missions)
- Registered (if the individual is actively on the trip either by being accepted or added to the trip in Focus Missions
- Cancelled (if the individual was once on the trip and is now removed. or the applicant was rejected
As the individual goes through the process, Focus Missions will continue to update MinistryPlatform on changes to the group member.
Below is the mapping of data fields from Focus Missions and how they are populated in MinistryPlatform for a n event participant.
| MinistryPlatform Field | Focus Missions Value |
|---|---|
| Participant | The Participant Record found or created from Focus Missions |
| Participation Status | Based on what stage the individual is in on the trip
|
| Notes | Created if the Focus Missions MinistryPlatform settings are configured to add notes |
If the trip has a price and a pledge campaign was created in MinistryPlatform, a pledge record will be created in MinistryPlatform to track progress. Depending on the rules set on the trip in Focus Missions, the pledge is added in one of three pledge statuses.
- Pending (if the individual applied and has not been accepted to the trip yet in Focus Missions)
- Active (if the individual is actively on the trip either by being accepted or added to the trip in Focus Missions
- Discontinued (if the individual was once on the trip and is now removed. or the applicant was rejected
| MinistryPlatform Field | Focus Missions Value |
|---|---|
| Donor | The Donor Record found or created from Focus Missions |
| Pledge Status |
|
| Notes | Created if the Focus Missions MinistryPlatform settings are configured to add notes |
individuals who have a MinistryPlatform user account can use the same credentials to log into Focus Missions
Background Check Management
Focus Missions allows for background checks to be run when the trip is setup to require one. MinistryPlatform also has the ability to request and keep background checks on individuals. Focus Missions can use MinistryPlatform to identify if a background check already exists for a person before ordering one.
Focus Missions requires the use of Protect My Ministry in order to connect Background Checks between Focus Missions and MinistryPlatform.
In order to use Background Checks as a MinistryPlatform integration, Protect My Ministry must be turned on in Ministry Platform. When this is complete, Focus Missions will use the background check types that are created in MinistryPlatform to populate the list of available background check types to use in Focus Missions for a background check. Currently, Focus Missions only allows for one background check type to be selected.
The background check type selected will be used to identify if the person has a background check in MinistryPlatform already. If a person has a background check but it doesn't match the type selected, a new background check will be created for the individual.
When the individual applies or is added to the trip, Focus Missions will check MinistryPlatform for an existing background check for the individual. If one exists already and it hasn't expired (in Focus Missions you specify how long a background check is good for) then Focus Missions will pull the information from MinistryPlatform to show that the individual has an already run background check.
If the individual does not have a background check already in MinistryPlatform for the background check type selected, one will be run from Focus Missions. Once the background check is completed, the information about the background check will be recorded in MinistryPlatform as well as Focus Missions.
Donation Management
Focus Missions does bi-directional syncing of donation information to and from MinistryPlatform. Any donation made in Focus Missions will be moved to MinistryPlatform as a donation with donation distributions.
In any online donation given to a pledge in MinistryPlatform will be moved over to Focus Missions.
When a donation is made in Focus Missions, a donation will be created in MinistryPlatform. It is possible for a donation to have multiple donation distributions associated to it, depending upon how the money needs to be allocated to team members. For instance, if a group of 3 people apply for a trip and want to pay a $100 deposit, a donation of $300 will be recorded in MinistryPlatform and then 3 different $100 donation distribution records will be created and associated with the 3 participants going on the trip.
Below is the mapping of data fields from Focus Missions and how they are populated in MinistryPlatform for a donationPayment .
| MinistryPlatform Field | Focus Missions Value |
|---|---|
| Donation | |
| Donation Amount | The amount of the entire donation |
| Donation Date | Date of donation success |
| Payment Type | Credit Card or ACH |
| Notes | Created if the Focus Missions MinistryPlatform settings are configured to add notes |
| Transaction Code | ReferenceNumber NOTE: This reference number differs depending on the Payment Merchant |
| Currency | USD |
|
Donation Distribution |
|
| Amount | The amount of the transaction (could be dependent on the selection on group signup for pay deposit or pay in full) |
| Program | Set by the Donation and Participant Program selection on trip creation |
| Pledge | Set by Focus Missions. A Pledge is created for the team member when person is added to trip in Focus Missions |
| Target Event | The Event that is created by Focus Missions when trip is created. |
| Notes | Created if the Focus Missions MinistryPlatform settings are configured to add notes |
Focus Missions will check MinistryPlatform for new donation distributions associated with Pledges periodically. In order for a donation distribution to be picked up, the donation distribution must be associated with a Pledge selecting the pledge in MinistryPlatform
This is useful when you have a check or cash that was handed to you and you need to record it.
Focus recommends that cash and check donations are recorded first in MinistryPlatform. This will allow Focus to pick up the donation and record it in Focus Missions
Pushpay Donations
If you use Pushpay as your online giving provider, then donations will be recorded in MinistryPlatform via Pushpay and not Focus Missions. Focus Missions will communicate with Pushpay to identify the payments that have been made for trips and team members and alter the donation distributions of the donation once Pushpay writes the donation to MinistryPlatform.
Pushpay writes a donation in MinistryPlatform and one donation distribution record as well. Once Focus Missions identifies that donation, it will split the donation into distributions necessary (ex: 4 people sign up for a trip and the payment needs to be split) and will associate to the right pledges in MinistryPlatform.
If Pushpay is the payment merchant, you will no longer select the MinistryPlatform Donation Program options when creating a trip. Instead you will select the Pushpay Merchant and then the Fund that should be associated from Pushpay
