M&A Data Migration Guide
Understanding the complexity of migrating to nGenue during acquisitions
1. How Difficult Is Data Migration?
Work is front-loaded, but highly repeatable and much easier than migrating into a generic ETRM.
What data must be migrated?
The acquired company typically brings data from one of these sources:
- Legacy ETRM
- Homegrown tools
- Utility-provided data feeds
- SQL databases
- Excel spreadsheets (common in C&I)
Typical data categories include:
Customer & Contract Data
- Contract terms
- Pricing structures
- Rate schedules
- Volume commitments
- Contract durations
Billing Data
- Meter reads
- Usage history
- Billing cycles
- Invoice templates
- Cashout / imbalance provisions
Operational Data
- Pools
- Storage positions
- Forecasting indicators
- Nomination Configuration
- LDC integration
Historic Performance Data
- Past invoices
- Historical positions
- Backcast load models
What makes migration tricky?
The most common challenges encountered in real-world migrations include:
Inconsistent data labels
e.g., One company uses "Acct_ID" while another uses "Service_Location_ID."
Spreadsheet conversions
Many smaller natural-gas retailers rely heavily on Excel; that logic must be captured, standardized, and implemented in nGenue's structured workflows.
LDC-specific differences
Rules for imbalance tracking, cashouts, and storage differ market-by-market and often must be restructured.
Contract pricing mismatches
Legacy systems often store pricing logic in ad-hoc ways, requiring normalization.
Data quality issues
Common during M&A: duplicates, missing fields, outdated meters, orphan accounts.
How long does data migration usually take?
Most of the effort is spent on:
- Mapping legacy fields to the nGenue data model
- Standardizing billing and pricing logic
- Validating historic data accuracy
- Conducting parallel-run comparisons
Actual loading into nGenue is fast — the prep work is the heavy lift.
2. Workflow Migration: How Hard Is It to Move Operational Processes?
A simplified process as the nGenue system includes:
Most migration effort centers on mapping the acquired company's current processes to nGenue's operating model.
What must be reconfigured?
Scheduling & Nominations
- Cutover dates determined
- LDC interconnects configured
- Nomination cycles validated
Billing
- Standard billing cycles set
- C&I templates configured
- Taxes, fees, and adjustments mapped
- Cashout logic and imbalance structures tested
Pricing
- Rate structures
- Margin logic
- Customer-specific adjustments
Forecasting
- Load models rebuilt using historical data
- Weather normalization adjustment
Where do workflow issues usually appear?
Example: A retailer doing cashout reconciliation manually in Excel.
Migration uncovers hidden rules ("Why does this rate always round differently for Zone A?").
Not uncommon — tribal knowledge is a real risk during M&A.
3. Training: How Hard Is It to Learn nGenue?
The platform is natural gas-specific and intuitive, so end users do not have to learn a generic commodity workflow and adapt it for gas.
Training focuses on:
- Daily scheduler tasks
- Billing cycles and exception handling
- Forecast review and load management
- Contract creation and pricing
- Reporting and margin analysis
User types that learn nGenue easily:
- Schedulers
- Billing specialists
- C&I account managers
- Analysts
User types that need more onboarding time:
- Staff transitioning from spreadsheet-only environments
- Teams accustomed to multi-commodity platforms with bespoke back-end logic
- Groups lacking clear, up-to-date workflow documentation
Typical training timeline:
4. Parallel Run & Cutover Difficulty
Parallel runs are where errors are exposed and corrected.
Typical comparisons include:
Common mismatch sources:
- Hidden spreadsheet logic
- Bad historical data
- Wrong LDC parameters
- Legacy rounding rules
- Incorrect contract term mapping
This step is technical but predictable — and reduces risk dramatically before go-live.