The transition from one platform to another should be well thought out and should not take place too frequently. However, the trigger is usually the emergence of one or more significant problems with the existing system. Sometimes this is quite clearly indicated by the need for additional functionality, significant changes in the marketplace, or the loss of a service partner. In other cases, it is more of a gradual process, for example, when the workload of regular tasks scales proportionally in parallel with user and vehicle numbers, or when the service structure becomes increasingly difficult to map.
This is followed by troubleshooting, analysis and research into internal and external solutions and opportunities for improvement. Often this phase concludes with the realization that it would be a good idea to start with an external partner or to change the external partner.
Migration always follows the same principle and consists of four steps.
MOQO receives data as an export and views the contents and elements of the database as well as their quality. Possible discrepancies between the data types of the inventory system and the MOQO platform are identified and discussed.
MOQO checks how the migration works from a technical point of view. For example, a data exchange via an interface or the export from the inventory system via a suitable file format.
The migration is simulated in a test environment, the success is checked by MOQO as well as by the sharing provider and readjusted if necessary. It is important to have successfully completed this process before the actual launch.
After successful preparation, the final data migration to the MOQO platform takes place. The sharing provider supports its drivers with an account activation link to the MOQO platform.