Moving Mail Filters Between Apps: Make an Inventory First

Capture the current rules before you leave

Open the current app’s filter or rules settings and record every active rule. Include the rule’s name, whether it is enabled, its position in the list, and any setting that controls whether later rules also run. Rule order can matter: one rule may move a message before another rule gets a chance to act.

Write down the conditions as precisely as the app presents them. Note whether conditions are combined with “all” or “any,” whether a match is based on sender, recipient, subject, or message contents, and whether it uses an exact match or a phrase. Include exclusions, case options, and any scope such as incoming mail only. Do not rely on a short rule name to explain its behavior.

Describe effects, not just labels

For each rule, list every action separately. A rule might move a message to a folder, mark it read, apply a label, flag it, forward it, or delete it. Record the destination folder or forwarding address exactly, and note whether the action happens immediately or only after another condition. If the app shows a stop-processing or skip-later-rules option, include that too.

Distinguish actions that change where a message appears from actions that affect delivery or visibility. For example, moving a message to a folder is not the same as forwarding it, and marking it read does not guarantee it will be easy to find later. This inventory is a description of what the existing app is configured to do, not proof that every message has been handled as intended.

Rule: Messages from [alerts@example.com]
Conditions: sender matches [alerts@example.com]; subject contains [weekly report]
Actions: move to [Reports]; mark read
Order: after [Priority senders]
Enabled: yes

Check what the destination app can express

Compare each recorded condition and action with the destination app’s actual rule controls. Check whether it can use the same fields, match logic, exclusions, and action combination. An app may offer a sender condition but not the exact matching behavior you used before; similarly, it may support folders but not the same forwarding or rule-order controls.

Do not assume that importing an account, connecting a mailbox, or copying messages also transfers filters. If the destination offers an import option, check what it says it includes and inspect the resulting rules rather than treating the import as complete. Where a condition or action is unavailable, leave that rule unrecreated or simplify it only if the changed behavior is acceptable to you.

Rebuild carefully and avoid accidental side effects

Create one rule at a time from your inventory. Select only conditions and actions that match the intended behavior, then review the saved rule before moving on. Pay particular attention to broad conditions such as a common word in the subject or a whole domain in the sender field: a small difference can catch more messages than expected.

Be especially cautious with deletion, forwarding, and rules that mark mail read. If you are unsure whether the destination app interprets a condition the same way, start with a reversible action such as moving a message into a review folder, if that action is supported. Do not replace a narrow rule with a broader one just to make the number of recreated rules match.

Test both matches and near-misses

For each recreated rule, identify a message that should match and one that is similar but should not. Use existing messages if the destination app lets you apply or preview a rule safely; otherwise, send controlled test messages from an address you can access. Do not use sensitive mail as a test. Confirm the actual outcome in the destination app: folder, label, read state, forwarding behavior, and whether any later rule also acted.

Test combinations, not just isolated rules. A message that matches two rules can reveal ordering or stop-processing behavior that a single-message test misses. If forwarding is involved, confirm the destination and inspect what was sent; do not assume that seeing the original message in a folder proves forwarding worked. If the app provides no safe way to test a high-impact action, keep that rule disabled until you can verify it.

For the report rule, test a message from [alerts@example.com] with subject [Weekly report for May] and confirm it goes to [Reports]. Then test a message from [alerts@example.com] with subject [Account notice] and confirm it is not moved by that rule.

Keep an audit note and review after the switch

Mark each inventory entry as recreated, intentionally omitted, or not supported. Add the destination rule’s name and the date you checked its behavior. This makes it easier to diagnose an unexpected message later and prevents you from assuming that an omitted rule was transferred automatically.

After using the new app for a while, inspect the folders and other destinations affected by your most important rules. Check for messages that were caught unexpectedly as well as messages that stayed in the inbox when you expected a rule to act. Adjust one condition at a time, then repeat the match and near-miss checks. Keep the original inventory until you are confident you no longer need to refer to the old configuration.

• Before relying on a rule, confirm its conditions, actions, enabled state, and order.
• Record unsupported rules rather than silently broadening them.
• Verify both an intended match and a similar non-match.