Data Migration Plan

Each of these big buckets has sub-data that should also be imported. An example is the CRM bucket. An admin would need to import the basic information of a CRM before he/she can import addresses, phone numbers, record types, etc. that need to be associated with CRM records.

An import will always begin with the CRM since most of the data in SiteStacker are traced back to a CRM record. Below is a brief description of what these big buckets are mostly used for and why it is imported.

IMPORTANT!: Before importing data into Site Stacker, make sure that all the System Messages are disabled to avoid sending email notifications to the Site Stacker users.

CRM

CRM is used to import contacts, donors, sponsors, admins, missionaries, etc. This consists of the First Name, Middle Name, Last Name, External ID (ID from an outside source), Email, Addresses, Phone numbers, Record Types, and Entities, which is custom data that is associated with any CRM Record. This helps the admin track contacts and their information.

Users

This import is for the admin to assign temporary passwords to CRM records so that these Users can have access to the login from the front-side of the website. This is also used if the admin wishes to give Users deeper access to the system.

Website Content (Missionaries / Projects / Datagroups)

This import is done to bulk import content into the website. An example of this import is importing the Missionaries' bio page or Projects/Campaigns into Site Stacker.

• Importing Missionaries
• Importing Projects
• Importing Tags & Tagging Content

Children

This import is for child sponsorship projects. Although children are imported into SiteStacker as CRM records, there are additional processes that differ from the basic CRM record that need to be followed for successful importing.

Historic Giving

Historic Giving is imported from a client’s Donor Management System (DMS). There are two main reasons why we import the Historic Giving data manually:

1. If the client is migrating out of their current DMS and will use Site Stacker to be their DMS
2. If the client has a DMS and wants to import both their Online and Offline gifts from their DMS into Site Stacker to reflect a more accurate data to their user. If the reason is number 2, the process usually looks like this:
   
   

Importing Tips

• DO NOT change the number in the import file template (ex. 01 Person.csv) as the number in the file name is used by SiteStacker to map the Data Import.

• Save the Import file in a UTF-8 file format.

• When you upload an import file, it will let you know if the file has been uploaded successfully or unsuccessfully.
  • If the file has been successfully uploaded, you can right-click on it and click ‘Run Import’ to actually run the import.
  • If the import was unsuccessful, you can check the errors by right clicking on the upload and click ‘Show Errors’.