-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate existing members over #31
Comments
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. |
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. |
In my above comment I was thinking of a workflow like this:
Am i overthinking this? I guess it would only be temporary, but at the same time I think it provides a nice balance between
|
Impact
High
Urgency
Later
The text was updated successfully, but these errors were encountered: