I've got a new version of the Exchange setup script for Outlook that supports importing from Entourage 2008 or 2004. For now, I'm placing it on GitHub for download until I can get it better tested and documented. You'll find it here:
https://github.com/talkingmoose/Outlook-Exchange-Setup/tree/4.5
The "README" includes a handful of notes about what's changed. The actual script you'll want to download is "OutlookExchangeSetup4.5.scpt".
How it works
The old instructions for deploying the script remain the same. Nothing has changed with that.
When the script runs it will check for the existence of:
- ~/Documents/Microsoft User Data/Office 2008 Identities/
- ~/Documents/Microsoft User Data/Office 2004 Identities/
If it doesn't find any old databases then it proceeds as before with configuring a new Exchange account.
If it finds any Entourage identities it will prompt the user to "Upgrade" or create a "New" email database. If he selects "New" then it proceeds as before with configuring a new Exchange account.
If he selects "Upgrade" the script it will create a list of the existing Entourage database identities (ignoring backup folders created when repairing the database) and prompt him to select one. I've included the modifications dates to indicate the most recent version vs. older versions. (I opted not to enable importing multiple identities because doing so could possibly create multiple accounts with the same settings.)
When the user chooses an Entourage identity the script begins the import process. Because AppleScript doesn't support things like progress bars or dynamic dialog boxes I have to use a rudimentary "dialog" window to show progress. I update the dialog every 20 seconds but that's a new configurable option in the properties list at the top of the script. Setting this to a lower number (more frequent) will have a noticeable impact on import time.
During the import the script is looking at the CPU usage by the "Microsoft Database Daemon". This is the application actually doing the import. Generally, it will use less than 5% of CPU at any given time. So long as the script reads that the Database Daemon is consuming more than 5% CPU for an extended period of time then it continues to update its progress.
In my limited testing on my 2.4 GHz MacBook Pro with 8 GB RAM and a 5400 RPM drive I am importing a 2.5 GB database in about 18 minutes. Keep in mind that the import process does not import Exchange account or IMAP account messages/events/contacts/tasks/notes. Microsoft expects those to download from the server. The script should import:
- Any messages/events/contacts/tasks/notes copied from an Exchange or IMAP account to folders under "On My Computer"
- Accounts
- Delegate accounts
- Autocorrect rules (I think)
- Categories
- Rules
- Schedules
- Signatures
I'd appreciate feedback from anyone who tests. :-)
@Don You're allowed a year to give feedback since you had to wait that long.