Google Workspace & Microsoft Email Migration Specialist

Overview We are looking for an experienced email migration specialist to move historical email from an existing POP-based setup into a Google Workspace environment that is already up and running. This is a data migration job only. We are handling Google Workspace licensing, mailbox creation, DNS, authentication, and day to day tenant administration on our end. Fixed price: $500 Current Environment • Roughly 60 GB of email data • Three active mailboxes total • One shared or general mailbox • Two individual mailboxes • Historical mail may live on the current mail server, on individual workstations, inside Outlook profiles, and/or in PST files • Existing folders and nested subfolders • Existing aliases and forwarding rules Scope of Work The contractor will handle: • Reviewing the current POP email setup • Taking a full backup of the POP environment before any work starts • Locating where the complete historical email actually lives • Exporting all available email data • Loading that data into the matching Google Workspace mailboxes • Keeping the existing mailbox to user mapping intact • Keeping the existing folder and subfolder hierarchy intact • Keeping messages in the same folders they are in today • Migrating Inbox, Sent, Drafts, archived mail, and any custom folders • Migrating mail stored locally in Outlook or in PST files • Identifying and documenting existing forwarding rules and aliases • Making sure mailbox, alias, and forwarding behavior stays consistent after the move • Validating the finished migration All accessible historical email inside the identified mailboxes needs to be migrated, including anything sitting in subfolders. Folder Preservation (Important) The existing folder structure needs to stay as close to identical as the technology allows. The contractor must not: • Dump all historical email into a single generic folder • Flatten nested folders • Merge unrelated folders together • Rename folders without getting approval first • Migrate only the Inbox and leave out local or archived folders Google Workspace uses labels instead of traditional folders, so labels need to be mapped in a way that keeps the same visible parent folder and subfolder organization. Anything that cannot be migrated, whether a folder or an individual message, needs to be flagged and documented before we call the project done. Forwarding Rules and Mailbox Mapping Every existing mailbox needs to keep pointing at the same user or function after the migration. The contractor will: • Document all current mailbox mappings • Document all aliases • Document all forwarding rules and their destinations • Confirm nothing was missed on mailboxes, aliases, or forwarding destinations • Hand over whatever we need to verify or rebuild those settings in Google Workspace • Confirm mail landed in the correct destination mailbox We will take care of the actual Google Workspace configuration where that is needed. Protecting the Source Data The contractor may not delete or alter any of the original email data. The current source environment, PST files, Outlook profiles, and local mail data all need to stay untouched until the migration is finished and signed off on. Since POP mail is often stored locally rather than on the server, the relevant workstations and mail applications need to be checked as part of this work. Validation Once the migration is done, the contractor needs to confirm: • All three mailboxes came across • Historical email is accessible • Folder and subfolder structures are in place • Messages sit in the correct folders • Sent mail is present • Attachments open properly • Message dates and sender details are retained • Source and destination message counts line up reasonably well • Any failed or skipped items are written up Deliverables • Full migration of all accessible historical email • Folder and subfolder structure preserved • Data mapped correctly to each destination mailbox • Inventory of aliases and forwarding rules • Side by side comparison of source versus destination mailboxes and folders • List of anything that could not be migrated • Confirmation that the original source data is still intact Out of Scope The consultant is not responsible for: • Buying Google Workspace licenses • Creating the Google Workspace tenant • Creating user accounts • General Google Workspace configuration • DNS or MX record changes • SPF, DKIM, or DMARC setup • Mobile device setup • End user training