Humanitru/ACME Workflow

IF ACME GIVES THE CLIENT A SANDBOX ACME ACCOUNT

1. Migrate data from old CRM into Alpine including memberships (Sprint)

2. Customer responsible for sending ACME membership data from their old CRM

3. Database Fixes if necessary (Sprint)

4. Connect ACME Integration (Sandbox). Humanitru monitors to make sure it’s matching correctly.
   a. Create Jira ticket (high priority) to add to sprint so dev can connect ACME on a local environment, make it sync, and then inspect the result of that; if it’s okay, then the dev will connect ACME on the production environment and mark done, if not, they will make adjustments to the data / probably the migration needs some fixing

5. Final Pull of Data into Alpine (Sprint), and then switch the ACME integration to connect to Production (EoD after Final Pull)

IF ACME DOES NOT GIVE THE CLIENT A SANDBOX ACME ACCOUNT

1. Migrate data from old CRM into Alpine including memberships (Sprint)

2. Customer responsible for sending ACME membership data from their old CRM

3. Database Fixes if necessary (Sprint)

4. Connect ACME Integration (Production). Humanitru monitors to make sure it’s matching correctly.
   a. Create Jira ticket (high priority) to add to sprint so dev can connect ACME on a local environment, make it sync, and then inspect the result of that; if it’s okay, then the dev will connect ACME on the production environment and mark done, if not, they will make adjustments to the data / probably the migration needs some fixing

5. Final Pull of Data into Alpine (Sprint)