Export a configuration
- Last UpdatedDec 12, 2025
- 5 minute read
To export configuration information
-
From the Windows Start menu, expand AVEVA Historian, and then click Configuration Export and Import. The Historian Database Export/Import Utility Wizard displays.

-
Select Export from Historian to a text file.
-
Click Next. The Connect dialog displays.

-
In the Server name box, type the name of the AVEVA Historian for which you want to export configuration information.
-
Provide a login for the Historian.
Select Use Windows authentication to use your Windows logon account to connect to the AVEVA Historian.
Select Use SQL Server authentication to use a SQL Server login. Enter a valid SQL Server username and password.
Important: SQL Server authentication is provided for backward compatibility only. For improved security, we recommend that you use Windows authentication.
-
In the File name box, type the path for the text file to export, or select
and use the file browser to select the file.
-
If you are exporting and want to encode the data as Unicode, select the Save file as Unicode check box. For more information, see Encode formats for configuration exports.
-
To export configuration information for all database entities (for example, tags, engineering units, summary operations, and so on), select Export all objects. Skip to Step 17.
-
Click Next. (If you are exporting a file, and the file already exists at the location, you will be prompted to overwrite it.) The Select Objects dialog displays.

-
In the Data acquisition and miscellaneous group, select one or more groups of definitions to export.
IDAS
An AVEVA Historian Data Acquisition Service (IDAS) is a software application that accepts data values coming from one or more I/O Servers and forwards them to a Historian. For more information, see About IDASs.
I/O servers
An I/O Server is an application that provides data to a client over a network.
Topics
A topic is an application-specific subgroup of data elements. For more information, see I/O server addressing.
System parameters
A system parameter is a numeric or string value used for system configuration. System parameters are stored in the System Parameter table in the AVEVA Historian database. For more information, see SystemParameter in the Historian Database Reference.
Storage locations
The storage location is the directory in which historical data files are stored. Storage locations are stored in the StorageLocation table in the AVEVA Historian database. For more information, see StorageLocation in the Historian Database Reference.
Engineering units
An engineering unit is the unit of measure for an analog tag. For example, RPMs, milliseconds, degrees.
Extended Property Names
The names of the extended properties associated with a tag. For example, Alias, Location.
Messages
Messages are the string values associated with the TRUE (ON) or FALSE (OFF) states of a discrete value.
Snapshot tags
Tags that are defined to have value snapshots saved by the system.
Summary operations
Aggregation calculations that are used to create summary values. See About summary replication.
Summary tags
Tag summaries.
Replication servers
A list of the replication servers that are configured for this instance of the Historian. For information on adding and maintaining replication groups, see Manage and configure replication.
Replication schedules
A list of the replication schedules that are configured for this instance of the Historian.
Extended Property Values
The current stored values of the extended properties associated with a tag.
Replication groups
A list of the replication groups that are configured for this instance of the Historian.
Replication tag entities
A list of the replication tags that are configured for this instance of the Historian. This is the replication configuration for individual tags (simple or summary).
TagHistory
A list of different versions and corresponding configurations, including the unique Tag ID for each version, of the same tag.
Structure Tag
Tags from the StructureType and StructureAttribute tables.
AutoTag
Tags generated by Historian’s auto-summary functionality.
AutoTag History
Tag history.
Saved Content
User-created dashboards and charts from Historian Client Web.
Note: If the DestinationTagId is empty, a new ID will be generated. If you copy a row to create a new tag entity, either leave the column empty or specify a unique ID.
-
To export analog tag definitions, select Include Analog Tags. System tags are not included.
-
In the Where tagname like box, type a string value in order to filter the tags by name. To include all tagnames, leave this option blank or use the wildcard symbol (%). The exporter recognizes all SQL Server wildcard characters. For example, to select all analog tags that have names starting with "MyTag", type "MyTag%".
-
In the Acquisition type list, select the filter for the source of the tag values.
All acquisition types
No filter set. The export file includes all tag definitions (that is, I/O tags, MDAS or HCAL tags, and tags for which values are not acquired).
IOServer only
Select to only include tag definitions that specify an I/O Server as the data source.
Manual only
Select to only include tag definitions that specify MDAS, HCAL, or manual data acquisition as the data source. For example, values from MDAS, HCAL, or Transact-SQL statements.
For more information on acquisition, see Configure data acquisition.
-
In the Storage type list, select the filter for the storage type. The storage type determines how often the value for an analog tag is stored. An analog value can be stored either by time interval (cyclic) or when the value changes (delta).
All storage types
Specifies no filter. Cyclic, delta, and unstored tags are selected for export.
Cyclic only
Only include tag definitions that specify cyclic storage. If you select this option, you can set an additional filter on the storage rate in the Storage rate list. Otherwise, click All storage rates.
Delta only
Only include tag definitions that specify delta storage.
For more information on storage types and rates, see Storage modes in the AVEVA Historian Concepts Guide.
-
Click Next. The Select Objects dialog displays.

-
Configure the filters for discrete, string, and event tag definitions. System tags are not included. These options are the same as for analog tags.
-
Click Next. The Confirm dialog displays.

-
Click Next to start the export. The Status dialog box appears, showing the results of the export. The number of objects exported is reported.

-
Click Finish to exit the wizard.