Migrating to Exchange

Secondary Files

A secondary file is a collection of one or more sections. Each section contains a description of the data, followed by the actual data. The offset in the primary file specifies the first section in the secondary file for messages with multiple sections.

The following table describes the fields in the header line of secondary files:

Heading Description Values
Type (Required) Type of data. Body, Attachment, Schedule, Document, or Other.
Length (Required) Length of data in bytes, including end-of-line characters. Integer. If message is body part of a free document, the length must = 0.
Encoding Reserved field. Leave blank.
Islast If TRUE, body or attachment is the last in the file for this message. If FALSE, the next section in the file is either body or attachment for this message. TRUE or FALSE.
Name File name of attachment. Required for sections that are attachments and documents, and ignored otherwise.
Position (Optional) Location, in bytes, where icon for attachment should be placed. Valid only for attachments. Default is to the end of the message body. Required for sections that are attachments and ignored otherwise. Must be between -1 and the number of bytes in the body.
Format File format of attachment. None or Macbinary. Defaults to None. Required for sections that are attachments and ignored otherwise.


Body, Attachment, and Other Types

The secondary file can contain data of five different types: Body (message data), Attachment, Other, Document, and Schedule. A message body and its attachments are in separate sections. Sections are separated by blank lines. Example...

This example shows sections of type Body, Attachment, and Other.
Do you want to play a game of racquetball after work tonight?


I saw this short review of Microsoft's BackOffice products.


Microsoft BackOffice package includes Windows NT Server, Microsoft Exchange Server, SQL Server, and System Management Server.


Free Document Type

Secondary files do not have to be associated with messages; documents or files can still be migrated. In the primary file, such files appear as standard messages. In the secondary file, you need to configure the file as follows:

  1. Create a Body entry of length = 0. The subject for this message is ignored.
  2. Set the Islast field to FALSE.
  3. Create a Document section next in the secondary file.

It is very important that the file name in the Document section include an extension. If none exists, add an extension that can launch a viewer application. Example...

Microsoft BackOffice package includes Windows NT Server, Microsoft Exchange Server, SQL Server, and System Management Server.

Schedule Type

Schedule data is moved to the user's mailbox as an attachment to a new mail message. The user opens the message and imports the data by double-clicking the attachment. If the data is not imported automatically when the user logs in the very first time, the user must install Outlook to import the data.

In the primary file, the schedule data appears to be another message in the message section. Example...

In the following example, the third message is the schedule message, which is placed in the Inbox.
,Jeff Smith,John Rodman,,,"End of Month Report",19950321093421,,-1,,,#SALESPO1.SEC(54)
Phoenix Project,Jo Berry,John Rodman,,,BackOffice Review,,,,,,#SALESPO1.SEC(161)
,John Rodman,John Rodman,,,Schedule+,19951005022543,,1,TRUE,,#SALESPO1.SEC(356)

In the secondary file, set the body of the message to a length of 0. The Migration Wizard automatically adds instructions for importing the schedule file in English, German, French, or Japanese, depending on the language of your Microsoft Exchange Server computer. Example...


Note   The first line in the schedule file must be a header line as follows:


Each line thereafter has schedule properties and values.

This section contains the following topic:

Related Topics

Primary Files Formatting the Migration Files