지금 지원 담당자와 채팅
지원 담당자와 채팅

Migrator for Notes to Exchange 4.16.3 - Pre-Migration Planning Guide

About the Migrator for Notes to Exchange documentation Introduction Critical considerations Other strategic planning issues Appendix A: Known limitations of the migration process

Directory export limitations

•
Directory catalogs are not exported. The Directory Export Wizard does not export Notes directory catalogs.
•
Dynamic members of auto-populated groups do not migrate. The Directory Export Wizard exports only the manager member of a Notes auto-populated (dynamic) group and not the dynamic members.

Issues migrating from pre-Notes 7 environments

The following limitations apply when migrating from a version of Notes earlier than Notes 7.

•
Some RTF formats in pre-Notes 7 environments do not migrate. The following Notes RTF formats (versions before Notes 7) do not migrate to Exchange because Microsoft Outlook does not offer any equivalent format: Shadow, Emboss, Superscript, Subscript, Extrude, and Highlighted text.
•
Bullets in bulleted lists (within an email) do not migrate from pre-Notes 7 environments. The list text migrates, in list form, but the bullet characters that precede each item in a bulleted list do not migrate.
•
Embedded Excel tables sometimes do not migrate in pre-Notes 7 environments. Excel tables embedded within a Notes message (before Notes 7 only) sometimes do not migrate. This problem is intermittent and occurs only with embedded tables (copied and pasted into the body of a message)—not to tables that are attached to messages.
•
Fonts lost from rich text in migrated calendar data from pre-Notes 7 environments. The font in the RTF body of a calendar item will maintain most of its formatting, but the font type is lost during conversion from Notes (prior to version 7) to Outlook.
•
Table colors and borders are not migrated from Notes clients prior to version 7. The data is migrated, but the formatting is limited without colors or borders.

Other non- or partial migration issues

•
The Highlighted text RTF format does not migrate from Notes 7 or higher. Other RTF formats, however, do migrate from Notes 7 or higher.
•
Archives on CD-ROM cannot be migrated. An attempt to migrate a user archive from a CD-ROM will generate this error:
ERROR: [4648-33-114-00000102]
Issue in determining design class of 'D:\nameswes.nsf'
NSFDbOpen: Cannot write or create file (file or disk is read-only)
User archive NSF files can be migrated from a hard drive via the file system, but cannot be migrated from a CD-ROM. If you want to migrate an archive on a CD-ROM, copy the NSF file to the migration server hard drive and migrate via the file system.
•
Page breaks, sections, horizontal rules, and computed text within a message do not migrate.
•
Image resources do not migrate: Image resources (inserted in a Notes message by Create|Image Resource) do not migrate.
•
OLE attachments do not migrate. But an OLE object can be migrated when embedded within the body of a message.
•
Notes rules do not migrate. Notes mail rules, which let individual users tell Notes how to process their incoming messages, do not migrate to Exchange except for out-of-the-office rules.
•
Outlook reminder pop-ups appear for migrated but unprocessed meetings that occurred in the past. Outlook displays its pop-up meeting reminder dialog box for a migrated meeting that is scheduled for a date/time in the past if the meeting was unprocessed when it was migrated. In this scenario, Outlook also adds the unprocessed meeting to the user's calendar, and marks it as tentative. This is native Outlook/ Exchange behavior.
•
Broadcast meetings are migrated as regular meetings. The Notes feature Do Not Receive Responses From Invitees, which makes a meeting invitation "broadcast-only," does not migrate to Exchange.
•
Cancelled meeting instances do not migrate. Migrator for Notes to Exchange does not migrate cancelled meeting instances, even though Notes may retain them.
•
ACL for disabled Notes user may migrate due to latency: A propagation delay in Notes may cause the ACL for a disabled Notes user to inadvertently be migrated when the migration occurs soon after the user is disabled. In this case the user will appear with a cryptic name such as NT- User: S-1-5-21-12354667. When the user is re-enabled in AD, after some propagation delay, the user will appear normally in the Outlook ACL.
•
Notes tasks that are not started and overdue in Notes migrate to Exchange as not started, but are not designated as overdue. This is due to a known limitation of Outlook.
•
A stationery folder migrates, but stationery is migrated as mail.
•
Stationery dates do not migrate. When Notes stationery is migrated to Exchange, the date associated with the stationery becomes the day-and-time of migration.
•
Signature templates do not migrate: The Data Migration Wizard and SSDM migrate signatures that occur in messages, as parts of the messages, but do not migrate Notes signature templates. End users who want to use automatic signatures in Outlook will have to create them in Outlook after they have been migrated.
•
Message recall-ability does not migrate: A message originating in Notes and migrated to Exchange/Outlook cannot be recalled from the Exchange/Outlook environment.
•
The prevent-copying attribute of a message in Notes is not preserved upon migration. The message itself is migrated, however.
•
Request update messages are not migrated. A Notes user who has been invited to a meeting or assigned a task can request information—a feature that sends a special Notes message back to the originator. These "request update" messages do not migrate.
•
Attachments to contacts do not migrate.
•
Custom alert text assigned to a Notes reminder is not migrated. A Notes user can create a calendar entry (a meeting, reminder, or so forth), and in the Remind Me feature may create or edit a customized message to be displayed with the reminder. When you migrate this data, the text is lost because there is no comparable feature in Outlook.
•
A contact's briefcase items do not migrate. The briefcase folder of a personal contact may contain attachments and comments, but the contents of the briefcase folder do not migrate.
•
Customized field labels in Notes PAB entries do not migrate. Any contents of such a field will migrate, to whatever field in Exchange corresponds to the original field label in Notes, but the customized label does not migrate.
•
Dates of draft items do not migrate. A draft item (no content in To, From, Subject, body) will migrate from Notes to Exchange, but the date associated with the draft becomes the day-and-time of migration.
•
Table borders do not appear in some target client platforms. The table borders of tables that appeared normally in the Notes source do not appear when migrated to some versions or OWA (Outlook Web Access) and Android. Tables appear normally, however, with their borders, in Outlook 2010 and most other target client platforms.
•
Meeting updates are not supported between Notes and Outlook in some cases. When a recurrence pattern for a series of meetings is supported in Notes but not supported in Outlook, and when the organizer OR attendee, but not both, has been migrated, some updates/cancelations/responses for single occurrences will not work.
•
"Private" meeting created in DWA isn't private after migration: The "private" status of a meeting created in Domino Web Access is not preserved upon migration. Migration does, however, preserve the "private" status of a meeting that was created by a local Notes client.
•
Meeting invitee tracking is not accurate in some cases after migration to Exchange: If a meeting is scheduled in Notes and a Notes invitee accepts the invitation after migration to Exchange, invitee tracking is not accurate in Exchange. There will be two entries, one that is correct, and one that is not. The one that is not will say "no response".
•
ACLs: ACLs can only be added for groups on mail folders if the group is a security group.
•
Display name of migrated rooms: After the calendar of a room resource is migrated to Exchange, and forwarding is set from Notes to Exchange, if you book the resource in Notes, the name of the room can appear to be changed. Due to the forwarding and a limitation on the way Notes parses addresses, the room will be referred by the left-hand side of the forwarding address and not the canonical name.
•
All migrated bullets look the same on ANSI Japanese systems: On ANSI Japanese systems, the Notes RTF exporter exports any bullet character as a Unicode • "BULLET", so all bullet characters in migrated messages appear the same, regardless of their appearance in Notes. (Migrator for Notes to Exchange uses Notes to export RTF from messages.)
•
Recurrence Rules: Some recurrence rules that conform to the iCalendar specification in Domino Notes are not properly migrated if they are not supported in Microsoft Exchange. For example, monthly recurring meetings with multiple dates or days are converted to weekly recurring meeting because Exchange does not support monthly recurrence with multiple dates or days.

Other Data Migration Wizard issues

•
Exchange provides no tracking info for invitation received in Notes but accepted post-migration in Exchange. Notes is unable to associate an accepted meeting invitation with a meeting organized in Notes, if the invitation was originally received in Notes, but not accepted until the recipient had migrated to Exchange.
•
Message subjects truncated: Messages with subjects longer than 4096 characters cause MNE to stop processing a mailbox at that message. MNE truncates longer subjects to 4096 characters. Meanwhile, Outlook truncates any message subject longer than 255 characters to 255 characters. A message subject longer than 4096 characters is truncated twice during migration: once by MNE to 4096 characters, and again by Outlook to 255 characters.
•
Duplicate messages from multiple Notes locations: MNE does not filter duplicate messages that it finds in different locations in the Notes environment. For example, a message that has been deleted in Notes might appear in Exchange if it had not been processed by the server so that it also occurred in some other Notes locations.
•
Hidden-contact AD forwarding option does not work in Exchange 2010 or later: The AD forwarding option to create a hidden contact and attach it as the alternate recipient of the mailbox (set by [General] Forwarding- Method=0), does not work in Exchange 2010 or later. This appears to be a limitation of Exchange.
•
A Created object within a Notes message appears twice (duplicated) after migration to Outlook.
•
Notes user-created folders are migrated to Outlook system folders. A user-created folder in Notes that has the same name as an Outlook system folder migrates to the corresponding Outlook system folder. Meanwhile, a Notes system folder migrates to its equivalent Outlook system folder. For example, the Notes system "Sent" folder and any user-created folder in Notes named "Sent Items" would both be migrated to the Outlook "Sent Items" folder.
•
When migrating only iNotes contacts, the Notes Mail Files screen does not appear, so you cannot choose to migrate via the server or the file system. The program will run via file system if that's what you chose for your last migration, unless you go into the Task Parameters or INI file and change it.
•
Possible problem with Symantic E-Vault migration: When migrating from a Notes environment with Symantic E-Vault, Exchange propagation issues may interfere with Migrator for Notes to Exchange setting custom attributes when the destination mailbox has never been accessed either by Outlook or by the migration application. One simple workaround would be to first run a "dummy" migration (e.g., use a date filter where date > 1/1/2100) to open all the target mailboxes before running the real migration.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택