Migration Process for Legacy Clients
Underlined, bold, & italicized steps are automated. All others are manual steps.
-
Client Requests to migrate to Rubex from CSM/CAE
-
CSM/CAE creates amendment/renewal that includes migration from their legacy product to Rubex
-
CSM/CAE close wins an opportunity to migrate to Rubex.
-
A migration order is created on the client's account
-
The client shows on the Professional Services team "to be migrated" report
-
PS team starts testing the migration
-
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
-
EFCO Client: On the migration order, the Account Owner (usually CAE) enters a date into the "Scheduled Date" field and informs the client of that date. Usually, no coordination is necessary as the migration is done in the background without the client present.
-
Growth CAE Manager will follow up with their team regarding scheduling EFCO migrations
-
Desktop/RPC Client: Professional Services team coordinates with the client for a migration date. They enter that date into the "Scheduled Date" field
-
Revenue Operations see the scheduled date on their "daily task" dashboard and provisions a Rubex account
-
Client receives an email to set up their Rubex password from the Hub
-
Professional Services team starts the migration process per the scheduled date/time
-
Professional Services team informs the CAE/CSM and client of the completed migration