Using the M3 DMP Migration Tool

The migration process starts with the M3 DMP Migration Tool. This tool performs the conversion of existing OP databases to ensure compatibility with M3 DMP MT services.

Before migrating, verify that these tasks are met:

  • Ensure all users sign out of the system
  • Back up the existing OP database
  • Locate and copy the DmpServer.ini filename from the currently installed OP M3 DMP service
  • Verify the DmpServer.ini configuration. Open the file in a text editor and ensure it contains these variablescwith corresponding values:
    • DBPREFIX
    • LPSSQLVersion
    • LPSSQLADMIN
    • LPSSQLCENTRAL
Note: The migration process is required one time. The database update requires less than 10 minutes and does not cause downtime.
  1. Open the M3Dmp On-Prem to Migration Tool.
  2. In Upload Dmp Server .ini file, specify this information:
    Select File
    Select the configuration file. Browse to select the verified DmpServer.ini filename.
  3. In Provision Database SQL Paths, specify this information:
    DB Name
    Specify a name for the new provision database. The database stores connection information and credentials, replacing the traditional .ini file usage.
    DB Data
    Specify the file path for the provision database Data (.mdf) files.
    DB Log
    Specify the file path for the provision database Log (.ldf) files..
    Note: If the provision database already exists in the SQL Database Instance, the values in DB Data, DBLog, and Connection String are ignored. This can happen if the process is repeated.
  4. In Connection, select Enter Connection Details or Enter Connection String.
  5. If Enter Connection Details is selected, specify this information:
    Instance
    Specify the instance hosting the provision database.
    Login
    Specify the user account.
    Password
    Specify the password.
    Port
    Specify the port used.
  6. If Connection String is selected, specify the SQL Server connection string with a user account that has sufficient privileges to create databases.
  7. Click Test Connection to verify SQL Server access. Ensure that the connection is successful before proceeding.
  8. Once all inputs are validated, click Migrate to start the migration process.

    If the migration completes without issues, a success message is displayed.

    If errors occur, click Show Logs to review the details and troubleshoot..