10 Best Tzunami Outlook Templates to Streamline Your Migration

Troubleshooting Common Issues with Tzunami Outlook Templates

1. Template not applying to mailboxes

• Cause: Incorrect target mapping or template scope (user vs. shared mailbox).
• Fix: Verify template’s scope and ensure the target mailbox GUID/email matches. Re-run mapping step and apply to the exact mailbox identifier.

2. Missing folders after migration

• Cause: Folder filters in the template or unsupported folder types (hidden/system folders).
• Fix: Check template folder filters and remove restrictive rules. Enable migration of system/hidden folders if needed. Re-run a folder-only test migration to confirm.

3. Duplicate items created

• Cause: Re-running migrations without proper delta/duplication settings or incorrect unique ID mapping.
• Fix: Enable deduplication options in the template, use Change Tracking/Delta migration features, or set correct Source-Target item ID mapping before re-migrating.

4. Attachment or item corruption

• Cause: Transfer interruptions, unsupported attachment types, or encoding mismatches.
• Fix: Run migration in smaller batches, enable retries on failure, and set transfer mode to preserve MIME/encoding. Re-migrate affected items from source.

5. Calendar items missing or incorrectly mapped

• Cause: Time zone conversion issues, recurrence handling differences, or permission mismatches.
• Fix: Ensure template includes calendar-specific mapping, enable time zone normalization, and verify organizer/attendee mappings and permissions.

6. Permissions and delegate access lost

• Cause: Template didn’t include ACL/permission mappings or target system uses different permission models.
• Fix: Add permission mappings to the template, migrate permissions separately, and validate target mailbox ACLs post-migration.

7. Slow migration performance

• Cause: Large batch size, network bottlenecks, or insufficient migration server resources.
• Fix: Reduce batch sizes, increase parallel threads moderately, run during off-peak hours, and monitor network/CPU/IO on migration servers.

8. Errors referencing throttling or rate limits

• Cause: Source/target server throttling (Exchange/Office 365).
• Fix: Enable throttling-aware settings in the template, add retry/backoff policies, and coordinate with admins to temporarily raise limits where possible.

9. Authentication or access failures

• Cause: Expired/insufficient credentials, MFA not handled, or service account lacks rights.
• Fix: Update credentials, use app-only auth where supported, ensure service accounts have impersonation/full-access rights, and handle MFA via app registration or delegated tokens.

10. Template import/export fails

• Cause: Corrupt template file, version incompatibility, or missing dependencies.
• Fix: Validate template XML/JSON, recreate template in the same product version, and ensure all referenced mappings/profiles exist on the target system.

Quick diagnostic checklist

• Confirm template scope and mailbox identifiers.
• Run a small test batch and inspect logs.
• Check filters, dedupe, and delta settings.
• Verify credentials, permissions, and throttling.
• Re-run only affected items after fixes.

If you want, I can provide step-by-step commands or log patterns to look for with your specific Tzunami version and target platform—tell me the version and target (Exchange/Office 365/other).