Import Data
The Import Wizard loads records into Alloy Navigator from a text file, an Excel workbook, or another database. Depending on the options you choose, it creates new records, updates existing ones, or both. You can save the wizard's settings as a reusable import profile and run the import again with that profile, including unattended.
The Import Wizard is one of the five Windows tools of the Administrative Tools package that the Alloy Navigator Cloud installer names; see Administering Alloy Navigator Cloud.
In the Import Wizard
Before you begin
- To sign in to the wizard interactively, you need the Administrator right. Without it, the wizard shows "You do not have enough permissions to use this function.", the sign-in fails, and the list of importable objects is not loaded. This check does not apply to an unattended run.
- For an unattended run, you need a Database Access Key stored on the
computer, under
HKEY_LOCAL_MACHINE\Software\Alloy Software\Access Keys\<name>, and a saved import profile. A Database Access Key is imported in the Access Key Import dialog, from an access key file (.reg) with Load from File... or by pasting the key into its text box.
Start the wizard
Start the Import Wizard in one of these ways:
- In the Alloy Control Panel, open the Import entry. The Control Panel
lists Import when
ImportWizard.exeis present in the installation. - From the Start menu, open Alloy Software > Alloy Navigator 2026 > Tools > Import.
- Run
ImportWizard.exefrom theBinfolder of the installation folder. On a default installation, the path isC:\Program Files\Alloy Software\Alloy Navigator\Bin\ImportWizard.exe.
The wizard signs you in first. It then runs through a fixed sequence of pages; the source type and the object class you choose decide which pages appear.
Choose an import mode
On the Import Mode page, choose Set up a new import or Use a previously saved import configuration.
For a saved configuration, enter the profile file in Select
Configuration, or use the button beside the box to browse for an .ipf
file, and then click Next. The box is available only while Use a
previously saved import configuration is chosen. Next is available
once the box holds a file name. The wizard reads the file when you click
Next and, when the configuration loads, goes straight to the Ready to
Import page.
Choose what to import
On the Destination Objects page, pick the entry to import from the Object Class list. The list is sorted alphabetically, and the first entry is preselected. Your license decides which entries appear: an entry that needs the ITAM or ITSM license module is listed only when the license includes that module or is a FULL license.
| License module | Entries |
|---|---|
| ITAM | Assets, Computers, Configurations, Consumables, Contracts, Documents, Equipment Lending Library, Equipment Reservations, Hardware, Networks, Products, Purchase Order Items, Purchase Orders, Software Catalog, Software Licenses, Stock Rooms, Stock Rules, Tracked Software, Vendor Products, Vendors |
| ITSM | Activities, Change Requests, Closure Codes, Incidents, Knowledge Base Articles, Problems, Project Tasks, Projects, Service Catalog Items, Service Requests, Services, SLA, Work Orders |
| None | Announcements, Brands, Categories, Classification Attributes, Company Addresses, Groups, Locations, Organizations, Persons, Relationship Types, Statuses, Types |
For Categories, Classification Attributes, Types, Statuses, and Closure Codes, the Lookup Options page follows. It reads "Please select kind of lookup"; for Types, Statuses, and Closure Codes it reads "Select the Object Class for importing Types." (or Statuses, or Closure Codes). In its Object Class list, choose what the imported values belong to:
- Types, Statuses, and Closure Codes: the object class the values apply to. Closure codes can be imported for Work Order, Incident, Problem, Change Request, and Service Request.
- Categories: the object class the category tree belongs to; four ticket classes also offer a separate "<Class> Activity" entry.
- Classification Attributes: one of eight lists - Ticket Impact, Ticket Priority, Ticket Urgency, Titles, Software Platforms, E-mail Types, Budgets, or Ticket Medium.
Choose the data source
On the Data Source Type page, choose Excel Workbook, Text File, or Database (ADO connection). The next pages depend on this choice:
- Data Source File (Excel Workbook or Text File): enter the file in
File Name. The browse dialog offers
.csvand.txtfiles for a text file and.xlsand.xlsxfiles for a workbook. Next refuses a blank name with 'The "File Name" field is mandatory, it can't be left blank.' and a missing file with "File '<name>' not exists." - Source Text Options (Text File only): the Field delimiter (Comma delimiter, Semicolon delimiter, Tab delimiter, or Space delimiter), the Text Qualifier (double quote, single quote, or None), and the Record Separator (CRLF, CR, or LF). A change on this page makes the Field Mapping page reload its preview.
- Source Data Formats (Excel Workbook or Text File): Date Order (MDY,
DMY, or YMD), Date Delimiter, Time Delimiter, Decimal Symbol,
Four Digit Years, and Leading Zeros in Dates. A delimiter box left
blank is not applied. These settings do not apply to a database source.
Before a value is written into a date or time field, the wizard reads it
with its general date and time format, not with the settings on this
page; a value that does not read as a date but reads as a number is still
accepted. The wizard does not check that the dates in a file are
formatted consistently. A saved configuration that lacks a value of this
page or of Source Text Options loads MDY,
/as the date delimiter,:as the time delimiter,.as the decimal symbol, Four Digit Years and Leading Zeros in Dates clear, CRLF, the double quote, and the semicolon delimiter. - Data Source Database (Database): Connection String and Table
are mandatory.
- Enter a connection string or use the button beside Connection String to choose a data-link file or build a connection string.
- Authentication offers Windows Authentication or SQL Server
Authentication and follows the connection string whenever the string
changes: it is Windows Authentication when the string's
Integrated Securityvalue istrue,yes, orsspi. Login and Password are available only for SQL Server Authentication. When a changed string resolves to SQL Server Authentication, its user ID and password are copied into these boxes. - Table becomes available once a connection string is entered and lists the source's tables when you open it. Changing the connection string clears Table.
- The run connects with the Authentication choice: Windows Authentication adds integrated security to the connection string, and SQL Server Authentication removes it and uses Login and Password.
The table list is built when you open Table while its list is empty. With SQL Server Authentication, a blank Login is refused first with the mandatory-field message. If the connection fails when the table list is built, the wizard shows the provider's message. For SQL Server Authentication it adds "Verify that the username and password are correct." and 'To automatically use the password from your ADO connection string, select "Allow saving password" in the "Data Link Properties" dialog box.'
Connect to a database source
After choosing Database (ADO connection) as the source type:
- On Data Source Database, click the button beside Connection String to open Build Connection String.
- Choose how to specify the connection:
- To use an existing
.udlfile, select Use Data Link File and click Browse.... In Select Data Link File, select the file. - To build a connection string, select Use Connection String and click Build.... Configure the source database connection in Data Link Properties, and click OK.
- To use an existing
- Click OK in Build Connection String to return to the wizard.
A changed connection string replaces the field and clears Table.
A data-link file appears as
FILE NAME=<path>. - Check Authentication. For SQL Server Authentication, check or enter Login and Password.
- Open Table and select the source table. Click Next to map its fields.
Map fields
The Field Mapping page pairs destination fields with input columns.
- To map one field, choose its Input Column. To unmap it, press Backspace in the Input Column cell. The Input Column list always offers every source column and marks the columns that are already mapped.
- You can also right-click a column of the Preview and pick the destination field from the menu, which marks the fields that are already mapped. The menu's Default Mapping clears every mapping and then maps each destination field whose caption equals a source column name, reading underscores in the column name as spaces.
- One input column can feed more than one destination field.
- Field Type shows each destination field's data type.
- Only fields with Mapped selected are imported. Blank source rows are skipped.
The Legend shows a required field in bold and a field that links to another record in italic. When you leave the page, the wizard checks, for most classes, that the key fields are mapped and otherwise shows 'Invalid mapping. The "%s" field is mandatory. Please specify a mapping for this field.'
For a file source, the page offers First row contains field names. The Preview shows the first 20 records of a text file (21 when the first row is not a header); all records of the source are imported. For a database source, the Preview shows a single row.
Drag the bar between the Preview and the mapping grid to resize the preview; the preview and the grid each keep a minimum height. Clicking the bar's grip hides the preview, and clicking it again restores the preview at its earlier height. The size is not kept: the page opens with the preview at its original height each time you start the wizard.
The grid does not offer system fields such as record IDs, links stored as IDs, and created and modified stamps. Binary fields are offered only for a database source. When you map a user-defined lookup field, a value that is not yet in its list is added to the list.
Match keys
For most classes, each row is matched to an existing record by a key that depends on the object class, and a blank key fails the row.
| Object class | Matched by |
|---|---|
| Most classes | The class's key field, which the Field Mapping page requires |
| Contracts | The title and the contract number together; the Field Mapping page requires both |
| Relationship Types | The name and the inverse name together (both required) |
| Software products | The product name and the version together; a blank version is its own match group |
| Types, Statuses, Closure Codes | The imported value together with the object class chosen on Lookup Options |
| Categories | A backslash path, resolved within the object class chosen on Lookup Options |
| Locations, Organizations | A backslash path in the required Placement field |
| Projects | A backslash path in the required name field |
| Computers, Hardware, Software Licenses | Name, Asset Tag, Barcode, or Serial Number, whichever you select on Import Options |
| Persons | A person-matching lookup built from up to three source fields: the full name, the login and domain in the primary login, and the primary email |
| Project Tasks | The task's external OID; the mapped parent object must also resolve to an existing Project or Task. The Field Mapping page requires both the OID and the parent object |
| Stock Rooms | The name alone |
When a mapped workspace value is available, the wizard matches it by name to an existing workspace. An unknown name does not create a workspace or change the record's workspace.
For Locations, Organizations, Projects, and Categories, the key is a path with one backslash-separated segment per level of the tree. For Locations, Organizations, and Projects:
- A doubled backslash stands for one backslash inside a name.
- Each level is looked up by name under the level before it, starting at the top level.
- A missing level is created only when the class's own create option is selected (Create new Locations, Create new Organizations, or Create new Projects), and a level created this way counts as a created record; otherwise the next level is looked up among the top-level entries.
- The last segment is the record's own name.
The Locations grid offers no Parent field. For Organizations, a value mapped to a Parent field is not used; the placement comes only from Placement.
For Computers, Hardware, and Software Licenses, a match field is available only when its field is mapped. When the selected one becomes unavailable, the selection moves to the next available one in the order Barcode, Serial Number, Asset Tag, Name.
For Persons, a new person is created only when no existing person matches. When the mapped manager equals the row's own full name, the person becomes their own manager. When the primary email is mapped and not yet recorded for the person, it is added and made the primary email; an email that already exists is left unchanged, even when it is not the primary one, and older emails are never deleted. This happens only when the row creates or updates the person.
Some classes are not matched on a key of their own and only add records:
- Activities: the mapped request field holds the OID of an existing record, and every row is added to it as a new activity. An activity is never updated. A Request value that does not resolve fails the row. The entry has no create or update option for the activity itself, only allow-create options for its category and its person.
- Knowledge Base Articles: every row is added as a new article, filed under a category named "Import", which is created if it does not exist. A mapped category is ignored. The entry has no create or update option for the article itself, only allow-create options for its person, status, and type.
- Company Addresses: every row is added as new, whether or not the create option is selected.
- Purchase Order Items: every row whose purchase order resolves by its number is added as a new item, so importing the same line again adds a duplicate. A blank purchase order fails the row; one that does not resolve skips the row with no error.
- Equipment Reservations and Vendor Products: every row is added as new. A reservation looks up its library item and its requester by name, a vendor product its vendor and its product; when either lookup is empty, the row is skipped with no error.
For Purchase Order Items, Equipment Reservations, and Vendor Products, the create option is always selected and cannot be cleared, and these imports never update a record.
A Project Task row whose parent object does not resolve is skipped with no error.
Set import options
The Import Options page ("Set import options.") shows the options of the class you import. Set All selects every option and Clear All clears every option.
- The create and update options, such as Create new Locations or Update lookup, decide what happens to each row. An unmatched row is added only when the create option is selected. A matched row is updated when the update option is selected, or when the record was created earlier in the same run. For Categories and Classification Attributes, these options are Create lookup and Update lookup; for Closure Codes, Create new Closure Codes and Update existing Closure Codes.
- An allow-create option for a referenced field, such as Category, Type, Status, Location, Organization, Vendor, Product, Manufacturer, Stock Room, or Unit of Measure, lets the wizard create a missing referenced record during the import.
- A person that the wizard creates for a ticket's Assignee, a group's manager, one person field each of Announcements, Knowledge Base Articles, Locations, Organizations, and Vendors, or a technician-type user-defined field is created as a technician. Such a person is looked up by full name, and a person that is found is left unchanged.
- The five ticket classes (Work Order, Incident, Problem, Change Request, and Service Request) resolve fourteen referenced fields: Assignee, Requester, Assignee Group, Category, Closure Code, Impact, Organization, Priority, Project, Status, Type, Urgency, Medium, and Service Name. All five classes offer the same allow-create options, and Assignee and Requester share one. A missing service is never created.
If neither the create option nor the update option is selected, the wizard asks "You did not select creation or updating of %s. Continue?" when you leave the page. For Categories and Closure Codes, the message names Classification Attributes instead of the entry you import.
The import does not apply object templates to the records it creates.
The Types and Statuses entries have no Import Options page. A Stock Rooms import looks up no referenced fields and offers no allow-create options.
Handle import errors
The Error Processing page ("Check the box to ignore errors during import.") holds one box, Ignore all errors.
- With the box clear, each row error shows its message and "Do you want to ignore this error?" For most classes, the message of a row error gives the row's key after "Source Key:". The underlying message follows a line "SQL Server replied:", except for an error that does not come from SQL Server, such as a blank required field. A value that does not convert to its destination field's type shows "Error while importing the data from Input Column into Destination Field." with the column, value, field, and type. Yes ignores this error, Yes to All ignores every further error in the run, and Cancel or No stops the run.
- With the box selected, the wizard does not ask.
A value that does not convert is dropped from the row whether or not the wizard asks. Every error adds to the Error Count statistic and is written to the System Log while the wizard is connected, and to the log file when one is given (see Run an import unattended). The choice is saved with the import profile.
Save and run the import
- On the Ready to Import page, click Save Configuration to save the
current settings as an import profile (
.ipf). The file name offered isAlloyImportProfile.ipf, or the name of the configuration you loaded on Import Mode. The profile stores the object class, the source type, the settings of the data source and data format pages, the options, the error choice, the mapped fields, and the database login and password, encrypted. - Click Next to start the import. Back and Next become unavailable. The Importing External Data page reads "Preparing data..." while the source is read and "Importing data..." while records are imported. Its Process statistics show Total records, Records processed, Time elapsed, Time remaining, and Errors encountered, refreshed at most once a second.
- To stop the import, click Cancel and confirm "The Import is currently importing data. Cancel the process?" with Yes. The run stops at the next row.
- On the Import Completed page, review the Statistics grid, and then click Finish to close the wizard. The page reads "The data from <file> file was imported into <class> records.", with "<table> database table" in place of the file for a database source, and "Review the import statistics and click Finish to close the wizard." Back and Cancel are not available on this page, and Finish closes the wizard without asking for confirmation.
The Statistics grid lists every statistic of the class you imported, zero counts included: the source record count, the error count, and a created and an updated count for the class and for each referenced object the import can create. For an Excel source whose first row contains field names, the source record count leaves out that row. The run also writes "Errors: n", "Total records: n", and "Import finished" to its log. If the run stops on an unexpected error, the wizard shows "Import canceled. Error: <message>" and moves to Import Completed.
Workflow during an import
Most classes save their records through workflow, so business-rule workflow items fire during the import; see Workflow Overview. These entries save records directly, without firing business-rule workflow items: Equipment Reservations, Vendor Products, Relationship Types, Stock Rooms, Brands, Company Addresses, Activities, Categories, Classification Attributes, Types, Statuses, and Closure Codes. The import of software products, matched by product name and version, also saves directly. An import of Equipment Reservations, Vendor Products, Relationship Types, software products, or Stock Rooms also leaves no row in the workflow log.
Run an import unattended
To run a saved profile without the wizard's pages, run ImportWizard.exe
with these switches. Switch names are not case-sensitive. Start the wizard
with /? or /Help to see the Import Command-Line Options window, which
lists all of them except the older /DB=.
/AccessKey="<key name>"and/Profile="<file name>": both are needed. The run is unattended only when the access key resolves to a stored key and the profile is not blank; a profile without an access key opens the wizard interactively./Server="<server>"and/Database="<database>"(or the older/DB=): optional. They replace the server and the database of the access key for this run. The run still signs in with the login, password, and authentication mode stored in the access key./Log_File="<file name>": optional. The wizard adds each message at the end of the file, as a line with the date, time, level (FATAL,ERROR,WARNING,INFO, orDEBUG), and message, and the file can be read while the import runs. When the file cannot be opened for writing, for example because it does not exist yet, the wizard creates it, which empties a file that already exists. The text is written as UTF-16 without a byte order mark. An interactive session started with/Log_Filewrites to the same file.
An unattended run logs in, loads the profile, and runs with no pages,
reporting only to the log. It never shows the error prompt. If neither the
create option nor the update option is selected, it writes a fatal line to
the log and fails. An unmapped required field is written to the log as a
fatal line. A data source that the wizard refuses is logged, and the wizard
closes. FATAL and
ERROR messages also go to the System Log while the connection is open.
Changes that an unattended run makes are recorded under the reserved Import
service identity, not under a technician.
Import logs in the Settings App
The Settings App's log browsers are described in Logs. A log browser that is not read-only offers Clear All, which clears the log in addition to the daily purge. A tool log browser opened for one job's log clears only that job's records; opened for the tool's log, it clears the tool's records. Settings... opens the retention settings. It is not shown when the log is read-only or when the browser shows one job's records, and a user without the right to manage logs sees "You do not have enough permissions to use this function." instead of the settings. A tool's own retention setting overrides the general one, which ships as 30 days, so changing one tool's retention does not change the others. The logs of the three AI tools fall back to 7 days instead of the general setting.