Data – What is Sticky

 

During the initial stage of onboarding, your coach will help you understand your data and assist you in checking migrated data. As you do this, we thought it would be helpful to highlight what data is "sticky" between migrations, and what isn't.

Sticky

All of these are sticky, meaning they are not deleted during future data migrations:

  • Congregations
  • Ministries
  • Programs
  • Accounting Company record
  • Statement Headers
  • Processes
  • Steps
  • Users
  • User Groups
  • Security Roles
  • Group Roles
  • Message Templates
  • Configuration Settings
  • Forms
  • Form Fields
  • Products & Payments
  • Locations
  • Buildings
  • Rooms
  • Room Layouts
  • Equipment
  • Journeys
  • Milestones

However, if you update the Primary Contact on the Ministries, those will not be sticky because they involve using a Contact record and those are not sticky. The Ministry itself will stay. The Primary Contact will be removed.

If you update the Process Manager or Specific User on a Step, those will stick because they are Users, not Contacts. 

Some further caution about editing Programs during your implementation:

  1. When editing Programs, do not set the program’s Primary Contact because that involves the Contact record, and those are not “sticky.”
  2. Programs can be renamed, but not copied or deleted. If they are deleted, they will just reappear after the next migration. Instead of deleting, just enter an End-Date and that will get them off the Current Programs list.
  3. We store the fund name in a hidden field on the Program, so renaming is fine.
  4. Do not merge, combine, or copy any Programs. Actions like copying would cause the record to duplicate because that hidden fund field is copied too. In some situations, we have seen copying a Program, then renaming the copy, cause duplicated donations. Of course, we can clean those, but it's better to avoid them.

Not Sticky

None of these are sticky, meaning they are deleted before future migrations.:

  • Contacts
  • Households
  • Participants
  • Participant Types
  • Groups
  • Events
  • Opportunities
  • Responses
  • Answers
  • Group Rooms
  • Events Groups
  • Selections
  • Messages
  • Publications
  • Contact Relationships
  • Background Checks
  • Form Responses
  • Event Participants
  • Counseling Sessions
  • Counseling Engagements
  • Group Participants
  • Program Groups
  • Suggestions
  • Group Inquiries
  • Group Attributes
  • Group Assessments
  • Donors
  • Donations
  • Donation Distributions
  • Batches
  • Deposits
  • Donor Accounts (MICR)
  • Pledges
  • Event Rooms
  • Event Equipment
  • Event Services
  • Participant Milestones
  • Contact Log
  • Household Care Log
  • Attributes
  • Prayer & Feedback Entries
  • Payments
  • Invoices
  • Addresses

All of the above-listed items will be deleted and reloaded from your legacy data.

There are a few exceptions, the standard contacts we load for you, having contact IDs less than 16 that will not be deleted during migrations. These include ***Default and ***Unassigned as well as the Check-me-in family and the Unassigned Caller

Another thing to note about data migrations

If you delete a record from MP, like a Ministry record, then on future migrations, the scripts will find that record missing and re-load it. If you end-date the record in MP, that will get it out of your Current Ministries view, and the migration scripts will find the end-dated record and not attempt to re-load it. So, end-dating is (almost) always the way to go!