Creating User Migration XMLs Outside H-Sphere

Last modified: 27 Dec 2007

WARNING: This documentation covers Parallels H-Sphere versions up to 3.1. For the latest up-to-date Parallels H-Sphere documentation, please proceed to the official Parallels site.

This document explains how to format user data for migration from third party hosting systems into H-Sphere. Use it to:
- migrate direct end users, resellers, and resellers' end users;
- migrate only direct end users if you don't have resellers.

• Files
• XML Validation

Files

Create the following files:

You may have data for hundreds and thousands of users in the xml file.

Alternatively, You may define DTD definitions directly within the XML file:

    <?xml version="1.0" encoding="utf-8"?>
    <!DOCTYPE users [
        // DTD rules as in users.dtd
        . . .
    ]>
    <users>
    . . .

We recommend defining DTD externally, using our latest DTD:

Warning: If you make a mistake in DTD definitions, migration may fail.

XML Validation

Once you have created the XML, please do the following:

1. Validate the user data xml files with any xml validation software.
2. Make sure the xml file does not contain user with the login "admin".
3. Make sure that mail sections of each user don't contain mail loops.
4. Ensure that the billing period starting date has the MM/DD/YY format.
5. Make sure that in the user tag the value of the login attribute is unique and doesn't begin with a number (this value will be used as the H-Sphere control panel login name).

Now you are ready to create the accounts.