In energy, the premise outlasts the customer, so migration keeps meters, service addresses and program enrollments attached to locations as occupants come and go.
Energy and utility migrations tend to involve customer data spread between a billing platform, a program enrollment tool, spreadsheets used by commercial account managers, and work order history in an older field system. We bring the relationship and service layers into Salesforce while billing remains the system of record for rates, usage and charges. Premises and service points are modeled separately from the people and businesses responsible for them, so a move-out or change of ownership does not erase history. Program enrollments, rebates and interconnection requests carry their status and dates, which keeps regulatory and program reporting continuous across cutover.
The central problem in energy data is that the location outlives the customer. A premise, meter or site stays in place while occupants, owners and billing accounts change, so migrating customers as simple accounts loses the history that explains a site's service record. Commercial and industrial clients add hierarchy, with many sites under one parent and different contacts for energy management, billing and operations. Utilities also report to regulators and program administrators on enrollments, complaints and outcomes, which means historical records must remain reportable after the move. Field work history matters too, because crews need past visits and equipment details at a site before they arrive.
Service addresses, meters and service points are loaded as their own records and linked to accounts through dated relationships. When occupants change, the premise keeps its full service and program history, and the new customer starts with a clean relationship rather than inheriting the previous occupant's cases, preferences or payment arrangements. Dated relationships also answer the common question of who was responsible for a site at a given point.
Efficiency programs, demand response enrollments, rebate applications and incentive payments often sit in a separate tracking tool or spreadsheet. We migrate them with status, dates and measure details so program managers keep continuous reporting for administrators and regulators across the transition, and customers are not asked to reapply for something already approved. Measure-level detail is kept wherever evaluation studies depend on it.
Large customers with many sites need parent accounts, site-level records and role-specific contacts. We rebuild that hierarchy from billing data and account manager spreadsheets, reconcile it with key account teams, and attach open opportunities, contracts and service requests to the correct level so nothing is orphaned at a site nobody manages. Billing contacts and site operations contacts are recorded separately because they call about different problems.
Past inspections, installations and repair visits are loaded against the site and asset rather than the customer, so technicians see what was done at a location. Where the legacy field system held photos or checklists, we keep references or attachments that remain useful for future crews working on the same equipment. Open work orders are migrated separately with their scheduled dates so no committed visit is dropped.
We begin with the billing and operations teams to agree on identifiers, because account numbers, premise IDs and meter numbers often mean different things in different systems. Premises and assets load first, then accounts and contacts, then enrollment and work history that depends on both. Each test load is reconciled against the billing platform's counts by customer class and against program reports. Customer service, program and field leads each review a sample of their own records. Cutover is planned outside peak weather and storm seasons, with a short freeze on edits in the legacy tools during the final load.
Account numbers, premise IDs and customer class are extracted for matching and loaded as reference data, while rates, usage and billing remain owned by the billing platform.
Meter identifiers and install dates are carried onto asset records so service history lines up, without copying interval usage data that belongs in the meter system.
Historical work orders and equipment attributes are mapped to sites and assets, and ongoing jobs continue to sync once the new integration is live after cutover.
Some asset, location and grid information is sensitive from a security standpoint. Decide which details belong in Salesforce at all, restrict access to operations roles, and avoid loading data that raises exposure without helping service or sales teams do their jobs.
Complaint logs, program results and customer protection records may be subject to regulatory reporting. Confirm with your regulatory team which history must remain reportable, migrate it with original dates, and validate that reports built in Salesforce match what was previously filed.
Accounts flagged for medical necessity, life support equipment or payment assistance carry obligations around disconnection and communication. Migrate those flags with their source and review date, restrict visibility, and test that they display wherever representatives make decisions affecting that customer.
Client names are anonymized.
Usually they stay out. Former occupants with no open balance, complaint or program obligation add little value and increase the personal data you hold. We keep premise history intact and load prior customers only where there is a reason, such as an open case, a pending rebate or a regulatory retention requirement your team confirms.
It can once it is reconciled. We compare enrollments, measures and incentive amounts by program and period against the reports previously sent to program administrators. Differences are resolved before the final load, and any record corrected during cleanup keeps a note about what changed and why, so auditors can follow the trail later without hunting through email.
No. Operational technology such as outage management and grid control stays separate. At most, Salesforce may later receive outage notifications to inform customer service. The migration focuses on customer relationships, service requests, programs and field history, which is where legacy CRM tools and spreadsheets usually hold the data that needs a better home after the old tools are retired.
Key account managers review their hierarchies in a sandbox before the final load, confirming parent accounts, sites and contacts. We freeze edits to those accounts briefly, load the final extract, and have the same managers spot-check their largest customers on the first day. Any site missing from the hierarchy goes onto a tracked fix list rather than being patched informally.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.