migration
Migrate solar operations from spreadsheets
Separate records, formulas, approvals, workflow, reporting, and history before moving spreadsheet-controlled operations into governed data.
01
Understand what each workbook controls
A workbook may act as a database, workflow, calculator, approval log, report, and archive. Each responsibility needs a defined destination.
- Workbook inventory and scope boundaries
- Record and formula map
- Cleanup and data validation
- Acceptance criteria, cutover, and rollback
02
Records and decisions to map
The assessment starts by naming the records, owners, approvals, and recurring decisions that make this operating area work.
- Workbooks, tabs, owners, and users
- Rows, identifiers, relationships, and duplicates
- Formulas, statuses, approvals, and reports
- History, attachments, reconciliation, and exceptions
03
Configuration and system boundaries
Configuration scopeThese areas are evaluated as configuration or integration scope. Exact behavior is confirmed before implementation.
- Operational records versus analysis files
- Required history and archive
- Formula replacement or retention
- Freeze, cutover, and rollback plan
04
Questions for the workflow assessment
Use these questions to expose hidden ownership, exception, and data requirements before the rollout is scoped.
- Who owns each workbook?
- Which formula changes a decision?
- What history is required?
- How will imported totals and samples be approved?
Review record
Sources and related pages
Next step
Map this workflow against the way your team works today.
Bring your current systems, records, owners, approvals, and exceptions. The assessment will identify what needs configuration, validation, or a staged handoff.