How ESCO workflows are usually organized
Typical ESCO delivery models combine:- Utility portal retrieval by analyst teams
- Spreadsheet-based QA and client reporting
- Mixed billing and meter datasets from many client portfolios
- Separate tools for issue tracking, billing exceptions, and exports
How ESCO source data maps to Nectar
| Common ESCO source concept | Nectar destination | Migration notes |
|---|---|---|
| Client account hierarchy | Company | Create one company per client portfolio. |
| Property/building list | Site | Preserve existing site IDs for continuity. |
| Utility account tracker | Account | Keep account number + provider as key fields. |
| Meter register or meter list | Meter | Map commodity and units during import QA. |
| PDF bill archive + billing table | Bill + usage data | Import history first, then automate future intake. |
| Exception tracker | Data Quality queue | Replace manual issue lists with structured triage. |
Recommended onboarding plan
Segment your migration by client tier
Start with one high-volume client, one mid-volume client, and one long-tail client to prove the operating model.
Normalize source exports
Use Nectar templates to standardize column names, units, and date formats across client datasets.
Load structure and history
Create companies, sites, accounts, and meters, then import historical bills and usage for validation.
Turn on automated collection
Use connections, uploads, and magic links to reduce manual collection effort.
What improves in Nectar
- Lower analyst time spent on repetitive monthly data prep
- Better auditability with record-level lineage and reconciliation
- Faster onboarding for new client portfolios
- More consistent outputs for sustainability and finance reporting
Features to evaluate in Nectar
Compared with many ESCO baseline workflows, Nectar can add:- Native magic link flows for client data capture
- Automated utility collection without manual portal checks each cycle
- Built-in anomaly and completeness monitoring
Nectar support during migration
Nectar helps your team build a repeatable migration factory:- Client-by-client mapping and rollout sequencing
- Validation templates and reconciliation checkpoints
- Operational playbooks for account managers and analysts