How to migrate old Outlook PST / OST files into new Exchange Server 2007 / SBS2008

I am currently in the process of setting up a new SBS 2008 Server for our company, which I'm just about done with.  I am at the point of getting all of our users into our new Exchange Server 2007 in SBS.  Is there a tool I can use to import all of our users old email (PST & OST files) into the new Exchange Server?  Any help and advice is greatly appreciated.  TIA!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You have two options:

Method1. Use Import-Mailbox Cmdlet on Exchange 2007. But make sure that you have a user and a amailbox for that user already created. The full syntax of the command is:
import-mailbox -identity "UserName" -PSTFolderPath X:\ (Where X is your PSt folder path)

- Create user and mailbox in Exchange / AD

- Move the pst to a specified directory (X:\) and give it the alias name of the mailbox like username.pst if username is the Alias of the user

- Do a export-mailbox Username -Pstfolderpath X:\

=> This will not overwrite the existing PST... This export does a modificication of the existing pst.

- Do a import-mailbox username -pstfolderpath X:\

Method2. The Second option is to import it via Outlook. Open the PSt in Outlook and Manually grad items into your Mailbox.

As far as I know there is no way to import OST files into Exchange.

Best Regards,

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Stewart BeelSenior Technical AnalystCommented:
Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
Don't worry about the OST files. Those will be recreated when the users connect to their mailboxes on the new server.

As for the PST files, those are now stored outside of Exchange. Do you want to import them back into Exchange and add them to the user's mailboxes. If you want to leave them as PST files like they are, you don't have to do anything.
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

dstjohnjrAuthor Commented:
Ok, here is what I could really use some help with currently:

We recently migrated from an externally hosted Exchange provider to Gmail.  Users didn't like Gmail, so, we decided to install an internal Exchange Server via SBS 2008 (although we havent cut over yet... we're still on Gmail, so at least their email is working right now).

What I need to do immediately is get a couple users access back into their old Exchange file so they can access all their old emails.  I need to know which file this would reside in so I can open it with Outlook.

Is it not the Outlook.ost file?  or what it be a .pst file?  TIA!
.If you have a .pst file then that would be the easiest way of importing back the old email into the new exchange server. The .ost is a cached exchange file and is just a offline file for outlook.
Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
The exchange files are actually stored in a database. So it isn't like each user has their own individual file. You can however export specific user's mail to a PST file using the Exchange migration tool. You should then be able to read the resulting PST file in Outlook.
dstjohnjrAuthor Commented:
Thank you for weighing in experts!  We are still going through this, as we have since made the decision to go with Microsoft Online Services, so, we have a whole new set of import issues, which I am posting in another question.  Thanks!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.