Chapter 9
Migrating from Digital ALL-IN-1

To migrate users from your Digital ALL-IN-1 version 2.3 or later, you need to install the source extractor. The source extractor copies data to migration files. Data that is copied to migration files includes mail messages, mail attachments, shared folders, events, personal distribution lists, and pending deferred mail.
You import these files by using the Migration Wizard, a tool included in Microsoft Exchange Server.

Microsoft Exchange Server Host Migration Tools
Support and Services 
Microsoft Exchange Server Host Migration tools assist in migrating from the following host-based messaging systems to Microsoft Exchange Server:
	IBM PROFS/OfficeVision
	Digital ALL-IN-1
	Verimation MEMO

These comprehensive tools provide host administrators with a means of migrating users’ accounts, private e-mail messages, shared information, attachments, documents, calendar data, and personal address data to Microsoft Exchange Server.

Important
The PROFS/OV, ALL-IN-1 and MEMO host source extractors are not supported through standard Microsoft Product Support Services, such as the Premier Support Plan.

To receive support and customization services around these tools, host administrators have the following options:
Microsoft Consulting Services 
Microsoft Consulting Services is providing services to assist in migrating to Microsoft Exchange Server. 
Independent Consultants and Software Vendors 
A number of independent software vendors and consultants provide fee-for-service and products to assist you in your migration planning, implementation, and customization. For contact information and descriptions of migration services and products offered, see the sections that follow. Also see the Microsoft Exchange Server home page (http://www.microsoft.com/exchange) for an up-to-date listing of Microsoft Exchange Server-compatible products and services.
Self-support/Customization 
Included with host migration are tools and documentation that enable you to manage your migration. The source code for each tool is provided to enable your system programmers, solution providers, or system integrators to support and tailor the tools to your specific needs.
Attachmate Corporation
Attachmate Corporation offers SupportWare for Zip!Office connectivity products and Migration Consulting Services. 
Attachmate SupportWare
Provides multilevel customer support offering specialized assistance on MAPI-to-host connectivity products including ZIP! Office Connector for PROFS, ZIP! Office Connector for SNADS, and ZIP! Office Client Connection. Services include toll-free customer support directly to engineers.
Attachmate Consulting Services
Provide a wide variety of custom programming or installation assistance on any of our program products or utilities that assist customers with migration or coexistence strategies concerning Microsoft Exchange Server and IBM hosts. Services include a quick-start program, contract programming, migration assistance, and coexistence consulting.
Attachmate Corporation
3617 131st Avenue, SE
Bellevue, WA 98006
Phone: 800-426-6283 or 206-644-4010
http://www.attachmate.com/
Digital Systems Integration Enterprise Messaging Services
Digital Systems Integration has a worldwide professional force of enterprise messaging and workgroup computing professionals. With a closely coordinated network of more than 450 experts around the world, many of them certified Microsoft Solution Developers, Digital can support the most demanding requirements of enterprise messaging networks.
MS-Exchange Planning Service
Designed for the customer who has committed to the implementation of the Microsoft Exchange Server as an enterprise-wide messaging infrastructure and wants to migrate from or integrate with an existing messaging infrastructure.
MS-Exchange Startup Pilot
Designed for the customer who wants to evaluate a practical implementation of Microsoft Exchange Server.
MS-Exchange Integration and Migration Service
Provides the customer with a working messaging handling system based on Microsoft Exchange Servers and clients. Installation, configuration, testing, roll-out project management, and training are delivered to customer locations around the world. The service addresses coexistence between legacy enterprise mail (office automation) systems and Microsoft Exchange Server, as well as migration from Digital’s ALL-IN-1, IBM PROFS, HP-Desk, and other legacy e-mail systems, including directory integration, administration, and management.
Americas
    Digital Systems Integration
    Enterprise Messaging Manager
    6404 Ivy Lane., M/S COP 1-7/9
    Greenbelt, MD, USA, 20770-1443
    Phone: 301-918-7732
    E-mail: Enterprise.Messaging@cop.mts.dec.com	
Europe
    Digital Systems Integration
    Business Development Manager
    BP 027 
    06901 Sophia Antipolis, France
    Phone: +33 92 95 54 85
    E-mail: Enterprise.Messaging@vbo.mts.dec.com	
Asia/Pacific
    Digital Systems Integration
    Consulting Manager
    139 Frome Street
    Adelaide, SA 5000, Australia
    Phone: +61 (8) 235-7242
    E-mail: Enterprise.Messaging@ado.mts.dec.com	

Icom Solutions Ltd.
Icom Solutions has worked with over 500 of the world’s largest organizations to design, build, and customize automated office and workflow solutions. Icom Solutions offers strategic and technical assistance and the full range of systems integration expertise to help the corporate organization define and realize migration strategies from high-cost, low-function host systems to lower cost, high-function client/server systems.
Icom offers specialized and off-the-shelf solutions to address migration to Microsoft Exchange Server from: Verimation MEMO, OfficeVision/MVS, OfficeVision/VM, OfficeVision/400, Fischer TAO, CA Email, DISOSS Library, and Lotus Notes and cc:Mail.
Icom Solutions provides a comprehensive migration service that covers the key issues in achieving a successful move. Business consultants help construct the business case for making the move to Microsoft Exchange Server to ensure the right level of sponsorship within an organization. Consultants can make a clear assessment of the starting point of the migration and define the optimum target architecture. Specialist planning services help organizations to plan and prioritize the transfer of users and applications and address the areas of internal skills development.
Technical consultants provide a wide range of specialist networking and systems integration skills to assist throughout the process.
Icom Solutions Ltd.
PO Box 1240 
Witton
Birmingham
U.K. B6 7UH
Phone: +44 (0) 121 356 8383
Fax: +44 (0) 121 356 0463
Microsoft Consulting Services
Microsoft Exchange Planning Service
For large organizations moving to Microsoft Exchange Server, Microsoft Consulting Services (MCS) provide a focused planning service that evaluates the customer’s current messaging and network infrastructure in light of their business objectives. Based on that evaluation, MCS produces a preliminary Microsoft Exchange Server design, highlights key technical and migration issues unique to the customer, and provides recommendations for testing, piloting, and migration resources.
In addition to the planning service, MCS can assist organizations with every aspect of their move to Microsoft Exchange Server, from piloting through deployment. With an emphasis on knowledge transfer, the MCS staff works closely with the customer’s technical staff and third-parties to ensure a successful migration to Microsoft Exchange Server.
To find out more about Microsoft Exchange Server Migration Consulting Services, contact your Microsoft account representative, or call (800) 426-9400. In Canada, call Microsoft Canada at (905) 568-0434. Outside the United States or Canada, contact your local Microsoft office.
SysTEAMus Corporation
SysTEAMus Corporation is a software engineering firm that specializes in the design, development, and implementation of client/server systems, electronic messaging applications, and Digital ALL-IN-1 systems.
SysTEAMus Exchange Migration Service is specially tailored to assist organizations in integrating with or making the transition from Digital ALL-IN-1 to Microsoft Exchange Server. The service includes the necessary up-front planning to ensure a smooth transition. Additionally, it is flexible and can be adjusted in scope to accommodate any size organization as either a supplement to internal staff or as a “we do it all” engagement. Services include migration of ALL-IN-1 applications to Visual Basic.
SysTEAMus Corporation
Suite #2800
6855 Jimmy Carter Blvd.
Norcross, GA 30071
Phone:   (770) 417-1251
Fax:       (770) 417-1909
Before Migrating
You need to perform a number of tasks before migrating. First, update your client hardware as needed. Also, set up your Microsoft Exchange Server site. For information about these two tasks, see the Microsoft Exchange Server Concepts and Planning Guide and the Microsoft Exchange Server Installation Guide.
Have users delete documents they don't need, retrieve any archived documents, or move documents to a special folder. Archived documents are not migrated.
You also need to synchronize directories beforehand. There are three methods: using the Directory Import and Directory Export commands in Microsoft Exchange Server, using Digital’s Directory Synchoronization Utility, or using a third-party program.
Digital ALL-IN-1 accounts are limited to 30 characters, whereas Microsoft Windows NT accounts are limited to 20 characters. If you are creating Windows NT accounts with the Migration Wizard and you have lengthy Digital ALL-IN-1 account names, you must either edit the migration files or modify the names of the Digital ALL-IN-1 accounts to 20 characters or less prior to migration.
If doing a multi-phase migration, you need to connect Digital ALL-IN-1 and Microsoft Exchange Server. The following gateways can be used:
X.400 with Digital’s MRX and Message Router to ALL-IN-1  Connects to native X.400 connectors in Microsoft Exchange Server; supports 1984 standards only.
X.400 with Digital’s MAILbus® 400  Connects to native connectors in Microsoft Exchange Server; supports 1988 standards.
SMTP with Digital’s MAILbus 400  Connects to the Internet Mail Connector in Microsoft Exchange Server; supports MIME.
Theory of Operation
The ALL-IN-1 Source Extractor must be used from the EX_MIGRATE account on the ALL-IN-1 system. This is a special account that must be created for the purpose of migrating user accounts. Whether the user names to be processed are chosen in the user interface, or via an input file, the processing is identical:
	1.	The first/next user is determined.
	2.	That user's account is visited.
	3.	Any required directory processing and name validation is performed.
	4.	Any documents that match the selection criteria are emitted to the output file(s).
	5.	Any event items that match the selection criteria are emitted to the output files as Inbox messages.
	6.	Any nicknames that match the selection criteria are emitted to the output files as Inbox messages. Any errors are noted in the log file.
	7.	Unless that was the last selected user, the process repeats.
The attribute mapping between ALL-IN-1 and Microsoft Exchange Server is as follows:
Exchange 	ALL-IN-1	ALL-IN-1 Field Name	
Common-Name	Username	USER	
Display-Name	Full Name	FULNAM	
Target-Address	Username	USER	
Start-Time	Start Time	STIME	
End-Time	End Time	ETIME	
Location	Location	LOC	
Description	Purpose	DESC	
Private	Confidential	CONFID	
Tentative	N/A	N/A	
Reminder	N/A	N/A	
Rem-Time	N/A	N/A	
Attendees	Attendee	ATENDE	
Note	Comments	N/A	
Folder	Folder	FOLDER	
Sender	Sender	FROM	
To	To	TO	
Cc	CC	CC	
Bcc	BCC	BCC (available in V3.0 and later)	
Subject	Subject	SUBJECT	
Send-Date	Date Sent	DELIVERED	
Received-Date	Date Sent	DELIVERED	
Priority	Importance	PRIORITY	
Unread	Status	emitted	
Unsent	Status	emitted	
Body	File Name	emitted	

International Issues
The ALL-IN-1 Source Extractor was developed in English with an effort to be easily translatable to any other (Single Byte Character Set) language that has an ALL-IN-1 language version. The use of imbedded visible character strings in code has been avoided in most cases. To translate this tool to a different language, the following steps are necessary:
	1.	Translate the visible portion of the ALL-IN-1 forms (.FLG files).
	2.	Scan the script files (.SCP) for imbedded text and translate as necessary.
Language-specific character sets are handled via language-specific terminals and printers rather than through the use of selectable code pages. The ALL-IN-1 system only sees ASCII values. The rendering of these values into visual form is accomplished entirely via the ROMs in the users’ terminals and printers. While the Source Extractor will specify code page 850 in the intermediate files, it is there as a convention and has no bearing on the terminal ROMs in use at any particular site.
Converting System Distribution Lists
Before you convert distribution lists, make sure you have converted user accounts to custom recipients (for information, see the Microsoft Exchange Server Administrator’s Guide). Then, perform the following steps:
	1.	Print the distribution lists to a file.
	2.	Use the Digital ALL-IN-1 system manager account to create a list of system distribution lists.
	3.	Use the Directory Export command in the Microsoft Exchange Server Administrator program to export a list of custom recipients.
	4.	In the list of distribution lists, replace all the account names with the directory or common names from the custom recipient export list.
	5.	Convert the list of distribution lists to directory import format (for information, see Chapter 3 in this guide, or see the Microsoft Exchange Server Administrator’s Guide.
	6.	For nested distribution lists, take the data from the common-name field of each group and replace the common-name of the Digital ALL-IN-1 distribution list’s custom recipient in the members field of all the distribution lists.
	7.	Import the file by using the Directory Import command in the Microsoft Exchange Server Administrator program.
	8.	Delete all system distribution lists in Digital ALL-IN-1 after directory synchronization occurs. If you delete them before the Microsoft Exchange Server distribution lists propagate to the Digital ALL-IN-1 directory, your users will be unable to send messages to the distribution lists.

Digital ALL-IN-1 users that have been added to the address list can use Microsoft Exchange Server distribution lists.
During migration, you might have to update the distribution lists as you delete custom recipients and replace them with mailboxes. If you have configured custom recipients to be replaced by mailboxes (as described in Chapter 2), you can avoid this extra task.
Converting Information for Migration
The source extractor has special ways of migrating nickname lists, some personal data, and WPS-PLUS, DX, or Mass-11 documents.
Nickname Lists
The source extractor copies the nickname files for each account to a message, which is migrated into the users’ Microsoft Exchange Server Inbox folder. The user can therefore create personal address book entries for each of the nicknames.
Personal Data
To-do lists, reminders, and calendar access information aren’t migrated. Before migrating mailboxes, have users print this information to a text document that is being migrated. After migration, they can re-enter these items into Schedule Plus.
Dictionaries are not migrated. Depending on the word processor used in your installation of Digital ALL-IN-1, it might be possible to print the personal dictionary file to a file, and migrate it as a text attachment or message. In Microsoft Exchange Server, users can forward it to themselves with the spell checker turned on. Every word that is misspelled can be added to the new personal dictionary file.
Auto-Reply and Auto-Forward settings are not migrated. The user must create new rules, using the features of Microsoft Exchange Server. 
WPS-PLUS, DX and Mass-11 Documents
Digital ALL-IN-1 supports non-ASCII mail messages, but Microsoft Exchange Server does not. In addition, WPS-PLUS and Mass-11 documents typically are not supported on personal computers. The source extractor converts these documents and mail messages as it migrates them.
The source extractor converts:
	All WPS-PLUS, Mass-11, and DX documents and attachments to ASCII.
	All mail messages created with the VMS version of WordPerfect to ASCII.
	All non-ASCII mail messages into attachments in the intermediate files and inserts a short text message describing the attachment.
The next section explains alternatives to the default translation action.
Document Conversion
You can use third-party converters for Digital ALL-IN-1 and personal computer viewers to avoid the loss of document attributes that result from ASCII conversions. Your options include:
	Before the migration, convert the documents into attachments, and convert the attachments into a compatible format. For example, word processing documents can be converted into Word, RTF, or WordPerfect® format, depending on what word processing program you are using on the personal computer.
	Modify the EX_ATTS.SCP and EX_DOCS.SCP scripts to call a 3rd party converter as part of the migration. For more information, see the comment at the end of the EX_DOCS.SCP script.
	Convert the documents to attachments, which are migrated in their native format, and provide the users with PC viewer or converter software that recognizes the Digital ALL-IN-1 formats.

On Digital ALL-IN-1, you can use tools such as Digital’s Compound Document Architecture Converter Library or Keypack® from FTP Software, Inc. for document conversion. On the personal computer, you can use several viewers and converters. An example of a converter for WPS-PLUS documents is Word for Word® for Windows from Mastersoft.
If a document is of a type known to ALL-IN-1, it keeps the original file extension and indicates the format with the attribute data. However, if the document is of unknown type, the document is given the file extension of “FGN” and is tagged as “FOREIGN” in its attributes. The source extractor does not convert any attachments other than on WPS-PLUS, Mass-11 and DX files. Attachments with an extension of FGN that are migrated to Microsoft Exchange Server will appear as plain documents, until the user associates the FGN extension with an application.
Preventing Server Overload
Both Digital ALL-IN-1 and Microsoft Exchange Server use single-instance storage for mail messages — one message addressed to multiple recipients on a server is stored once. However, when users’ documents are extracted for migration, each user has a personal copy of each document in the migration files. As a result, more disk space may be required for Microsoft Exchange Server than for Digital ALL-IN-1. 
There are several strategies for preventing the volume of migrated materials from overloading Microsoft Exchange Server, as shown in the following table.
Strategy	When	Advantages	
			
Empty wastebaskets on folders in user accounts.	A few days before migration.	Deleted documents aren’t migrated.	
Have users clean up their folders before migration.	A few weeks in advance, with additional reminders as time to migrate gets closer.	Only users delete mail. 	
Limit migration to a recent date range.	During the extraction process.	Old documents, including mail in special folders, aren’t migrated.	
Limit migration to inbox and one special folder.	During the extraction process.	Allows users to put old documents they need in a folder to be migrated. The date range, if used, is applied to both folders. 	
Migrate accounts only; allow users to forward valuable items to their new mailbox.	During the extraction process, and before the old accounts are removed.	Allows users to migrate valuable data, and speeds the migration process for the administrator.	
Migrate accounts only, without migrating file cabinet contents.	During the extraction process.	Users start afresh with Microsoft Exchange Server.	

In all these strategies, it is important to let users know which documents are being moved.
Extracting Information from Digital ALL-IN-1
This section describes how to install the Digital ALL-IN-1 Source Extractor on a Digital ALL-IN-1 system. 
Prerequisites
You need the following software and hardware:
	Digital ALL-IN-1, version 2.2 or later (local language version). This source extractor runs within ALL-IN-1, which runs under the VMS (or OpenVMS) operating system. Any version of VMS that is supported by ALL-IN-1 is supported (typically V5.4 or greater).
	Enough free disk space to create a migration account and build the intermediate migration files. These files require an amount of disk space roughly equal to the combined sizes of all documents to be migrated in a given session. These files could require hundreds of megabytes of disk space, depending on your system and users.
	The EX_MIGRATE account must have the XOWN (ALL-IN-1) privilege in order to execute the migration scripts and access the forms library. 
Note that the tools can be used to migrate most customized Digital ALL-IN-1 systems unless standard Digital ALL-IN-1 functions have been altered.
Installing the Extractor
The source extractor is made up of ALL-IN-1 script files and forms. They can be found on the Microsoft Exchange Server CD in the \MIGRATE\TOOLS\HOST\ALL-IN-1 directory. The following procedure explains how to install the extractor:
1.	Create a Digital ALL-IN-1 account called EX_MIGRATE with a very high or no disk quota.
2.	Using SYS$SYSTEM:AUTHORIZE.EXE, give this account READALL and SYSPRIV privileges (both Authorized and Default) in addition to typical user privileges.
3.	In the ALL-IN-1 profile for EX_MIGRATE:
	Specify EDT as the default editor.
	Include EXFORMS as a default form library.
	Include EX_MENU as the initial form.
4.	Copy all files from the Microsoft Exchange Server Migration Tools directory into the ALL‑IN‑1 directory of the EX_MIGRATE account (typically [EX_MIGRATE.A1] or [EX_MIGRATE.OA]). You can use any file transfer program to copy the files, as long as they are copied in text mode.
5.	From the EX_MIGRATE ALL-IN-1 directory (at the $ prompt), type:
@EX_INST
This command builds the EXFORMS forms library and renames files.
	6.	If there were errors, correct the condition suggested by the error message and retype the @EX_INST command.

Guidelines for Using the Source Extractor
This section covers the guidelines you should follow in order to use the source extractor most efficiently.
Limiting Batch Size
Process users in small batches. The allowable number is difficult to predict due to the number of variables involved. Start with batches of 100 or fewer users. If you are using Digital ALL-IN-1 version 2.3, start with batches of 50.

Note
The source extractor can’t process more than 950 users per batch.

Reprocessing Users
If you select a user who has already been migrated, the source extractor processes the user again and logs when the previous process occurred. Use the comments in the script file EX_BUILD.SCP to alter the script to ignore already-processed users’ accounts. The comment is:
!!! Insert a .GOTO USERS_LOOP here to avoid re-processing a user

Running Multiple Instances of the Source Extractor
You can run multiple instances of the source extractor concurrently, provided that you’re not trying to process the same user at the same time. 
	1.	Log onto the EX_MIGRATE account at multiple terminals (or in multiple terminal windows).
	2.	For the second and subsequent runs, use the /REENTER qualifier when starting Digital ALL-IN-1.

Migrating Systems Without DECnet™ and Message Router
The source extractor is set up for systems that are running DECnet™ and Message Router, and has the associated logical names defined. If your system is not running these programs, the system mailbox name defaults to A1, and the node name defaults to THEVAX. 
To override the defaults manually, assign the following values to permanent symbols:
<GET $EX_NODE = “local choice of node name”
<GET $EX_MAILBX = “local choice of mailbox name”
<GET $EX_SUFFIX = “ @A2 @OURSYS” 

where A2 represents $EX_MAILBX, and OURSYS represents $EX_NODE
Creating Migration Files
The following migration files are created.There is one primary and one secondary file for each account.
File	Description	
		
mmddhhmm.PKL	Packing list file  —  Names all files in a batch.	
mmddhhmm.PRI	Primary intermediate file  —  Lists accounts processed and secondary files.	
mmddhhmm.LOG	Log file  —  Shows running status of a migration batch.	
mmddhhmm.nnn	Secondary file  —  Contents for a given account.	

Note
mmddhhmm is based on the month, day, hour, and minute that the EX_MENU command was invoked, and nnn is a sequentially assigned number starting with 001.

Extracting Information
The following procedure explains how to extract information.

Caution
Make sure that users you’re migrating aren’t using ALL-IN-1. Otherwise, files may be locked.

	1.	Log onto the EX_MIGRATE account to start an ALL-IN-1 session.
	2.	If the EX_MIGRATE account doesn’t start with the source extractor menu, enter the invisible command EX_MENU to access it. 
	3.	Choose the MIG option to bring up the migration options screen. Specify the desired parameters.

Microsoft Exchange Server Migration Source Extractor for ALL-IN-1
Migration Batch Name:        ________     Program generated (MMDDHHMM)
Accounts or Control File:    _________________________________  Optional
Create Mailbox List?:            _ (Y/N)
Create Nickname Document?:       _ (Y/N)
Include Documents?:              _ (Y/N)
Restrict To One Folder:    ______________________________  (Folder Name)
Earliest Document Date:      ___________  (MM/DD/YY or DD-Mmm-YYYY)
Latest Document Date:        ___________  (MM/DD/YY or DD-Mmm-YYYY)
Include Calendar Items?:        _ (Y/N)
Earliest Calendar Item Date: ___________  (MM/DD/YY or DD-Mmm-YYYY)
Latest Calendar Item Date:   ___________  (MM/DD/YY or DD-Mmm-YYYY)

Migration Batch Name
This field is automatically generated, based on the date and time when the EX_MENU command was invoked, or the last time a migration process finished since entering the menu. If a number has already been assigned, the number is incremented by 1 until a unique number is found and assigned. This number is the basis for all file naming for the migration batch: it is the file name for the primary file, all secondary files, the packing list file, the log file, and the temporary work files used during the process.
Accounts and Control File
Use this field to specify an Accounts or Control File. The file must be an existing VMS file in the same directory as the source extractor. You can only specify one of these fields; they are mutually exclusive. The extractor looks at the first line of the file to determine if it is a valid user name, in which case the file is treated as an accounts file. Otherwise, the extractor considers the file to be a control file.
A control file specifies the name and path of a related accounts file, and any parameters. All other input on this screen is ignored. The parameters specified in the control file or default values are used. 
The following tags are supported in control files for the Digital ALL-IN-1 extractor: Accounts, Mailbox, Email, Schedule, EmailStart, EmailEnd, SchedStart, SchedEnd, and Folder. The Folder tag is for the Restrict to One Folder option. For more details on control files, see Appendix C.
The tags PAB, File, Public, Logfile, and Loglevel are not supported.
If you do not specify an accounts or control file, specify the parameters on this form. Leave a field blank to specify the default value. The next screen is an account selection form. Select the accounts to process in this batch.
Create Mailbox List
This field can have a value of Y or N (this is automatically localized for foreign systems). Choose Y to create a directory section in the primary file, which is used to create mailboxes in Microsoft Exchange Server. Choose N to omit the directory section.
Create Nicknames Document
This Y or N field specifies whether to convert each user’s nickname file to a mail message and migrate it into their Inbox on the Microsoft Exchange Server. An example of the message created by this process follows.
Nicknames from your ALL-IN-1 account:
KAber	Kim Abercrombie	
Steve	SAlboucq @SMTP @FAB	
JamesA	JALLARD @A1 @HUBNTH	

Include Documents Field
This Y or N field specifies whether to process the users’ Digital ALL-IN-1 file cabinets. Choose Y to process the users’ mail messages, word-processing documents, and personal distribution lists for migration. Choose N to omit this processing.
Restrict to One Folder
Use this field to specify one folder to process from each user’s Digital ALL-IN-1 file cabinet. The folder must be created in the Main drawer. Only documents that meet the other selection criteria (date range and not a dictionary) are processed. If the folder does not exist, only INBOX documents are processed for that user. If this field is blank, all eligible documents in the users’ file cabinets are processed. The users’ INBOX folder is processed regardless of this field. 
Earliest and Latest Document Date 
Use these fields to specify a date range of documents to process. These fields are only evaluated if the Include Documents Field contains a Y. If you do not want to filter documents by date, specify a very old early date and a future latest date. Entries such as TODAY, YESTERDAY, TOMORROW, EOM, TODAY -3Y, and TODAY +30D are correctly interpreted.
Include Calendar Items
Use this field to specify whether to process users’ ALL-IN-1 events. Choose Y to format the users’ event data in Schedule+ import form and place it into the intermediate files for migration. Choose N to omit the users’ events from processing.
Earliest and Latest Calendar Item Date
Use these fields to specify a date range filter for processing event data. These fields are handled in the same manner as the Earliest and Latest Document Date Fields.
	If you select nickname processing, a document containing the user’s nicknames is created and placed into the migration files. It will be imported to the user’s Inbox on the Microsoft Exchange Server.
	If you select calendar information, the source extractor creates a document in Schedule Plus Import format from each user’s ALL-IN-1 events that match the criteria specified in the parameters. The Schedule Plus Import format data is appended to the Intermediate Files.
	4.	Do one of the following:
	If a control file exists, type the name of the control file and the parameters in the Control or Accounts file field.
	If an accounts file exists, type the name of the accounts file in the Control or Accounts file field.
	If neither file exists, leave the Control or Accounts field blank. 
	5.	If you do not specify an Accounts or Control file, the source extractor displays a User Index screen. You select the accounts to process from this list.
		Use the arrow keys to move the pointer to the desired account, and then press the Select key. 
		– or –
		Type line numbers and ranges, and then press the Select key.
	6.	To continue choosing, type xw.
		To begin processing, type ex.

Note
Depending on the number of accounts selected and the size of the affected file cabinets, the MIG option could take several hours to complete.

	7.	Review the log file by selecting the Log menu. The log file lists each user processed and any errors. You can also use the Log menu to get the file names used for the current batch of processed users. The log file uses the same naming convention with .LOG as the file type.
	8.	Transport the migration files to the Microsoft Exchange Server in binary mode for input to the Migration Wizard.
		
Your next step is to import the migration files by using the Migration Wizard. For more information, see Chapter 2, “Using the Migration Wizard,” or online Help for the Migration Wizard.
Post-Migration Tasks
After a mailbox is migrated, the user needs to perform a few tasks.
Pending Deferred Mail
Pending deferred mail is migrated to the user’s Microsoft Exchange Client Inbox folder. Because the Microsoft Exchange Client does not have an equivalent feature, the users need to send the mail.
Personal Distribution Lists 
Personal distribution lists are migrated as a mail message in the user’s Distribution Lists folder. Each message has a subject that matches the name of the personal distribution list, and a body that contains all the members’ names. Users may need to update the addresses as they are entered to the personal address book.
Shared Folders
Users need to “re-share” their shared folders on the Microsoft Exchange Server by dragging the folders to the appropriate location in the public folder hierarchy. As the administrator, you should have a plan for public folders and permissions in place. You also need to let users know where they can move the folders after migration. An informational message is migrated that lists all access permissions for shared folders so that they can reestablish similar sharing afterward.
Personal Folders
All drawers become personal folders. All folders in drawers are created as subfolders of the migrated drawer folders. For example, folder REVIEWS in drawer PERSONAL is migrated as folder REVIEWS in the folder PERSONAL.

BLANK PAGE
IMPORTANT: This text will appear on screen, but will not print on a PostScript printer.
This page should be the last one in this file; it was inserted by running the InsertBlankPage macro.
Do not type any additional text on this page!