Migration Process for Legacy Clients

Underlined, bold, & italicized steps are automated. All others are manual steps.

1. Client Requests to migrate to Rubex from CSM/CAE

2. CSM/CAE creates amendment/renewal that includes migration from their legacy product to Rubex

3. CSM/CAE close wins an opportunity to migrate to Rubex.

4. A migration order is created on the client's account

5. The client shows on the Professional Services team "to be migrated" report

6. PS team starts testing the migration

7. Upon complete and successful test, the Account Owner receives an automated chatter in SFDC informing them of the completed test and prompts to set up a migration date with client

8. EFCO Client: On the migration order, the Account Owner (usually CAE) enters a date into the "Scheduled Date" field

9. Growth CAE Manager will follow up with their team regarding scheduling EFCO migrations

10. Desktop/RPC Client: Professional Services team coordinates with the client for a migration date. They enter that date into the "Scheduled Date" field

11. Revenue Operations see the scheduled date on their "daily task" dashboard and provisions a Rubex account

12. Client receives an email to set up their Rubex password from the Hub

13. Professional Services team starts the migration process per the scheduled date/time

14. Professional Services team informs the CAE/CSM and client of the completed migration