Haskell (The Haskell Company) — Power BI Report Server to Power BI Service migration (2019)
Contracted — countersignedFirst-pass editionHaskell (The Haskell Company) · 2019 · Project ID EPC-2019-HASKELL-PBIRS
Evidence record: Haskell (The Haskell Company) evidence record with redacted documents and SHA-256 hashes
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
EPC-reported — statement of work on file; evidence record pending. Haskell (The Haskell Company) engaged EPC Group (O'Connor Enterprise Group, Inc., doing business as EPC Group) for Power BI Report Server to Power BI Service migration — 150-hour block per EPC Group statement of work v2.0 dated January 30, 2019 (document on file; countersignature to be confirmed when the evidence record is built). Project ID EPC-2019-HASKELL-PBIRS. 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 2019, EPC Group completed Power BI Report Server to Power BI Service migration for Haskell (The Haskell Company) on Power BI Report Server (June 2017), Power BI Service, Power BI apps and workspaces, led by Errin O'Connor, EPC Group's founder and the architect named in the engagement documents (the statement of work is prepared by Errin O'Connor), addressing an on-premises report server that had to be migrated to the Power BI Service without changing existing datasets, with a workspace strategy and user adoption. The work ran through the phases the documents define: Assessment, Design, Deploy and Migrate, and Post-Deployment Support. 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: EPC-reported — statement of work on file; evidence record pending; 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 | Haskell (The Haskell Company) | document |
| Industry | Architecture, engineering and construction | document / public record |
| Engagement date | January 30, 2019 (SOW v2.0) | document |
| Work | Power BI Report Server to Power BI Service migration (150-hour initiative) | document |
| Microsoft products | Power BI Report Server (June 2017); Power BI Service; Power BI apps and workspaces | document / scope |
| Scope unit | 150-hour block per EPC Group statement of work v2.0 dated January 30, 2019 (document on file; countersignature to be confirmed when the evidence record is built) | document |
| EPC Group role | Consulting and delivery under the instrument named above | document |
| Lead architect | Errin O'Connor — the statement of work is prepared by Errin O'Connor | document |
| 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 | EPC-reported — statement of work on file; evidence record pending; Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) | Evidence Center convention |
| Evidence record | evidence record pending (CC builds it from the document on file) | — |
| External source | none published yet | — |
| Project ID | EPC-2019-HASKELL-PBIRS | EPC Group |
What the document states
EPC Group Statement of Work v2.0 (January 30, 2019): discovery and assessment of the Power BI Report Server environment; migration plan; Power BI Service branding and theme development aligned with Haskell's guidelines; app and workspace strategy; migration support without changes to existing datasets; Power BI training and adoption; a Power BI report template (.pbix) following branding guidelines. Phases: Assessment, Design, Deploy and Migrate, Post-Deployment Support.
Starting environment (EPC-reported, first pass)
An engagement of this type begins with a Power BI Report Server environment (June 2017 release) with its reports and dashboards, source data systems, and an organization moving to the Power BI Service with branding, app and workspace, and training requirements. 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 on-premises report server that had to be migrated to the Power BI Service without changing existing datasets, with a workspace strategy and user adoption.
EPC Group's responsibility
Discovery and assessment of the Report Server environment, a migration plan, Power BI Service branding and theme development, an app and workspace strategy, migration support for existing reports and data, and training and adoption — as the statement of work describes.
Technical decisions (EPC-reported, first pass)
The decisions this kind of engagement turns on are which reports migrate as-is versus are redeveloped, the workspace and app structure, gateway and data-source strategy, branding and report-template standards, and the training approach. The decisions actually taken for Haskell will be stated here from the project record.
Delivery sequence (EPC-reported, first pass)
Typical sequence for this engagement type: assessment and discovery → design → deploy and migrate → post-deployment support and training. 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 source document is on file with EPC Group; CC builds the evidence record (redacted images, SHA-256, transcript) before this page leaves first-pass status. 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)
- Inventory every report and its data source before promising a migration date.
- A report template (.pbix) with the organization's theme is the cheapest adoption tool there is.
Related service
Power BI Report Server to Power BI Service 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.