Contents
Field Name Definitions (Coming Soon)
Introduction
The CRM Migration template is designed to assist you and your organization with mapping your existing data to CRM fields and data types. This article describes the CRM Migration Template.
You can use whichever templates best match your data and then modify them by adding or deleting columns as needed for your specific situation.
If your data is in a different format and you require assistance with mapping, configuration, and understanding how your data will map to CRM fields, then you may want to consider reviewing our Migration Service Options.
Tab Descriptions
Tab |
Data Type |
Short Description |
Individual Contact Information |
Contact | All contact information (address, phone, email, etc) associated with people can be added to this sheet |
Organization Contact Information |
Contact | All contact information (address, phone, email, etc) associated with Organizations, Businesses, Partners can be added to this sheet |
Gifts (Donations) |
Transactional | All historical data for Donation (Donations & In-Kind Gifts) can be added to this sheet. |
Pledges |
Transactional | All historical data for Pledge giving history can be added to this sheet. |
Event Details |
Configuration | To migrate Event Registrations you must configure events prior to migration or complete this sheet with the detail of each event you would like to migrate. |
Event Registrations |
Transactional | All historical data for Event Attendance and Ticket Purchases (Donations & In-Kind Gifts) can be added to this sheet. |
Membership Levels |
Configuration | To migrate Member History you must configure Membership Levels prior to migration or complete this sheet with the detail of each event you would like to migrate. |
Membership History |
Transactional | All historical data for Member history (Payments & Renewals) can be added to this sheet. |
Grants |
Transactional | All historical data for Grants can be added to this sheet. |
Sales (Other Items) |
Transactional | All historical data for sale of other items (excluding: Event Tickets, Memberships, and gifts, can be added to this sheet. |
Interactions & Tasks |
Transactional | All historical data of Communication History can be added to this sheet. |
Funds |
Configuration | If you are migrating Donations and you have a lot of Funds, you can use this template to speed up the configuration process. |
Campaigns |
Configuration | If you are migrating Donations and you have a lot of Campaigns, you can use this template to speed up the configuration process. |
Programs |
Configuration | If you are migrating Donations and you have a lot of Programs, you can use this template to speed up the configuration process. |
Chart of Accounts |
Configuration | If you are going to by using the Quickbooks sync or Financials, and you would like to set up Chart of Accounts, you can use this template to speed up the configuration process. |
Account Classes |
Configuration | If you are going to by using the Quickbooks sync or Financials, and you would like to set up Account Classes, you can use this template to speed up the configuration process. |
Pricing per Module
To migrate data to CRM there are a couple of options. You can choose to use our import utility to migrate Basic Contact information and Gifts, or you may choose to use our migration services to assist you with getting all of your data into CRM.
For more information about our data migration services, click here.
Tab |
Estimated Cost to Migrate Data |
Individual Contact Information |
$250 |
Organization Contact Information |
|
Gifts (Donations) |
$250 |
Pledges |
$250 |
Event Details |
$500 |
Event Registrations |
|
Membership Levels |
$500 |
Membership History |
|
Grants |
$250 |
Sales (Other Items) |
$250 |
Interactions & Tasks |
$250 |
Funds |
$250 |
Campaigns |
|
Programs |
|
Chart of Accounts |
$250 |
Account Classes |
Row Descriptions
Row |
Name |
Short Description |
1 |
CRM Field Name | This row indicates what the fields will be named in Fundly. |
2 |
Field Type | This row indicates what the available field type will be in Fundly upon migration. |
3 |
Field requirement | In order to create data entries in CRM, there are validations that are required in order to complete the records. In Row 3 of the Migration template, there are 'Field requirements' that indicate what the validations are for the listed CRM field. |
> 4 |
Sample Data | These row(s) are filled with sample data to assist you in determining how your data will be entered in this template |
Field Types
Field Type |
Example |
Short Description |
Text |
 |
Used to enter general text (Including numbers) |
Number |
 |
Use to enter number only (Excluding characters) |
Single Dropdown |
 |
Dropdown menu where you will only be able to select one option. Usually requires configuration in CRM prior to migration |
TRUE/FALSE |
 |
Only True OR False values can be provided in this column. Other options: Yes/No True = 1 False = 0 |
Multiple Select |
 |
In the CRM this will be represented with multiple checkboxes or a dropdown where you can select multiple options. Usually requires configuration in CRM prior to migration. Required: When entering data for multiple select options in the template, you must separate the multiple values with a comma. Example: "May, Oct, Sept, Dec"
|
Currency |
 |
Only dollar amounts can be entered in this column. Example: $10.00, $(25.00), $100 |
Date |
 |
Only dates can be entered in this field. Acceptable date format = mm/dd/yyyy Example: 04/07/2015 |
Requirements
In order to create data entries in CRM, there are validations that are required in order to complete the records. In Row 3 of the Migration template, there are 'Field requirements' that indicate what the validations are for the listed CRM field.
Field Requirement |
Short Description |
Mandatory |
Fields are required to Migrate data to CRM. Without data in the required fields, certain data may not get migrated |
Typical |
Fields are data fields that are frequently used by Non-Profits migrating data to CRM |
Seldom |
Fields are seldom used by Non-Profits when migrating to CRM |
Typical
|
Additional Values may be required for configuration (added) if they are not standard within CRM. If the values provided in the columns are not standard and not configured prior to migration, they will not be successfully transferred. Click here to view a list of all the default value available in CRM |
Helps w/Duplicates |
Inlcuding this information in the data file helps us use a unique identifier to help merge duplicates during migration. |
Field Name Definitions
COMING SOON
Comments
0 comments
Article is closed for comments.