1. Purpose
This document defines the scope, limitations, and post-migration review period when migrating email accounts from Rackspace (or any third-party provider) to JUCRA’s SmarterMail infrastructure.
Approval of this policy confirms acceptance of the review period and responsibility boundaries.
2. Scope of Migration
JUCRA will:
-
Create mailboxes on the new SmarterMail server
-
Configure DNS (MX, SPF, DKIM, DMARC where applicable)
-
Migrate server-side mailbox data from the source provider
-
Confirm successful mailbox login via webmail
-
Confirm folder structure visibility at top level
Migration is performed server-to-server.
JUCRA does not migrate:
-
Local PST or OST files
-
Emails stored only on user computers
-
Emails archived locally in Outlook
-
Data inside email client rules or profiles
-
Corrupted mailbox structures
-
Third-party application integrations
3. 10-Day Verification Period
After migration completion, the client has:
10 natural calendar days to:
-
Check all folders via webmail
-
Confirm presence of critical mail
-
Confirm sent mail visibility
-
Report any missing folders or anomalies
Webmail is considered the authoritative source of truth.
After 10 days:
-
The migration is deemed accepted
-
The source account may be permanently closed
-
No further recovery attempts can be guaranteed
4. Special Character & Folder Structure Limitation
Certain folder naming formats may not migrate correctly, including but not limited to:
-
Leading special characters (*, &, %, etc.)
-
Invalid UTF encodings
-
Deeply nested folder structures
-
Provider-specific system folders
-
Folders using forward slashes or reserved characters
If a folder does not migrate:
-
JUCRA will review the source account (within the 10-day window)
-
JUCRA will attempt a manual folder review free of charge
-
Restoration is best-effort only
JUCRA cannot guarantee recovery of:
-
Corrupted folders
-
Improperly encoded folder names
-
Folders created by client-side mail software anomalies
5. Local Email Client Limitation
JUCRA is not responsible for:
-
Emails stored only in Outlook PST/OST files
-
Emails previously deleted locally
-
Rules that moved emails to local-only folders
-
Cached mode display inconsistencies
-
Folder mapping issues inside Outlook or other clients
-
Synchronisation issues on mobile devices
As outlined in the JUCRA Email Support Policy :
JUCRA provides infrastructure only.
JUCRA does not provide end-user IT support.
6. Definition of “Missing Email”
An email is considered “missing” only if:
-
It does not exist in webmail on the source server, and
-
It does not exist in webmail on the destination server
If the email exists in webmail but not in Outlook or a device, this is a client-side issue and falls outside migration scope.
7. Backup & Recovery Limitation
During the 10-day verification window:
-
JUCRA may temporarily retain access to the source mailbox (if contractually possible)
-
After this window, access to the source provider cannot be guaranteed
-
JUCRA is not responsible for third-party provider retention policies
JUCRA cannot guarantee indefinite access to legacy systems.
8. Acceptance Clause
By approving migration, the client confirms:
-
They understand the 10-day review period
-
They will verify mailboxes via webmail
-
They accept the infrastructure-only support model
-
They accept limitations relating to special characters and client-side storage
-
They accept that after 10 days, the migration is considered complete
9. Large Mailbox Disclaimer
Very large mailboxes may require staged migration and may not complete instantly.
