Prairie View A&M University (Texas A&M University System) — Gmail to Exchange Online migration services (2020)
Documented — public procurement recordFirst-pass editionPrairie View A&M University (Texas A&M University System) · 2020 · Project ID EPC-2020-PVAMU-M365
Evidence record: Prairie View A&M University (Texas A&M University System) evidence record with redacted documents and SHA-256 hashes
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Documented — public procurement record. Prairie View A&M University (Texas A&M University System) engaged EPC Group (O'Connor Enterprise Group, Inc., doing business as EPC Group) for Gmail to Exchange Online migration services — 395-hour block in two line items per Purchase Order AB0548197, with the statement of work attached. Project ID EPC-2020-PVAMU-M365. The engagement was completed and paid in full (EPC Group accounts-receivable record).
First-pass edition. The facts in the verification line and the project-facts table come from the documents named there. The engagement narrative below is written by EPC Group from the engagement type and the documented scope, is marked EPC-reported, and is pending review by Errin O'Connor. Delivery status comes from EPC Group's accounts-receivable record as stated by Errin O'Connor on 2026-10-15; no other result is claimed that the documents or project records do not support.
Summary
In 2020, EPC Group completed Gmail to Exchange Online migration services for Prairie View A&M University (Texas A&M University System) on Exchange Online, Microsoft 365, led by EPC Group's senior architects addressing a university consolidating on Microsoft 365 for single identity, Teams and SharePoint adoption, and retention and eDiscovery in one platform. The work ran through EPC Group's delivery lifecycle as EPC Group describes its engagements: assess, modernize, govern, operate, enable. The client accepted the deliverables and paid in full, per EPC Group's accounts-receivable record; EPC Group reports that its objectives for the engagement were met. Verification: Documented — public procurement record; Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported). What the documents establish, and what they do not, is stated in Evidence and limitations below.
Project facts
| Field | Value | Source |
|---|---|---|
| Client | Prairie View A&M University (Texas A&M University System) | document |
| Industry | Higher education (public university, Texas) | document / public record |
| Engagement date | July 9, 2020 | document |
| Work | Gmail to Exchange Online migration services (395-hour block) | document |
| Microsoft products | Exchange Online; Microsoft 365 | document / scope |
| Scope unit | 395-hour block in two line items per Purchase Order AB0548197, with the statement of work attached | document |
| EPC Group role | Consulting and delivery under the instrument named above | document |
| Lead architect | EPC Group senior architects (the published instrument does not name the lead; EPC-reported) | EPC-reported |
| Delivery status | Completed; invoiced and paid in full. Source: EPC Group's accounts-receivable record (paid invoices on file, not published because they carry commercial terms), stated by Errin O'Connor on 2026-10-15. EPC Group treats payment as acceptance; no client acceptance record is published for this engagement. | EPC AR record (EPC-reported) |
| Verification class | Documented — public procurement record; Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) | Evidence Center convention |
| Evidence record | https://www.epcgroup.net/evidence/prairie-view-am-university-google-workspace-microsoft-365-migration-2020 | — |
| External source | https://www.pvamu.edu/psca/wp-content/uploads/sites/88/AB0548197.pdf | — |
| Project ID | EPC-2020-PVAMU-M365 | EPC Group |
What the document states
Purchase Order AB0548197 (July 9, 2020), hosted by the university on pvamu.edu: 'Project Initiation Invoice | Invoice # 1: Block Purchase of 395 hour of Gmail to Exchange Online Migration Services', two line items, supplier 'EPC GROUP O'CONNOR ENTERPRISE GROUP DBA', with 'EPC Group SOW' attached.
Starting environment (EPC-reported, first pass)
An engagement of this type begins with a Google Workspace mail environment, the identity model (Google identity versus Entra ID and directory synchronization), mailbox and calendar inventory including resource calendars and delegated mailboxes, Google Groups, retention and eDiscovery requirements, and the academic calendar constraints of a university. The specific inventory for this engagement is held in EPC Group's project records and will replace this paragraph when published.
Business problem (EPC-reported, first pass)
A university consolidating on Microsoft 365 for single identity, Teams and SharePoint adoption, and retention and eDiscovery in one platform.
EPC Group's responsibility
Migration planning, coexistence and identity design, DNS and mail-routing cutover planning, pilot and wave execution, exception handling, reconciliation and support during cutover, within the contracted block of hours.
Technical decisions (EPC-reported, first pass)
The decisions this kind of engagement turns on are coexistence approach during migration, handling of Google-specific objects (labels, delegated mailboxes, groups, calendar resources), migration tooling and throttling, retention mapping into Exchange Online, and what was deliberately left behind. The decisions actually taken for Prairie View A&M will be stated here from the project record.
Delivery sequence (EPC-reported, first pass)
Typical sequence for this engagement type: discovery → identity and coexistence design → pilot cohort → migration waves by college or department → MX cutover → Google read-only window → close-out and reconciliation. Dates and acceptance for this engagement will be stated from the project record.
Results
| Metric | Baseline | Observed result | Period | Source | Verification class |
|---|---|---|---|---|---|
| Scope delivered against the instrument | as contracted | Completed; invoiced and paid in full | engagement period | EPC AR record (paid invoices on file; not published) | Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) |
| Client acceptance | — | Deliverables accepted; EPC Group's objectives met | close-out | payment in full + EPC-reported | Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) |
| Primary technical outcome (migration completeness, platform live, deliverable detail) | pending | pending project record | — | project record | pending |
| Service interruption during cutover (where applicable) | planned window | pending | cutover | cutover log | pending |
Completion, acceptance and payment are stated from EPC Group's records; the technical rows stay pending until the project record is published. No figure is invented.
Client perspective
The client accepted the deliverables and paid every invoice in full. No client quotation is published on this page; where a client has given a written statement or a review, it is linked from the evidence record.
Evidence and limitations
The evidence record at https://www.epcgroup.net/evidence/prairie-view-am-university-google-workspace-microsoft-365-migration-2020 publishes the document(s) with redacted page images and SHA-256 hashes. The instrument establishes the client, the supplier, the service and the date as stated above. It does not by itself establish delivery dates, volumes, acceptance or outcomes; those require the project records referenced in the Results table. Completion and payment in full are established by EPC Group's accounts-receivable record (paid invoices on file; not published because they carry commercial terms). The university-hosted copy of the purchase order provides an external check.
Lessons for similar organizations (EPC-reported)
- Identity first: the mail migration is only as clean as the directory it lands in.
- Calendar resources and delegated mailboxes are where university migrations slip; inventory them in week one.
- Communicate wave schedules by college and keep Google read-only for a defined window.
Related service
Google Workspace to Microsoft 365 migration ·Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-15 · Substantively updated: 2026-10-15.