You copy Outlook tasks to another computer by exporting them to a Personal Storage Table file, moving that file to the new machine, and importing it back into Outlook. The fastest path is File > Open & Export > Import/Export > Export to a file > Outlook Data File (.pst), but the right method depends on whether you use classic Outlook for Windows, the new Outlook, Outlook for Mac, Outlook on the Web, or a Microsoft 365 mailbox tied to Microsoft To Do.
The problem the topic addresses is real and common. Tasks stored in a local Personal Storage Table file do not sync with the cloud, so a hard drive failure or a new laptop can wipe years of action items. Microsoft’s own guidance in the Outlook data file documentation confirms that PST data lives only on the device unless you move it. Tasks stored on Exchange Online behave differently because they ride with your mailbox and surface inside Microsoft To Do.
A 2025 Statista report on cloud adoption shows that 60% of corporate data now lives in the cloud, yet many Outlook users still keep tasks in legacy local files. That mismatch is exactly why a clean copy plan matters.
Here is what you will learn in this guide:
- 📦 How to export and import a PST so every task moves intact
- 🔄 How cloud-synced Microsoft 365 mailboxes copy themselves automatically
- 🍎 How Outlook for Mac and Outlook on the Web differ from Windows
- ⚠️ The mistakes that quietly delete or corrupt task data during a move
- 📜 How U.S. retention laws like Sarbanes-Oxley and HIPAA shape your move
Understand Where Outlook Tasks Actually Live
Before you copy anything, you need to know where the tasks sit. Outlook stores items in two main containers, and the storage type controls every step that follows. The first is a Personal Storage Table file, known as a PST file, used by POP3 accounts and on-premises archives. The second is an Offline Storage Table file, the OST, which mirrors an Exchange or Microsoft 365 mailbox.
The PST is portable. You can copy it, move it, or import it on any Windows PC running Outlook. The OST is not portable. Microsoft’s OST file overview makes clear that an OST is tied to one profile on one machine and rebuilds itself from the server.
For tasks, that distinction is everything. If your tasks live in a PST, you must physically move the file or export it. If they live in Exchange Online, signing into Outlook on the new machine is enough because the server pushes the tasks down again. The consequence of getting this wrong is real. A user who copies an OST file to a thumb drive and tries to open it on a new PC will hit an error, because OSTs cannot be imported by the standard Outlook import wizard.
A common misconception is that tasks always sync with the cloud. They do not. Tasks created in a local PST stay local until you export them. That is why a University of Wisconsin IT note warns that moving items into a local PST removes them from the web view.
How To Find Your PST or OST File
Open Outlook on the old computer. Click File, then Account Settings, then Account Settings again, and pick the Data Files tab. Click any entry and choose Open File Location as described in this eSilo data-file walkthrough. Windows opens File Explorer at the right folder.
The default path on Windows 10 and Windows 11 is C:\Users\<username>\Documents\Outlook Files for PSTs created in Outlook 2013 or later. Older builds drop the file at C:\Users\<username>\AppData\Local\Microsoft\Outlook, a hidden path noted in this Ablebits backup guide. The consequence of guessing wrong is that you copy a stale or empty file and lose every task you thought you saved.
A common misconception is that the AppData folder is visible by default. It is not. You must enable hidden items in File Explorer’s View menu first.
Tasks vs. To Do vs. Flagged Email
Outlook treats tasks, To Do items, and flagged email as related but different objects. The classic Tasks module stores items in the Tasks folder of your data file. Microsoft To Do, explained in this To Do integration guide, syncs tasks across devices through Exchange Online. Flagged emails surface as tasks but live inside the mail folder.
The consequence of mixing these up during a copy is data loss. A flagged email moved without the underlying mail item loses the flag context. A To Do task that was never saved to the mailbox folder will not appear in a PST export.
A common misconception is that exporting a PST captures To Do items the same way it captures classic tasks. It captures the underlying mailbox tasks folder, not the Microsoft To Do app’s separate metadata.
Method 1: Copy Tasks With a PST Export and Import
The export and import method is the official Microsoft path and it works on every version of classic Outlook for Windows from 2010 through Microsoft 365. It works for any account type because the export reads what is currently in your data file rather than what is on the server.
On the old computer, open Outlook and click File, then Open & Export, then Import/Export. Pick Export to a file and click Next. Choose Outlook Data File (.pst) and click Next as outlined in this Dell migration article. Select the Tasks folder, check Include subfolders, and click Next. Pick a save location, leave the duplicate option on Replace duplicates with items exported, and click Finish.
You can set a password on the export. The consequence of choosing a password is real protection against casual snooping, but Microsoft warns in the PST password support article that lost passwords cannot be recovered. A common misconception is that the password encrypts the file. It does not — it only blocks the wizard, and forensic tools can still read the contents.
Copy the resulting PST to a USB drive, OneDrive, or a network share. On the new computer, open Outlook and click File, then Open & Export, then Import/Export. Pick Import from another program or file, then Outlook Data File (.pst), browse to the file, and click Finish. The Tasks folder appears in your task list.
Real-World Example: Maria the Paralegal
Meet Maria, a paralegal at a Chicago law firm. She tracks 412 case-related tasks in classic Outlook. Her firm gives her a new Lenovo ThinkPad and she has 24 hours to migrate. Maria exports a PST named tasks-2026-04.pst, copies it to a firm-issued encrypted USB drive, and imports it on the new laptop. Every task, including custom categories and due dates, lands intact.
The legal angle matters here. Under the Federal Rules of Civil Procedure Rule 37(e), a party that loses electronically stored information after a duty to preserve attaches can face sanctions. Maria’s careful copy keeps her firm out of spoliation trouble.
The consequence of skipping the export step would have been the loss of attorney-client task notes that the firm must preserve under ABA Model Rule 1.15. A common misconception is that IT can always recover a wiped laptop. They often cannot, especially after secure-erase.
Real-World Example: David the Small Business Owner
David runs a four-person HVAC shop in Tampa. His tasks live in a POP3 account on his old desktop. He exports the Tasks folder to david-tasks.pst, uploads it to OneDrive, and downloads it on his new desktop. The whole job takes 18 minutes.
David’s concern is the IRS recordkeeping rule under 26 CFR 1.6001-1 that requires business records to remain accessible. His task list contains job-cost notes, so the export protects deductible documentation. The consequence of losing those notes would be a denied deduction during an audit.
A common misconception is that POP3 mail clients auto-sync tasks across devices. POP3 only handles inbound email, so tasks never leave the local machine without a manual export.
Method 2: Let the Cloud Do the Work
If your Outlook account is Microsoft 365, Exchange Online, or Outlook.com, the easiest copy method is no copy at all. Tasks stored in those mailboxes live on Microsoft’s servers, and they reappear the moment you sign into Outlook on the new device. Microsoft confirms this in the Microsoft 365 mailbox sync article.
On the new computer, install Outlook from your Microsoft 365 portal. Sign in with the same work or school account. Wait for the initial sync to finish, which can take a few minutes for large mailboxes. Open the Tasks module or the To Do app, and your tasks are there.
The consequence of skipping a final sync check is silent data loss. If the old PC had cached tasks that never uploaded, signing in on the new PC will not magically pull them down. Always confirm the Send/Receive queue is empty before you decommission the old machine.
A common misconception is that every Outlook account syncs tasks to the cloud. Only Exchange-class accounts do. IMAP and POP3 do not, even though IMAP syncs email.
Microsoft To Do as a Bridge
Microsoft To Do is the modern face of Outlook tasks. As the To Do support page explains, every task you create in classic Outlook against an Exchange mailbox flows into To Do automatically. Install the To Do app on the new computer, sign in, and your tasks appear with all due dates, reminders, and subtasks intact.
The consequence of relying on To Do without a backup is that an accidental deletion propagates everywhere within seconds. A common misconception is that the cloud is a backup. It is replication, not preservation, and Microsoft’s shared responsibility model places data protection on the customer.
New Outlook for Windows
The new Outlook for Windows replaces the classic client and routes tasks through the cloud by default. The new Outlook overview makes clear that there is no local PST for new Outlook accounts. To copy tasks, simply sign in on the new computer.
The consequence of trying to export a PST from new Outlook is frustration, because the menu is missing or limited. A common misconception is that new Outlook is just a refresh of classic Outlook. It is a different application built on the web stack.
Method 3: Outlook for Mac and Outlook on the Web
Outlook for Mac stores data in an OLM file, not a PST. To move tasks between two Macs, export an OLM through File > Export as documented in this Outlook for Mac export guide. Copy the OLM to the new Mac and import it through File > Import.
The cross-platform challenge is real. A PST cannot be imported into Outlook for Mac directly, and an OLM cannot be imported into Outlook for Windows directly. You need a bridge account on Exchange Online, or a paid converter such as Stellar Converter for OLM. The consequence of skipping the bridge is wasted hours and possible data corruption.
Outlook on the Web has no local data file. Tasks live on the server. To copy tasks between two browser sessions, you simply sign in. To export, use the OWA export option by first connecting the account in classic Outlook, then exporting from there.
A common misconception is that you can drag tasks from OWA to your desktop. You cannot. The browser does not expose the underlying mailbox file.
Example: Priya the Mac-to-Windows Switcher
Priya is a designer in Austin moving from a 2019 MacBook Pro to a Surface Laptop. Her 89 tasks live in an OLM. She first connects her Microsoft 365 account in Outlook for Mac, lets the tasks sync to Exchange Online, then signs into the new Surface. The tasks appear in seconds.
The consequence of trying a direct OLM-to-PST conversion would have been a third-party tool fee and possible category loss. Priya’s bridge approach is free and clean. A common misconception is that Macs and PCs cannot share Outlook data. They can — through the cloud.
Three Common Migration Scenarios
| Migration Path | Outcome You Should Expect |
|---|---|
| Classic Outlook PST exported and imported on new Windows PC | All tasks, categories, and due dates land intact in a new data file |
| Microsoft 365 account signed into new computer with no export | Tasks sync from Exchange Online within minutes; no manual copy needed |
| Outlook for Mac OLM moved to Windows without a bridge account | Tasks fail to import; you must use a converter or an Exchange bridge |
Mistakes to Avoid
The migration looks simple, but the failure modes are sharp. Each mistake below has cost real users real data.
- Closing Outlook ungracefully before the copy. A PST in active use can be locked or partially written, leading to a 0xc0000005 corruption error on import.
- Copying an OST instead of a PST. OSTs cannot be imported through the wizard, as confirmed in the Microsoft data file article.
- Skipping the Include subfolders checkbox. Custom task subfolders are silently dropped from the export.
- Forgetting the password. A password-protected PST cannot be recovered without the password and Microsoft will not break it for you.
- Relying on Cached Exchange Mode without checking the cache window. The default 12-month cache means older tasks may not be in the local PST at all.
- Storing the PST on a FAT32 USB drive over 4 GB. FAT32 file size limits truncate the file mid-copy.
- Importing into the wrong profile. Tasks land in a profile you do not normally use, and you think they are gone.
- Treating cloud sync as backup. Replication is not preservation; one bad delete propagates instantly.
- Migrating during an active sync. Items in transit can be lost if you yank the device offline mid-Send/Receive.
Pros and Cons of Each Method
PST Export and Import
| Pros | Cons |
|---|---|
| Works on every classic Outlook version since 2010 | Manual and slow for large mailboxes |
| Captures categories, due dates, and reminders | OST files cannot be exported this way without a bridge |
| Portable to any Windows PC | Password loss is permanent |
| Independent of internet access | Cached Exchange Mode may exclude older tasks |
| Free and built into Outlook | Requires you to remember the file location |
Cloud Sign-In Sync
| Pros | Cons |
|---|---|
| Zero manual file handling | Requires Exchange-class account |
| Tasks appear automatically | Sync errors can hide partial transfers |
| Cross-device availability through To Do | Cloud outage blocks the move |
| Survives a stolen laptop | A bad delete propagates everywhere |
| Compliant with most retention frameworks | You depend on Microsoft’s uptime SLA |
Do’s and Don’ts
Do’s
- Do close Outlook before copying any data file, because Windows locks the PST during use.
- Do verify the new machine’s Outlook build matches or exceeds the old one, because newer PSTs cannot open in older clients.
- Do keep a second copy of the PST on a separate drive for at least 30 days after the move.
- Do test the import on the new computer before wiping the old one, because rollback options vanish after a wipe.
- Do document the transfer date and method, especially for regulated industries under HIPAA 45 CFR 164.310.
Don’ts
- Don’t rely on drag-and-drop between Outlook windows, because tasks dropped on certain folders silently convert to email.
- Don’t trust antivirus exclusions on the new PC; a real-time scanner can corrupt a PST mid-import.
- Don’t import a PST larger than 50 GB, because performance degrades sharply past that mark per Microsoft’s PST size guidance.
- Don’t assume IMAP carries tasks; it does not.
- Don’t delete the old data file until the new client has been used for at least one full Send/Receive cycle.
Step-by-Step: Export Tasks From Classic Outlook
Each step matters and each choice has a downstream consequence.
- Open Outlook and click File.
- Click Open & Export, then Import/Export.
- Choose Export to a file and click Next.
- Pick Outlook Data File (.pst) and click Next.
- Highlight the Tasks folder, check Include subfolders, and click Next.
- Click Browse, pick a folder you can find later, name the file with the date, and click OK.
- Choose Replace duplicates with items exported to avoid stale versions overwriting fresh ones.
- Click Finish.
- Optionally set a password; remember it cannot be recovered.
- Wait for the progress dialog to close before ejecting any drive.
The consequence of skipping step 7 is duplicate task chaos on the new machine. A common misconception is that Outlook auto-deduplicates after the import. It does not.
Step-by-Step: Import Tasks Into the New Computer
- Install Outlook on the new computer and complete first-run setup.
- Click File, then Open & Export, then Import/Export.
- Choose Import from another program or file and click Next.
- Pick Outlook Data File (.pst) and click Next.
- Browse to the PST you copied over.
- Choose Do not import duplicates to keep server-synced items clean.
- Click Next.
- Pick the Tasks folder and check Include subfolders.
- Choose Import items into the same folder in: your current account so the tasks merge with cloud-synced ones.
- Click Finish and watch the status bar.
The consequence of choosing Import items into the current folder when you meant same folder in is that subfolders flatten into one list. A common misconception is that you can re-run the import to fix it; you have to delete the bad import first.
U.S. Legal and Compliance Considerations
Tasks often contain sensitive information that triggers federal retention rules. The Sarbanes-Oxley Act Section 802 requires public companies to preserve records that could relate to financial statements for at least seven years. A task tied to an audit checklist falls under that umbrella.
The Health Insurance Portability and Accountability Act applies when tasks reference patient information. Healthcare workers who copy tasks must document the transfer in the security log under 45 CFR 164.308.
The Gramm-Leach-Bliley Safeguards Rule covers financial firms. Tasks containing client SSNs or account numbers must move only on encrypted media. The consequence of moving them on an unencrypted USB drive is an FTC enforcement action.
State laws layer on top. The California Consumer Privacy Act and the New York SHIELD Act require reasonable security during data transfers. A common misconception is that an internal move is exempt from breach laws. It is not — a lost USB still triggers notification.
Recap of Relevant Rulings
In Zubulake v. UBS Warburg, the Southern District of New York held that parties must preserve electronically stored information once litigation is reasonably anticipated. Tasks tracking case work fall squarely within that duty. The consequence of a sloppy migration that loses tasks during litigation is an adverse inference instruction.
In Coleman (Parent) Holdings v. Morgan Stanley, the court imposed a $1.45 billion judgment partly because of email and task data loss during system migrations. The case shows that migration mistakes carry real money consequences.
Key Entities You Should Know
- Microsoft Corporation — publisher of Outlook and the steward of the PST and OST formats per Microsoft Learn.
- Exchange Online — the cloud mailbox service that holds Microsoft 365 tasks.
- Microsoft To Do — the modern task interface that mirrors mailbox tasks per the To Do site.
- The PST and OST formats — the two Outlook data files; only the PST is portable.
- The Federal Trade Commission — the agency that enforces the Safeguards Rule and CCPA-adjacent privacy obligations through the FTC privacy program.
- The U.S. Department of Health and Human Services — the HIPAA enforcer through its HHS HIPAA portal.
- The American Bar Association — the source of model rules that govern lawyer data handling.
FAQs
Can I copy Outlook tasks without a PST file?
Yes. If your account is Microsoft 365 or Exchange, sign into Outlook on the new computer with the same credentials and the tasks sync from the server within minutes.
Will my categories and due dates survive the export?
Yes. A PST export preserves categories, due dates, reminders, and recurrence patterns when you choose Outlook Data File (.pst) as the export format and include subfolders.
Can I import a PST into Outlook for Mac?
No. Outlook for Mac uses the OLM format and cannot directly import a PST; you must bridge through an Exchange Online account or use a third-party converter.
Does the new Outlook for Windows support PST export?
No. The new Outlook for Windows is cloud-first and does not expose the classic PST export wizard for most account types; use classic Outlook to export.
Are tasks in Microsoft To Do automatically backed up?
No. Microsoft replicates To Do data but the shared responsibility model places backup duty on the customer; use a third-party tool for true backup.
Can I password-protect my PST during export?
Yes. Outlook offers a password field at the end of the export wizard, but Microsoft cannot recover lost passwords, so store the password securely.
Will copying an OST file work the same as a PST?
No. OST files are tied to a single profile and machine and cannot be imported through the standard wizard; convert to PST first or use a cloud sync.
Do IMAP accounts move tasks between computers automatically?
No. IMAP only synchronizes email folders, not tasks; you must export tasks to a PST manually before switching computers.
Is a USB drive safe enough for a task migration?
Yes, if the drive is encrypted with BitLocker or hardware encryption; an unencrypted drive can trigger breach notification laws if lost.
Can I migrate just one task folder instead of all tasks?
Yes. During the export wizard, highlight only the specific subfolder you want and uncheck Include subfolders to limit the scope precisely.
Do I need to keep the old PST after a successful import?
Yes. Keep the old PST for at least 30 days as a safety net; some import errors only surface days later when you open older tasks.
Will my tasks show up in the To Do app after the import?
Yes, if the account is Exchange-based; the imported tasks land in the mailbox and To Do reads from the same store within one sync cycle.
Does the size of my PST affect the migration?
Yes. Microsoft recommends keeping PSTs under 50 GB for stable performance; larger files migrate slowly and risk corruption during the import.
Can my IT admin move tasks for me through Group Policy?
Yes. Enterprise admins can use the Office Deployment Tool and roaming profiles to relocate Outlook data files across machines without user action.