Confirm the path for the existing installation before creating anything new
If an SMA portal change concerns your existing solar installation, first establish its actual communication equipment, country and official migration notice. Ask SMA or the authorized installer whether the system follows an automatic migration cohort, an applicable qualified manual route or a legacy exception. Do not create a duplicate site, delete the Classic installation or buy hardware merely because the portal looks different. Keep the same installation and owner clearly identified throughout the review.
SMA’s current migration FAQ describes country- and system-dependent automatic moves, including Webconnect and Sunny Home Manager 2.0 systems. It separately identifies legacy exclusions. The answer is therefore not that every installation must be manually recreated by its homeowner. This guide concerns a platform transition for an existing owner. Our monitoring ownership-transfer guide covers the different problem of obtaining legitimate access after buying a home; a portal migration should not be used to bypass that process.
Identify the communication architecture, not just the panel brand
Use the installation file and existing authorized account to record the actual inverter and system-management or communication equipment. Ask the installer to reconcile missing or inconsistent identity information. A household describing its system only as SMA may not know which part communicates with the portal. Keep the system identifier and architecture together so support can address the correct installation without relying on a screenshot of a generic dashboard.
SMA’s FAQ names Sunny WebBox, Cluster Controller, Inverter Manager and Sunny Home Manager 1.0 as systems not included in the described migration. If one appears in your records, ask for the actual supported path and limitations. Do not turn the exception into an automatic hardware-replacement recommendation. Nor should an older release note about a hardware-conversion project be treated as the same procedure as today’s automatic portal migration. The actual equipment and current support response control.
Keep automatic migration and the qualified manual chapter distinct
The selected SMA manual chapter describes moving an existing Sunny Home Manager 2.0 system and requires a System administrator role in Classic and an Installer role in ennexOS. That is a specific route with prerequisites, not a generic homeowner workaround for any legacy installation. Have the authorized provider establish whether it applies. Do not borrow an installer login, elevate access informally or select a new-system workflow simply because a migration option is unavailable.
Keep a record of the route SMA confirms and who is responsible for any action. If the official notice describes an automatic move, ask what confirmation to expect rather than initiating a separate manual project. If qualified action is actually required, request a scope tied to the existing system and accepted prerequisites. This article performs no migration, creates no account, changes no permission and reproduces no configuration steps that could detach devices or duplicate the installation.
Separate lifetime energy from detailed performance curves
SMA’s FAQ distinguishes transferred lifetime energy data from the recent performance curves moved at migration. It specifies the last 60 days for those curves and describes older Classic access only as temporary. Do not promise that every historical interval will appear at the same detail forever or invent a date when old access ends. Ask support which records remain available for the actual system and which limitations need documenting before the transition.
Use the monitoring-record export guide for preserving an authorized native record without relabeling gaps as measured zeros. Here the separate decision is what the migration itself retains. Keep the date range, data type and resolution attached to any missing-history question. A lifetime total matching expectations does not prove that all earlier curves transferred, and a missing curve does not by itself establish lost solar generation.
| Evidence | Question for SMA or the authorized provider | Not established alone |
|---|---|---|
| Actual system architecture | Which migration route applies? | All SMA installations follow one process |
| Official notice and country | Is this installation’s move confirmed? | Another owner’s date applies |
| Authorized roles | Who can complete the specific accepted route? | A homeowner may borrow installer access |
| Energy totals and curves | Which history types and periods remain? | Every interval is retained at full detail |
| Fresh reporting and alerts | What remains to investigate after the move? | Portal access proves electrical health |
Read dated updates without extending their scope
The reviewed SMA product page includes both migration FAQs and dated release notes through September 2026. Its newer registration and export information should not be used to make an unrelated promise about every existing system’s migration or history. If an older FAQ and a later instruction appear inconsistent for your intended action, preserve the exact references and ask support to reconcile them before proceeding. Do not silently select whichever statement makes a preferred outcome sound certain.
Keep country-specific tariffs, grid-management functions and product availability out of a general homeowner migration claim. A feature described for Germany or another listed market is not proof that it applies to a United States residence. Likewise, a new dashboard feature is not an engineering reason to replace working hardware. The service proposal should identify the actual migration need and exclusions without bundling speculative savings, utility benefits or a universal upgrade requirement.
Illustrative scenario: a new appearance prompts an unnecessary duplicate-site plan
Imagine an existing owner sees unfamiliar portal navigation and proposes registering the same array as a new installation. This is an illustrative scenario, not an account we accessed. The owner first gives the authorized provider the existing site identity, actual communication equipment and official notice. Support establishes which transition applies and explains what should remain associated with the original installation before anyone changes the site structure.
The owner records any differences in history or features as specific questions rather than rebuilding the site to make the dashboard resemble the old one. If a needed role is absent, the case follows the official support process instead of shared credentials. The example promises neither flawless migration nor uninterrupted history. Its useful outcome is continuity of the correct installation and a clear assignment of the remaining platform questions, without unauthorized account or device changes.
Verify reporting separately from migration completion
After the actual transition is confirmed, review the correct site and device identities, available owner access, reporting timestamp and relevant notifications with support. Record which history and features are present and which limitations remain. A confirmation email and a visible dashboard are useful milestones, but they do not settle a production alert or certify the electrical condition of the array. Keep any such concern open under its own service scope.
If reporting remains stale, use the communications guide only where its separate network-change circumstances actually fit, or obtain the appropriate manufacturer investigation. Do not reset inverters, change grid parameters, open live-DC equipment or approach rooftop components to recover a portal view. Preserve the migration case, accepted route, completion confirmation and unresolved findings. Platform continuity is the goal here, not a claim of output, savings, warranty renewal or repaired hardware.
Frequently asked questions
Should every owner recreate a site? No. Does every SMA architecture follow the described automatic migration? The FAQ identifies exclusions. Is the selected manual route available without its roles and Home Manager2.0 scope? Do not assume so. Will every detailed historical interval transfer? Do not promise that. Does a changed dashboard prove lost production? No.
Should I delete Classic records? No deletion is authorized here. Can I borrow installer credentials? No. Does a migration notice require buying hardware? Obtain the actual supported explanation. Does this article apply German tariff features to a US home? No. Who resolves conflicting instructions? SMA and the authorized provider for the actual installation and current route.