Install data model CiviCRM extensions #680

The old contacts data used extensions to provide additional data fields. These extensions should be installed before importing the data so that the data linked to those fields can be preserved.

The following tasks should be done prior to the data import (#586):

• Determine which extensions the old data used
• Install the prerequisite extensions
• Create a list of configuration settings to apply before data import
• Apply pre-import configuration settings

assigned to @altsalt

changed title from Install data model extensions to Install data model {+CiviCRM +}extensions

@ramereth / @detjensrobert Is the old CiviCRM instance (volunteer.snowdrift.coop) still available? The url seems to be timing out. We're about to import the old data to the new instance and it would be helpful to log in and check the data fields and extensions used by the dataset. Thanks!

We don't manage that host -- volunteer.s.c doesn't point at us. Is this one of your old AWS instances?

@detjensrobert You're right — it's still pointing to an AWS IP. Would it be possible to redirect the volunteer.s.c subdomain to https://contacts.snowdrift.coop/volunteer? It's put in maintenance mode at the moment, but will be a volunteer form there when it's back.

If it's too much trouble, then please remove the volunteer.s.c record, so it's no longer pointing to unknown infrastructure. Thanks!

We have the redirect prepped and will let you know once it has been deployed.

@iko The DNS change and redirect have been deployed!

Thanks @detjensrobert!

The 2015年11月23日 and 2016年02月25日 dumps had these civi modules:

• org.civicrm.volunteer
• eu.tttp.noverwrite
• biz.jmaconsulting.search.anyteloremail
• org.woolman.genderselfidentify

I did not see any other extensions, components, add-ons, etc. that looked to be added by us.

marked the checklist item Determine which extensions the old data used as completed

I should add that we are likely not going to use any of these add-ons moving forward and that I've gone through the data and confirmed that we aren't obviously losing any data from entries, as they were mostly unused.

marked the checklist item Install the prerequisite extensions as completed

After quite a bit of fiddling, I have not found a good way of diffing the old configuration settings and the new ones, aside from visually spinning up two instances. Given this, I'm suggesting that we call it good and change settings as needed moving forward.

One last thing to check before closing this issue, whether enabling/disabling a component impacts entries in a not-easy-to-back-out-way.

Related to #588