Shoviv GroupWise to Outlook: Step-by-Step Migration Guide

Troubleshooting Shoviv GroupWise to Outlook Migrations — Common Issues & Fixes

1. Connection failures to GroupWise server

• Cause: Incorrect server address, port, or network/firewall blocking.
• Fix: Verify server/port and network reachability (ping/traceroute). Allow ports in firewall and proxy; test with GroupWise client credentials; use correct connection mode (Online, Caching, Default Proxy, Remote).

2. Authentication or permission errors

• Cause: Wrong credentials or missing mailbox/admin rights.
• Fix: Use valid user credentials or GroupWise admin account. For Exchange/Office 365 targets, ensure required admin roles and mailbox full-access are granted. Re-enter credentials and retry.

3. Partial or missing mailbox items after export

• Cause: Filter settings, unsupported item types, or corrupted source items.
• Fix: Disable/adjust filters, enable full item export (include calendars/contacts/archives), run export on smaller mailbox subsets, repair or re-sync corrupt GroupWise mailboxes before migration.

4. Large mailboxes / PST size issues

• Cause: Single PST exceeds Outlook limits or migration stalls on very large folders.
• Fix: Use Shoviv PST-splitting option (set target PST size), migrate mailboxes in batches, export archive mailboxes separately.

5. Slow performance or long migration times

• Cause: Network latency, CPU/Disk I/O limits, migrating many mailboxes at once.
• Fix: Migrate during off-hours; increase parallel threads moderately; run tool on a machine with better CPU/RAM and fast disk; migrate fewer mailboxes concurrently.

6. Errors exporting attachments or special characters

• Cause: Encoding/Unicode issues or corrupted attachments.
• Fix: Ensure Unicode PST option is selected; test export of affected items individually; re-save or remove corrupted attachments in source if necessary.

7. Mapping/misplaced folders in target PST/Exchange

• Cause: Incorrect folder mapping or automatic mappings not matching source structure.
• Fix: Use manual mailbox/folder mapping in the tool, preview mapping before final run, and enable “preserve folder hierarchy” options.

8. Tool crashes or unexpected exits

• Cause: Software bugs, insufficient system resources, or incompatible versions.
• Fix: Update Shoviv to latest build; ensure system meets requirements; check Windows Event Viewer for errors; contact Shoviv support with log files and a small reproducible sample.

9. Incremental export not behaving as expected

• Cause: Incorrect incremental settings or changed source item metadata.
• Fix: Confirm incremental export option is enabled and configured correctly; if issues persist, perform a fresh full export for that mailbox.

10. Office 365 / Exchange target failures

• Cause: Throttling, incorrect target configuration, or lack of required Exchange Online permissions.
• Fix: Use application impersonation or proper admin credentials, respect throttling (reduce concurrency), validate target mailbox existence and quota, and check Azure AD app permissions if using app-based auth.

Quick diagnostics checklist (run before full migration)

1. Confirm GroupWise and target credentials work in native clients.
2. Test connectivity (ping/traceroute, telnet to ports).
3. Run a small test migration (single mailbox).
4. Enable Unicode PST and set PST split size if large mailboxes.
5. Collect logs from Shoviv and note error codes/messages for support.

When to contact Shoviv support

• Persistent crashes or unexplained error codes after updating to the latest build.
• Reproducible data loss or corruption in exported items.
• Large-scale migrations requiring vendor guidance on performance tuning.

If you want, I can produce a short pre-migration checklist tailored to your environment (mailbox counts, average size, GroupWise version) and recommended Shoviv settings.