Profiles
General Mapping
CommunitySuite Field |
FIMS Field |
Notes |
ID # |
N/A - CommunitySuite unique ID |
|
Legacy Code |
ID Code |
- Only Profile 1 person or organization migrating from FIMS will have a Legacy Code with a number in it.
- Spouse and Household profiles - no legacy ID code from FIMS.
- They will have a code of spouse or main_house and will be new profiles with the migration in CommunitySuite.
|
Anonymous Flag |
Anonymous Check Box on Donor Tab |
|
Website |
Web Site (web-site) |
|
TaxID (State) |
N/A |
|
FedID (SSN/EIN) |
Soc. Sec. No (ssno), Donor - Biographical |
|
Service Areas |
County Code (County), Profile 1 |
- Loose connection between Zip Code/County Code and Service Area.
|
Philanthropic Interest |
N/A |
|
Profile Types |
Affiliation Codes (Aff Pro) |
- All affiliation codes and sub affiliation codes migrate, but they will be sorted A-Z in CommunitySuite without any sub-hierarchy like it has in FIMS.
- They can be migrated to Profile 1, Profile 2, or Household record or copied to all three or two profiles.
|
Profile Fund Categories |
Fund Associations tab. (Rep Type) |
- Will migrate the Rep-Type Description.
- Migrates to Profile 1 record in CommunitySuite; however, it can be adjusted to also migrate to Profile 2 or Household record.
|
Address Types |
Address Types (Address-Type) |
|
Org Roles |
N/A |
|
Notes to the Profile |
Contacts tab, Notes tab, Comments radio button on the grantee/vendor/donor tabs |
- Notepad A-Z tabs, gift language, special handling, and contacts are all brought over as a note.
- These land on the native profile or can choose between individual/household.
- These will migrate standard on Profile 1 record but can be moved to Household record for profiles with a Profile 1 and Profile 2 setup in FIMS.
|
Note Types |
Contact Types (CntcType) |
- See Opportunities, List Type - Task/Note Types
|
Individual
CommunitySuite Field |
FIMS Field |
Notes |
Prefix |
Prefix, Profile 1 |
|
First Name |
First (FName), Profile 1, or (NickName) |
- First name will come over standard.
- If user is using nicknames, then migration can load nickname into the first name field. Profile first name will load to Legal First Name instead. If nickname is used for other purposes (like a comment), then it can be ignored, and first name will always come to this field.
|
Middle Name |
MInit (M.I.), Profile 1 |
|
Last Name |
LName (Last), Profile 1 |
|
Suffix |
Suffix, Profile 1 |
|
Legal First Name |
N/A |
- If nickname and first name are populated in FIMS and nickname is not being ignored, then this will be the first name from FIMS.
|
Gender |
Gender, Profile 1 or Profile 2 (does not migrate) |
- Gender can be set up post go live with a bulk update.
|
Work Organization |
Organization |
|
Work Title |
Title Code (Bus-title), Profile 1 |
|
Legal Name |
N/A |
- Legal name can be bulk updated to display the name different than that in the First/Last name field.
|
Salutation |
Default Salutation (Ctc-Salutation) |
- Any of the applicable salutations can be chosen.
|
Mailing Label |
Mailing Label (default) or Joint or Alternate Name |
|
Birthday |
Birth Date, Donor Tab under Biographical Info |
|
Deceased Flag |
If "Deceased" or "inactive" is filled in, Donor Tab under Biographical Info |
- If the profile is marked inactive in FIMS, it will migrate as deceased into CommunitySuite, but no decease date will be documented.
|
Deceased Date |
Deceased, Donor Tab under Biographical Info |
|
Partner/Spouse
If a profile 2 person exists in FIMS, they will now be their own individual profile in CommunitySuite with a legacy code of Spouse.
CommunitySuite Field |
FIMS Field |
Notes |
Prefix |
Partner Prefix, Profile 2 |
|
First Name |
Partner First, Profile 2 |
|
Middle Name |
Partner M.I., Profile 2 |
|
Last Name |
Partner Last, Profile 2 |
|
Suffix |
Partner Suffix, Profile 2 |
|
Gender |
Gender, Profile 2 (does not migrate) |
- Even if tracked in FIMS, gender does not migrate.
- It can be bulk edited post go live.
|
Salutation |
Nothing migrates |
- Saluation is blank in CommunitySuite with the initial migration, but these can be set per formality preference.
|
Mailing Label |
Nothing migrates |
- Mailing label is blank in CommunitySuite with the initial migration, but these can be set per formality preference.
|
Birthday |
Birth Date field, Donor tab - biographical area, Partner |
|
Deceased Flag |
N/A |
|
Deceased Date |
Deceased Date, Donor tab - biographical area, Partner |
|
Email |
Partner E-mail, Profile 2 |
|
Work Phone |
Partner Work, Profile 2 |
- Profile 2 - Toggles between Cell and Work.
|
Mobile |
Cell-Phone (Cellular), Profile 2 |
- Profile 2 - Toggles between Cell and Work.
|
Households
CommunitySuite Field |
FIMS Field |
Notes |
Household Name |
See Notes |
- Household profile is created because there is a profile 1 person and a profile 2 person in FIMS.
- It is a new profile created with the migration.
- The profile 1 person and profile 2 person are their own individual profiles and will be linked to this household profile.
- The household profile combines the last name, profile 1 prefix plus first name plus middle initial then "and" plus profile 2 prefix first name and middle initial.
|
Legal Name |
N/A |
- Legal name can be bulk updated to display name different than that in the Household name field.
|
Salutation |
Nothing migrates |
- Saluation is blank in CommunitySuite with the initial migration, but these can be set per formality preference.
|
Mailing Label |
Nothing migrates |
- Mailing label is blank in CommunitySuite with the initial migration, but these can be set per formality preference.
|
Birthday |
N/A |
|
Deceased Flag |
N/A |
|
Deceased Date |
N/A |
|
Organizations
CommunitySuite Field |
FIMS Field |
Notes |
Organization Name |
Organization (Org Name) |
|
Contact |
|
- Cleanup in FIMS any duplicate org profiles that are actually primary contacts for organization, so they come over as individual profiles. After migration, link in CommunitySuite.
|
Prefix
|
Prefix, Profile 1 |
|
First Name
|
First (FName), Profile 1 |
|
Middle Name
|
MInit (M.I.), Profile 1 |
|
Last Name
|
LName (Last), Profile 1 |
|
Suffix
|
Suffix, Profile 1 |
|
Contact Title
|
Title, Profile 1 |
|
Legal Name |
N/A |
- Legal name can be bulk updated to display name different than that in the Organization name field.
|
Salutation |
Ctc-Salutation (Default Salutation) |
- Salutation does not appear with standard migration.
- It is possible to adjust to pull it in on organizational profiles.
|
Mailing Label |
Mailing Label (default) |
- Mailing label does not appear with standard migration.
- It is possible to adjust to pull in on organizational profiles.
|
Birthday |
N/A |
|
Deceased Flag |
Bio Tab Deceased Date |
- Org profile migrates as deceased if deceased date is populated. However, it is not common to have deceased dates populated on Org profiles.
|
Deceased Date |
Inactive flag |
- Org profile migrates as deceased if deceased date is populated. However, it is not common to have deceased dates populated on Org profiles.
|
Tax Class |
|
- Tax class does not migrate; however, it can be set up post go live.
|
FedID (EIN number) |
TaxID on Grantee tab |
- FedID (EIN Number) does not migrate; however, it can be set up post go live.
|
Addresses
If the address is a household, then take Profile 1 address. If you split to make the household triangle, then take Profile 1 and Profile 2. Profile 1 address becomes primary. Addresses on alternate addresses tab will migrate with address type if applied.
CommunitySuite Field |
FIMS Field |
Notes |
Address Type |
Address Type |
|
Address |
Address Line 1, Profile 1 tab |
|
Address 2 |
Address Line 2, Profile 1 tab |
|
City |
City |
|
State |
State |
|
Zip Code |
Zip |
|
Country |
Country |
|
Primary Flag |
|
- Address on profile 1 is marked primary; same address on spouse record will be marked primary.
- Migration will adjust to apply primary address flag to household.
- No alternate addresses will be marked primary.
|
Pay Flag |
N/A |
|
Mailing Flag |
N/A |
|
Inactive Flag |
N/A |
|
Emails
CommunitySuite Field |
FIMS Field |
Notes |
Email Type |
N/A |
|
Email |
E-mail |
- Email will include emails from the alternate addresses tab.
|
Primary Flag |
N/A, see note |
- E-mail on profile 1 is marked primary.
- Any emails included on alternate address tab will migrate, but they will not be marked primary.
|
Inactive Flag |
N/A |
|
Phones
CommunitySuite Field |
FIMS Field |
Notes |
Type |
N/A |
|
Domestic Number |
N/A |
|
International Number |
N/A |
|
Other Detail |
WorkExt |
|
Home Phone |
HomePhone (Home Phone) |
|
Work Phone |
WorkPhone (Work Phone) |
|
Mobile |
Cell-Phone (Cellular) |
- Profile 1 - Toggles between Cell and Fax.
|
Fax |
Fax |
- Profile 1 - Toggles between Cell and Fax.
|
Primary Flag |
N/A |
- If only one phone number is migrated, it is marked primary.
- If more than one phone number is migrated, then none of the phone numbers are marked primary.
|
Inactive Flag |
N/A |
|
Do Not Email |
N/A |
|
Do Not Call |
N/A |
|
Do Not Mail |
AllowMail checkbox is unchecked. |
- If AllowMail checkbox is unchecked in FIMS, then the entire profile, including all addresses, will be flagged in CommunitySuite as Do Not Mail.
|
Profile Fund Categories |
Fund Rep Type Coding in Fund Associations tab |
- The Rep Type description will be seen in CommunitySuite, not the Fund Rep Type code.
|
Profile Links |
Relationship Tab |
- If relationship inverse is not set in FIMS, only one side of relationship will be labeled in CommunitySuite.
|
Inactive Profiles
|
Inactive flag |
- These come over as deceased.
- A script can be run after the final data load that will look to see if there is a date in the deceased date field.
- If the deceased date is blank, then the profile will be marked as inactive.
|
History (Donations, Invoices, Vouchers, Grants, Scholarships) |
|
- These come over as relevant.
- All profiles with donation history will be marked as a donor.
|
Profile Designations
CommunitySuite Field |
FIMS Field |
Notes |
Customer Profile
|
|
|
Donor Profile
|
|
|
No additional fields from native profile |
|
|
Fund Advisor Profile
|
|
- This is set up post go live; however, training about how to set this up will take place.
|
Login Field
|
N/A
|
|
Donation Notify Flag |
N/A |
|
Grant Notify Flag |
N/A |
|
Statement Type Drop Down Menu |
N/A |
|
Funds |
N/A |
|
Grantee Profile |
|
|
FedID (SSN/EIN) |
TaxID or Charity No on Grantee tab |
- FedID (SSN/EIN) Field not included with migration, post go live bulk update only.
|
No Charity Status Check Flag |
|
|
Last Charity Status Check |
N/A - Calc |
|
Last Financial Date |
|
|
Public Request Flag |
N/A |
- This flag can be created and set post go live.
|
Default Grant Type |
Program Area (Grantee tab) |
- This does not currently migrate over to top level of profiles, but it does migrate to grantee level of profile.
- There are two separate tables currently in FIMS, one for grants and one for profiles. You can choose to run a manual query and migrate one or the other.
- This will migrate default grant type (Program Area) on grantee level of a profile if a grantee becomes default grant type.
- Only shows on grantee level of the profile. It does not show on top level of organization profile.
|
Student Profile |
|
|
School |
|
|
Student Number |
|
|
Vendor Profile |
|
|
Account Number |
|
|
Website |
|
|
Terms |
|
|
Default Account |
|
|
Need 1099 Flag |
1099 checkbox selected on Vendor tab |
- This populates on profile level of record.
- It can be viewed in Custom Profiles report with Needs 1099 field added.
|
Funds
Fund
CommunitySuite Field |
FIMS Field |
Notes |
Fund ID |
N/A - CommunitySuite unique # |
|
Name |
Fund Name (fund-name), Tab 1 |
|
Public Name |
N/A |
|
Sort Key |
Sort Name |
|
Created |
Date (established), Fund 1 |
|
Short Name |
Fund ID (fund-id), Tab 1 (Legacy Code for funds) |
|
Group |
Sub-Type, Tab 1 |
- Type can be brought over and can replace subtype, class, division or fundtype.
|
Sub-Group |
Fund Class, Tab 1 |
- Type can be brought over and can replace subtype, class, division or fundtype.
|
Division |
Division (divcode), Tab 1 |
- Type can be brought over and can replace subtype, class, division or fundtype.
|
Segment |
Fundtype, Tab 1 |
- Type can be brought over and can replace subtype, class, division or fundtype.
|
Sub of Fund |
Master Fund ID |
- Fund 2, Fund Stmt Radio Button.
|
Anonymous Flag |
N/A |
- User will set during training.
|
Donor Advised Flag |
N/A |
- User will set during training.
|
Agency Fund Flag |
N/A |
- User will set during training.
|
Affiliate Fund Flag |
N/A |
- User will set during training.
|
Restrictions
CommunitySuite Field |
FIMS Field |
Notes |
Default Restriction Drop Down |
N/A |
- User will set during training.
|
Endowed Flag |
N/A |
- User will set during training.
|
With Donor Restrictions Flag |
N/A |
- User will set during training.
|
Principal Restriction Drop Down |
N/A |
- User will set during training.
|
Principal Balance Value |
N/A |
- User will set during training.
|
Track Spendable Flag |
N/A |
- User will set during training.
|
Spendable Restriction Drop Down |
N/A |
- User will set during training.
|
Spendable Balance Value |
N/A |
- User will set during training.
|
Distribution Type |
Policy(polcode), Tab 1 |
|
Distribution Internal |
N/A |
- User will set during training.
|
Last Quarter End Balance |
N/A |
- CommunitySuite calculation.
- Click on value to see prior quarters
|
Options
CommunitySuite Field |
FIMS Field |
Notes |
Budget Flag |
N/A |
- User will set during training.
|
Statements Flag |
N/A |
- User will set during training.
|
Hide Amounts |
N/A |
- User will set during training.
|
No Memorials |
N/A |
- User will set during training.
|
Promote |
N/A |
- User will set during training.
|
Private |
N/A |
- User will set during training.
|
Default Grant Type |
N/A |
- User will set during training.
|
Service Area |
County Code( CountyCode), Fund 1 |
- If applicable, this can be switched to Region Code.
|
Fund Statement Format |
N/A |
- User will set during training.
|
YTD Interval |
N/A |
- User will set during training.
|
Admin Fee Settings
CommunitySuite Field |
FIMS Field |
Notes |
Admin Fee Types |
feecode (Admin Fee), Tab 1, and Tab 2 Radio button |
- Primary on Fund 1 tab.
- Additional are listed on Fund 2 tab.
|
Admin Fee Accounts |
N/A |
- User will set during training.
|
Admin Fee Group |
N/A |
- User will set during training.
|
Admin Fee Paid By |
N/A |
- User will set during training.
|
Admin Fee Reduces Spendable Flag |
N/A |
- User will set during training.
|
Cash Management
CommunitySuite Field |
FIMS Field |
Notes |
Revshare Options |
N/A |
- User will set during training.
|
Manage Cash |
N/A |
- User will set during training.
|
Investment Account |
N/A |
- User will set during training.
|
Checking Account |
N/A |
- User will set during training.
|
Min Checking Balance |
N/A |
- User will set during training.
|
Min Fund Balance |
NA |
- User will set during training.
|
Fund Summary |
Yearbook (fnd-yrbook) |
- This displays on the Giving Hub in CommunitySuite.
|
Notes |
|
- An individual note is created for each instance of the following:
- Notepad.
- Operational Notes (fnd-opnotes).
- Gift Language (fnd-giftlang).
- Spec Handling (Spec-handling).
|
Beneficiaries |
Distributions tab |
|
Closed Funds |
Date Inactive |
|
Grants/Scholarships
Grants
CommunitySuite Field |
FIMS Field |
Notes |
Grant ID |
NA - CommunitySuite unique # |
|
Granting Fund |
Fund ID |
- Fund Name mapped and displayed beside Fund ID in FIMS.
|
Grant Date |
Grant Date |
|
Service Area |
County Code |
- This can be configured for Region Code instead of County Code.
|
Grant Advisor |
Officer |
|
Legacy Code |
Grant Num |
|
Anonymous |
Does Not Migrate |
- User will have to manually mark individual grants as anonymous post go live.
|
Grantee Contact |
Does Not Migrate |
- User will have to manually update or set post go live.
|
Description |
Program Name |
|
Grant Type |
Program Area |
|
Scholarships
CommunitySuite Field |
FIMS Field |
Notes |
Award Date |
Grant Date |
|
Scholarship |
Schol Fund |
- Scholarship fund name mapped and displayed beside Schol Fund code in FIMS.
|
School/Grantee |
Grantee |
- School/Grantee is listed under Recipient Payment section in CommunitySuite.
|
Amount |
Grant Amount |
|
Legacy Code |
Grant Number |
|
Student |
Student |
- Student is listed on the Application Record in FIMS.
|
Donations/Vouchers
Donations
CommunitySuite Field |
FIMS Field |
Notes |
Donor |
Acknowledgment tab on gift: Name, Address 1-2, City,State,Zip |
- Donor field in CommunitySuite includes the preceding FIMS fields under one section.
|
Tribute |
Acknowledgment tab on gift: Under Memorial/Honorarium section - Name |
- Tribute is listed with "in memory of" or "in honor of" preceding name.
|
Amount |
Amount |
|
Fund |
Fund ID |
- Fund Name is mapped and displayed beside Fund ID in FIMS.
|
Donation Date |
Gift Date |
|
Check Number |
Check# |
|
Service Area |
County |
|
Legacy Code |
Gift Number |
|
Custom Message |
Purpose (Perm/Endowed) |
- Purpose is mapped into CommunitySuite as a custom message.
|
Vouchers
CommunitySuite Field |
FIMS Field |
Notes |
Legacy Code |
Voucher Number |
|
Campaigns/Opportunities
Campaigns
CommunitySuite Field |
FIMS Field |
Notes |
Campaign Group |
Gets labeled "FIMS Import" to group all imported data. Does not migrate from a related FIMS Field. |
|
Campaign Description |
Purpose or Source Code and Description from the Additional Detail area on a Gift record. |
- Each purpose or source code is listed as its own campaign within the group.
- Donations that have both a source and purpose codes will only pull in the source code in campaigns.
- Both purpose and source codes are listed in the donation record in CommunitySuite in the Custom Message field.
|
Campaign Date |
N/A |
- This will be the date that the data was imported into CommunitySuite.
|
Invitees |
Profile of the gift that was coded with a purpose or source code. |
|
Opportunities
CommunitySuite Field |
FIMS Field |
Notes |
Opportunity Type |
Purpose Code on Promise record |
- If no purpose code is defined, opportunity type will be "Unknown."
- Default CommunitySuite Opportunity Types (ID numbers 1000-1005) will also show in the Opportunities area.
- No profiles or records will be assigned to these.
|
Stage |
N/A |
- All migrate into stage "New."
- Further setup of stages is done post go live.
|
Created Date |
Promised Date |
|
Target Date |
Promised Date |
|
Solicited Amount |
Amount field on Promise record. |
|
Committed Amount |
Maturity Value |
|
Balance |
N/A |
- This calculates from Solicited amount and any gifts linked to Opportunity record in CommunitySuite.
- It can be done post go live.
|
Fund |
Fund ID on Coding area of Promise record. |
|
Opportunity Note |
Promises Comments |
- Note will also appear on the top level of the CommunitySuite profile.
|