Migrate existing members over about web HOT 3 OPEN

We have also talked about a slower but "easier" migration plan where we send an email to members when their membership expires asking them to sign up to the new service.

This gives folks an opportunity to decide if they want their data in the new system instead of forcing it upon them and then requiring them to ask for it to be removed.

Maybe we can make the migration process easier for people by allowing them to import their data from membermojo - but as membermojo does not have an API I think that would require some form of minimal manual intervention combined with some tooling in the admin back end to interpret the membermojo csv format.

from web.

I don't see any way to accomplish this without a manual step. Membermojo provides a CSV of all members, so while uploading this to the GZ system would be possible it would remove the member opportunity to choose what to do with their data. The only thing I can think of from a customer service perspective would be that the member is provided with a tickbox for "Import my data from membermojo", then Django would only ask for email and payment and we would manually copypasta their data across.

from web.

In my above comment I was thinking of a workflow like this:

1. Member receives their email asking them to renew in the new system and provides them with a link that allows them to import their old data into the new system
2. This link sends an email to a list of people who are authorised to migrate data from membermojo (mainly yourself James I would imagine)
3. Whoever picks up the migration logs into the django admin dashboard where there is a form for migrating users over
4. The person doing the migration uploads the membermojo CSV to the form BUT ensures all other member info is removed. Basically a CSV with one row in it
5. When the member is created they receive an email saying their account has been created with some kind of temp password and a link to login. They login and are forced to change their password.
6. The user is presented with a payment form and is only activated when their payment is setup.

Am i overthinking this? I guess it would only be temporary, but at the same time I think it provides a nice balance between

• Ease of use for the member and the person doing the migration
• The members choice to not move their data to the new system
• Accuracy (no manual data entry)

from web.