How to Export and Import Outlook Rules to Another Computer

If you're moving to a new laptop, exporting Outlook rules to another computer is one file, not forty separate clicks — classic Outlook can save every rule to a single .rwz file and reload it with the Import Rules button. New Outlook does not have either option yet, which changes the plan if you've already switched.

Which rules actually need that file depends on where they're stored. Rules tied to an Exchange, Microsoft 365, or Outlook.com account live on the server and show up automatically the moment you sign in elsewhere — the export file is really only for POP accounts and for a handful of actions that only classic Outlook can run locally.

If you've searched for the export option and can't find it, that's often the real answer: you're already in new Outlook, and the button was removed rather than moved. The section on what breaks below covers what to do in that case.

Two different questions can hide inside "transfer my rules": are you moving a whole account to a new machine, or copying a handful of rules to a second account you already use elsewhere? The export file answers both, but the checklist below is written for the more common case — one person, one mailbox, a hardware swap.

What Actually Moves With Your Mailbox, and What Doesn't#

Outlook rules split into two families, and only one of them needs an export file at all. Server-side rules are stored on the mail server itself — Exchange, Microsoft 365, or Outlook.com — and Outlook evaluates them even when the app isn't open. Sign into that same account on a new computer, and those rules are already there.

Client-side rules exist only inside the local Outlook profile. They cover actions the server can't perform on its own: playing a sound, starting another program, moving a message straight into a local .pst archive, or applying a custom form. These are the rules the .rwz export file actually protects.

The split matters more than the export button itself. A reader who backs up only the client-side rules and assumes the whole set is protected usually finds out the hard way mid-migration, when a server-side rule they never thought about keeps working fine and a local one just stops.

It also explains why a Gmail or Yahoo account added to classic Outlook behaves differently from an Exchange account added the same way: unless the provider runs its own server-side filters, every rule Outlook applies to that account is client-side, so it depends entirely on the export file to travel anywhere.

• Stays on the server automatically: move or copy to a server folder, forward, redirect, mark as read, apply a category, delete
• Needs the export file: play a sound, start an application, move to a local .pst archive, run a script, apply a custom form
• Doesn't move into new Outlook either way: it has no rules import screen at all — see the FAQ

Pre-Migration Checklist#

Do these before you touch the export button. Skipping them is why an import looks successful and then quietly doesn't fire.

None of this takes long, and skipping it is the most common reason people report that a rules migration "didn't work." The export and import mechanism itself is reliable; missing context about what each rule depends on is what actually breaks.

• Confirm you're in classic Outlook, not new Outlook — the Export Rules button lives under File > Manage Rules & Alerts > Options, and that path doesn't exist in the new app
• Check the account type: Exchange, Microsoft 365, and Outlook.com rules already travel with the account; POP and local-only rules are the ones that genuinely need the file
• Note anything close to the rules quota — inbox rules are capped around 256 KB total per mailbox, higher for migrated mailboxes, so a bloated rule set can fail to import in full without an obvious error
• Write down the exact folder names, categories, and .pst file paths your client-side rules reference — a rule pointing at a path that doesn't exist on the new machine drops that action silently
• List or screenshot your current rule names and their order before importing anything, as your rollback reference
• If more than one person shares the migration — a team moving off one shared machine — export separately per mailbox; the .rwz file is scoped to whichever account was selected in the rules list when you clicked Export
• Create one throwaway test rule before you export — something obvious, like moving a specific test-only sender straight to a folder — so you have a single, disposable rule to check on the new machine before you trust the whole set

How to Export and Import the Rules File#

The path is the same in both directions: Manage Rules & Alerts, then the Options button most people never open.

One thing trips people with more than one account in the same Outlook profile: the rules list is scoped to whichever account is selected when you open the dialog, so switch accounts first if you manage more than one mailbox.

1. 1

   Open Manage Rules & Alerts

   In classic Outlook, go to File > Manage Rules & Alerts. On some ribbon layouts this sits under the Rules menu instead of File.

2. 2

   Click Options, then Export Rules

   In the dialog, click the Options button in the top corner, then Export Rules. This exports every rule for the selected account at once, not one at a time.

3. 3

   Save the .rwz file

   Name the file and save it somewhere you'll actually find again — a cloud drive folder or a USB stick, not the desktop of the machine you're retiring.

4. 4

   Move the file to the new computer

   Copy it over however you'd move any small file: cloud sync, USB drive, or a message to yourself. The .rwz file itself is typically a few kilobytes.

5. 5

   Open Manage Rules & Alerts on the new machine

   Same File > Manage Rules & Alerts path, same Options button — this time click Import Rules and select the file you saved.

6. 6

   Verify order and test each rule

   Imported rules are appended to the existing list, not merged in place, so check the run order and re-tick 'stop processing more rules' where the sequence matters, then send a test message per rule.

7. 7

   Repeat per account

   If you manage more than one mailbox in the same Outlook profile, export and import run once per account — there's no single file that carries rules for every account in the profile.

What Breaks When You Move Rules to a New Computer#

Not every rule element survives the round trip cleanly. This is what to check before you assume the import worked. The table assumes a like-for-like move — classic Outlook to classic Outlook; every "no" row below gets worse, not better, if the destination is new Outlook instead.

None of these are one-in-a-thousand edge cases — they're the six or seven things that show up in almost every rule set once it's more than a year or two old, because rules accumulate folder references and local dependencies gradually, without anyone auditing them until a migration forces the question.

Rollback Plan#

If imported rules misfire — wrong order, an action that silently fails — you don't need to touch the account's server-side rules to fix it. Import only adds entries; it never overwrites what was already there.

Compare the new list against the screenshot or list you made in the checklist step. Delete anything that's clearly a duplicate or that references a path that doesn't exist on this machine, then re-import a corrected .rwz file if you need to start over.

Outlook on the web is a useful neutral check here: it shows the server-side rules for the account regardless of which desktop machine you're on. If a rule you expect to see is missing there too, the problem is the rule itself, not the migration.

Doing It Without Downtime#

If every rule you rely on is server-side, there's genuinely nothing to migrate — sign into the account on the new machine and the rules are already running. The export and import steps above only matter for the client-only actions layered on top.

For a heavier client-only rule set, keep the old machine's Outlook profile active until you've verified each imported rule fires on the new one. Run both for a day, then decommission the old install once test messages land where they should.

Shared and delegated mailboxes complicate this further. A delegate's client-only rules live on the delegate's own machine, not the shared mailbox, so migrating the delegate's computer doesn't touch anything the mailbox owner or other delegates see — each person on a shared mailbox handles their own export separately.

IMAP accounts sit in between the two families. Some providers process filters server-side (Gmail's own filters, for instance), but any rule you built inside Outlook for an IMAP account is client-only by definition, so it follows the same export path as a POP account rather than the server-side path Exchange rules use.

If you're weighing whether to do this migration in classic Outlook now or wait and rebuild in new Outlook instead, there's no forced deadline pushing that decision this year. Microsoft moved the enterprise opt-out window for new Outlook to 1 March 2027, per Microsoft 365 message center post MC949965 (updated 20 February 2026), and classic Outlook is licensed to stay supported until at least 2029. A same-version machine swap in classic Outlook is a safe, current option, not something you're racing a shutdown to finish. Confirm your organization's own timeline in the Microsoft 365 admin center rather than a blog post — the opt-out date is tenant-controlled.

Either way, the export file is disposable once you trust the new machine. Keep it around as a lightweight backup of your rule set, but the source of truth after the move is whatever's actually running — not the .rwz file that got you there.

Where AI Emaily Fits#

The .rwz file only solves the classic-Outlook half of this problem. If you're one of the readers rebuilding rules by hand in new Outlook because there's no import screen yet, re-typing ten filters from memory is where most people give up halfway through.

AI Emaily's Rules + Context Brain connects to the same Outlook mailbox — Gmail and IMAP accounts too — and keeps filing logic in one place that isn't tied to a single desktop app's export button. You describe what should happen to a sender or a subject line once, and it applies going forward without a .rwz file to lose track of on the next machine swap. It doesn't import an existing .rwz file itself; think of it as the rebuild step, not the migration step. We build AI Emaily.