Diane Poremsky said:
don't import - let outlook create the new pst, open the old one using file,
open, outlook data store and MOVE the items over. right click on non-default
folders and choose move to move the entire folder and contents. For items in
the default folders, select all (ctrl+a) and right click, move... and when
you're done, your links won't be broken.
This tip was helpful, though the process can be cumbersome.
I had a PST from Outlook 2003 Beta which I wanted to upgrade to the
production release. This might help someone else: I didn't find an
obvious way to Move calendar items, so I Exported my old calendar
folder to a new backup.pst, then immediately imported the folder data
back into the new calendar folder. I'm hoping that the Import
function adjusts internal item structures where required like the
Move.
For development and usage purposes I'm always concerned that MS has
upgraded the internal format of the PST's, less obvious changes than
ANSI/Unicode. You'd hope that something changed/improved between a
beta and production, so it seems logical that using an old PST may not
be a good idea.
Can someone verify that MS has special code to properly Move and
integrate PST data from prior releases into each updated release?
Are RWZ files just as portable, even O2k/XP to O2003? That is, are
the rules updated into the proper format when imported?
Food for thought, no answers requested unless they're quick:
Seems like a whole book chapter (or at least several web pages) could
be dedicated to the nuances of migrating data between any given
release. How do you migrate, for example, if you have access to a
hard drive that has an older Outlook release but that system can't be
booted (need registry for categories, etc)? Do you have to create
folders in a new PST if you import the RWZ from an old one?
I wonder if there'd be any market for one-stop 3rd party migration
tools, considering the obvious issues people are having...
Thanks for all your help MVP's!!!!!!
Tony