Superior Court of California, County of Amador — Exchange 2013 to Exchange 2019 migration, AD Connect resolution, domain-controller migration (2024)

Contracted. Superior Court of California, County of Amador engaged EPC Group (O'Connor Enterprise Group, Inc., doing business as EPC Group) for Exchange 2013 to Exchange 2019 migration, AD Connect resolution, domain-controller migration — per Purchase Order 4500147661. Project ID EPC-2024-AMADOR-EX19. 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 2024, EPC Group completed Exchange 2013 to Exchange 2019 migration, AD Connect resolution, domain-controller migration for Superior Court of California, County of Amador on Exchange Server 2019, Active Directory, Entra Connect (AD Connect), Windows Server 2019, led by EPC Group's senior architects addressing an unsupported or soon-unsupported Exchange version, directory synchronization errors that block hybrid readiness, and infrastructure on operating systems past mainstream support. 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: Contracted; 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

What the document states

Purchase Order 4500147661 (May 30, 2024): 'Initiative for Migration from Microsoft Server Exchange 2013 to Microsoft Exchange 2019 Server, Resolution of AD Connect Issues, and Migration of the domain controller from 2012 to 2019.'

Starting environment (EPC-reported, first pass)

An engagement of this type begins with an Exchange Server 2013 environment at or near end of support, Active Directory and AD Connect synchronization state, mailbox and shared-mailbox inventory, public folders and resource mailboxes, mail-flow dependencies (MX, connectors, relay), backup and retention obligations, and any domain-controller operating systems due for replacement. 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)

An unsupported or soon-unsupported Exchange version, directory synchronization errors that block hybrid readiness, and infrastructure on operating systems past mainstream support.

EPC Group's responsibility

Assessment of the existing Exchange and Active Directory estate, migration design, build of the target Exchange 2019 servers, mailbox and public-folder moves, AD Connect remediation, domain-controller migration where contracted, cutover support and knowledge transfer.

Technical decisions (EPC-reported, first pass)

The decisions this kind of engagement turns on are coexistence versus cutover sequencing, server sizing and database layout for Exchange 2019, the order of AD Connect remediation relative to mailbox moves, certificate and namespace planning, and decommissioning criteria for the legacy servers. The decisions actually taken for Amador Superior Court will be stated here from the project record.

Delivery sequence (EPC-reported, first pass)

Typical sequence for this engagement type: assessment and inventory → target build and validation → pilot mailboxes → batched mailbox moves → mail-flow and client cutover → legacy decommission and documentation. Dates and acceptance for this engagement will be stated from the project record.

Results

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/amador-superior-court-exchange-2019-active-directory-migration-2024 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).

Lessons for similar organizations (EPC-reported)

• Fix directory synchronization before moving a single mailbox; most 'migration' failures are identity failures.
• Inventory public folders, resource mailboxes and relay dependencies early — they are the long pole in small environments.
• Keep the legacy servers until mail flow, mobile devices and backup have been validated on the new platform.

Related service

Exchange and 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.