Preparing to use the Migration Assistant

For a successful migration, we recommend taking some measures to prepare your systems to avoid difficult-to-solve problems that could lead to migration failure.
To prepare your systems for migration:
  1. Install RICOH ProcessDirector on the target system.
    1. Verify that your system meets the prerequisites.
    2. Follow the installation instructions just as you would for a new installation.
    3. Return to this procedure after you complete the process to install the base product.
    4. Log in to the version of RICOH ProcessDirector that you just installed. Use the User Name aiw and the Password aiw.

      When you change the password for this user, remember the new password. We recommend logging in as this user until the migration process is complete and all users are imported to the target system.

    5. Install the same features that you had on your old system and any new features that you have purchased. If an error occurs during the installation, contact Ricoh Software Support.

      For more information, see Installing features and Installing RICOH Transform features.

    6. Download and install license keys. RICOH ProcessDirector and all features install in trial mode. If the trial period expires before you install license keys, the software stops working.

      Note: You can install license keys after the migration process is complete if you prefer.
  2. If you use the Reports feature, review Planning for Reports database migration. Before you start the Migration Assistant, consider these items:
    • Whether you want to continue using the existing Reports database or create a new one for the target system.
    • If you want to create a new database, what instance of PostgreSQL to use, an instance installed with RICOH ProcessDirector or one installed separately.
    • If you are creating a new database for the target system, whether you want to migrate your existing data.

    If you plan to create a new Reports database on the target system and migrate your existing data into it:

    1. Log in to the source system and enable all the data collectors whose data you want to migrate.
    2. Create the new database. Log in to the target system and open Administration ⇒ Reports ⇒ Database settings. Review and update the settings, then enable data capture. The database table is created automatically if everything is configured correctly.
      Note: This step is required if you use a PostgreSQL instance installed outside of RICOH ProcessDirector.
  3. If you are using the Preprinted Forms Replacement feature, export the media.zip file from your target system and copy it to the source system. Follow the instructions for Exporting media with electronic forms.
  4. When you import step resources, the files that they refer to are not included in the export package. Copy the files referenced in the step resources from the source system to the target system manually. You must copy the files to the target system before you start the Migration Assistant.
    1. To import all the step resources, copy the contents of /aiw/aiw1/StepResources from the source system into the same directory on the target system.
    2. To import specific step resources, open the XML file that you exported. Find the entry for each step resource that you exported and locate the StepResource.File property. In that value, find the name of the RSC file associated with that step resource. For example, in this value:
      <property name="StepResource.File" value="{&quot;fileName&quot; : 
&quot;/aiw/aiw1/StepResources/
1992052c6ef44a229b8b43d77232bf53.rsc1992052c6ef44a229b8b43d77232bf53.rsc
&quot; , &quot,&quot;displayName&quot; : &quot;
Ricoh_Export-2019-08-26_13-30-04.xml&quot;}"/>

      The file name is: 1992052c6ef44a229b8b43d77232bf53.rsc

    3. Find the file on the source system and copy it into the same directory on the target system.
  5. The Migration Assistant cannot migrate SSH Key credentials.
    Private Key credentials cannot be exported, because they must be created on the system where they are used. Objects that use private key credentials fail in the Migration Assistant and must be recreated manually afterwards.
  6. Prevent common issues that can result in migration failure:
    1. Take a snapshot or backup of both the source and target systems to avoid the risk of data loss.
        Note:
      • Using Migration Assistant to upgrade on a different computer does not affect the source system, preserving the data and configuration. We recommend backing up both systems as a safety measure.
    2. Make sure that the Product Update features are installed on both systems at the same level. In the Feature Manager, find the Product Update feature for both systems and compare the values in the Installed Version column.
        Note:
      • If the target system has a higher version, you have the opportunity to download the package during the migration. Then you can install the Product Update using Import Package on the source system Feature Manager page.
      • If the source system has a higher version, find the most recent product update package in: /opt/infoprint/ippd/available. The name of the package is: ProductUpdate-3.4.version_number.epk. Download the package, then log in to the target system. Open Feature Manager, import the package, then install it.

        For more information, see Adding or upgrading a feature using Import Package.

    3. Check file system capacity. For a successful migration, the target system should have at least as much available capacity as the source system.
    4. Verify that antivirus or other security software that locks and scans files is still disabled on the target system.

      Verify that exceptions for these paths are defined in your antivirus software:

      • /aiw/aiw1
      • /opt/infoprint/ippd
      • /var/psf
      • If you use DB2 installed with RICOH ProcessDirector as your database:
        • /home/aiwinst/sqllib
      • If you use PostgreSQL installed in a Docker or Podman container as your database:
        • /var/lib
      • If you use a custom feature that integrates BCC software running on a Windows application server with RICOH ProcessDirector, exclude this path on the Windows system that the BCC software runs on:
        • C:\BCC
Parent topic: Using the Migration Assistant