Data migration of an existing Microsoft Windows CMS to a new Insight Software 6.3 system

Cluster CMS with remote database example
mximport –f <File Name> –p <password> –v <Cluster CMS IP> -n <Cluster CMS
Name> -r <true>
For example, mximport –f c:\export.zip –p somepassword –v {IP address} –n
hpcluster –r true
Non-Cluster CMS example
mximport –f <File Name> –p <password>
For example, mximport –f c:\export.zip –p somepassword
In both examples, the export archive file is read from the root directory of the C: drive and is called
export.zip. Since the password was provided, the user is not prompted for the password.
1. Sign in to the source CMS with operating system-level administrative privileges. Be sure this is the
same user who installed the Insight Software.
2. Open a command prompt:
a. Navigate to Start menuRun.
b. Type cmd, and then click OK. The command prompt window appears.
3. In the command prompt window, execute the import command:
mximport
4. A prompt for a Data encryption password appears. Type the password and press Enter. The password
does not appear in clear text.
IMPORTANT:
The password provided must be identical to the one used when the export utility
was run, otherwise the exported file cannot be read.
5. A dialog appears stating Is Database Remote(y/n)? Type Y and press Enter, otherwise type N and press
Enter.
If the database is remote, you are prompted to confirm whether the prerequisite configuration steps
have been followed for remote database access. Type Y if you have performed the steps, or type N if
you have not performed the steps. If you type N, follow the prerequisite steps in Step 2: Configuring
remote database access for the import operation to the target CMS, and then start the import operation
again.
6. A warning message displays indicating that the import wipes out all data from the database. Enter Y to
continue the import process, or enter N to terminate the import process.
Note:
The import process clears the data on the target system and database before it
actually imports any data into the target CMS.
Figure 2: Console output of import tool operation
C:\>mximport -f Products.zip
:-:-:-:-:-:-:-:-:-::-:-:-:-:-:-:-:-:-::-:-:-:-:-:-:-:-:-::-:-:-:-:-:-:-:-
:-::-:-
:-:-:-:-:-:-:-: