The import is designed for In-link version 2.3.4, however it will work, or partially work, for most of the older In-link2 versions up to 2.0.10. If you have one of the older In-link2 versions and are experiencing problems, please upgrade your In-link2 to the version 2.3.4, and then run this import.

In this step, the administrator will need to designate the options of the import – how the In-link2 data is supposed to be integrated into In-portal and In-link3.

• Administrative Group – this field designates the In-portal administrative group (by default, ‘Admin'), into which the old In-link2 administrators should be imported. You can choose a different group for the import, and then designate the administrative users later. Clicking on the group button will pop up a list of In-portal groups.
• Regular User Group - this field designates the In-portal group (by default, ‘Members'), into which the old In-link2 users (link owners) should be imported. It is recommended to import then into a group that will give them access to the front-end, and to modify their links. However, you can choose a different group for the import, and then manage the users later. Clicking on the group button will pop up a list of In-portal groups.
• Initial Import Category – this field designates the In-portal category, which will serve as a root for the In-link2 import. This category will be the equivalent of the Home category in In-link2, and all of the sub-categories will be created underneath. Clicking on the category button (folder icon) will pop up a catalog navigator, where you can select the category.
• Link Image Name – this field designates the link image field in the In-link2 database, which was used to store the link image name. By default, it is ‘link_image' , however many users have used a custom field for this purpose, in which case you should enter the custom field name here.