Preserving Read/Unread Status and Email Metadata During Migration

What Counts as Email Metadata

Metadata is everything about a message that isn't the message body itself. It's the layer of information that makes an inbox searchable, sortable, and trustworthy. For a Google Workspace migration, this includes:

• Sent and received timestamps: the exact date and time each message was sent or arrived, not the date it happens to be re-imported.
• Read/unread status: whether a user had already opened a message before migration.
• Flags and labels: starred items, Gmail labels, categories, and any custom tagging applied in the source mailbox.
• Sender and recipient details: the To, From, Cc, and Bcc fields exactly as they appeared originally.
• Folder and label hierarchy: how messages were organized, including nested folders and label structures.
• Message properties: formatting, inline images, and attachment associations tied to each email.

None of this is visible in the email body, but all of it shapes how a mailbox feels once it lands on the new platform. Lose the timestamps and a user's sent history gets reordered. Lose the read/unread flags and every message looks new again, even ones opened months ago.

Why Metadata Preservation Matters During Migration

Search and retrieval

Most people rely on date ranges to find old emails: "the invoice from around March," or "that thread from last quarter." If migration shifts message timestamps, search results stop matching what users remember, and finding a specific email becomes guesswork instead of a quick lookup.

Compliance and legal holds

Organizations in regulated industries often need to prove exactly when a message was sent or received. Altered timestamps or missing sender/recipient data can undermine audit trails, weaken e-discovery responses, and break retention policies that depend on accurate, unaltered metadata.

User experience on day one

Nothing erodes confidence in a migration faster than opening a new mailbox and finding thousands of messages marked unread. A flood of false unread flags signals to employees that something went wrong with the migration, even when the content itself is fine. Preserved read/unread status lets employees pick up exactly where they left off, without re-sorting years of correspondence just to find what's actually new.

Workflow continuity

Flags, labels, and folder structure aren't cosmetic details. Teams build filters, rules, and daily habits around them. When a migration flattens that structure, the time employees spent organizing their mailbox disappears along with it, and rebuilding those habits from scratch costs real productivity.

How EdbMails Preserves Metadata During Migration

EdbMails treats metadata as part of the message itself rather than something to reconstruct afterwards. During a Google Workspace to Office 365, Exchange, or IMAP migration, the tool reads each email's full property set, including timestamps, read/unread flags, sender and recipient headers, and folder placement, then replicates it on the destination server rather than assigning new values on arrival.

A few specifics worth knowing:

• Original folder hierarchy is mapped, not rebuilt: EdbMails carries over the Gmail label and folder structure, so nested folders appear in the same arrangement on the target mailbox, whether that's Office 365, Exchange Server, or an IMAP-based system.
• Read/unread status transfers as-is: A message left unread in Gmail stays unread after migration; one already opened stays marked read. This holds across every supported target, from Google Workspace to Office 365 to Google Workspace to Exchange and Google Workspace to IMAP.
• Selective filters can use metadata too: Administrators can filter migrations by date range, sender or recipient address, or even by message read/unread status, which is useful for staged migrations or compliance-driven selective transfers.
• Incremental migration relies on metadata to avoid duplicates: EdbMails supports incremental migration to avoid duplicates on re-runs. Instead of storing your full mailbox contents, it keeps a small, encrypted record of previously migrated items on your local machine. On follow-up runs, it checks that record and pulls across only new or changed messages, saving bandwidth and cutting migration time.
• Secure transfer throughout: All metadata and message content move over encrypted connections using OAuth 2.0 and TLS, so nothing is exposed in transit.

Because mailboxes are migrated using a Google Admin account rather than individual user logins, this metadata preservation applies consistently across every mailbox in a bulk migration, not just a handful of test accounts.

How to Verify Metadata After Migration

A quick check after migration goes a long way toward catching anything unexpected before users log in. Here's a practical way to do it:

• Spot-check a sample of mailboxes: Pick a few accounts with a mix of old and recent mail, and confirm that timestamps on messages match the original Gmail account.
• Compare read/unread counts: Check the unread count in a folder before and after migration. They should match, or be lower only if new mail arrived during the process.
• Open a few flagged or labelled messages: Confirm stars, labels, and categories carried over correctly and that folder structure looks the same as the source.
• Review the migration report: EdbMails generates logs and completion reports during the process, which list migrated item counts per mailbox and any items that failed to transfer, so administrators don't have to check everything manually.
• Test search and sort: Try sorting by date and searching within a date range on the migrated mailbox to confirm the results line up with expectations.

For a full breakdown of everything that gets migrated alongside metadata, including attachments, contacts, calendars, and tasks, see Migrate Google Workspace Emails, Contacts & Calendars.

Frequently Asked Questions

1. Does EdbMails change email timestamps during migration?

   No. Original sent and received timestamps are preserved exactly as they appeared in the source Google Workspace mailbox.

2. Will emails already read in Gmail show as unread after migration?

   No. Read/unread status transfers along with the message, so previously opened emails remain marked as read on the target platform.

3. Can I filter a migration based on read/unread status?

   Yes. EdbMails supports filtering by message read/unread status, along with date ranges and sender or recipient addresses, which is useful for selective or staged migrations.

4. Does folder structure stay the same after migration?

   Yes. Folder and label hierarchy from Google Workspace is mapped to the equivalent structure on the destination platform, so navigation stays familiar.

5. Is metadata preserved across all supported migration targets?

   Yes. This applies whether the destination is Office 365, on-premises or hosted Exchange Server, or an IMAP-based platform.