The short answer
Consolidate a solar tech stack by auditing every tool against the workflow it serves, identifying the seams where humans retype data, and collapsing the sales, marketing and communication tools first. Keep design and accounting separate. Migrate new leads before historical data so nothing arriving today falls into the gap.
- 01Audit by workflow, not by tool. The question is which seams you are removing.
- 02Sales, marketing and communication is the cluster worth collapsing first.
- 03Design and accounting should usually stay specialist.
- 04Never cut over everything at once. New leads first, history second.
Nobody chooses nine tools. They accumulate: a form builder because the site needed one, a texting app because the crew needed one, a review tool after a bad month, a CRM after a lost lead. Each was reasonable, and together they produce a business where somebody retypes a customer's details four times.
The audit
List every tool with a monthly fee, then add the free ones, which are usually where the worst seams live. For each, write down four things.
| Column | Why it matters |
|---|---|
| What it does | In one sentence. If it takes three, that is a finding |
| Who uses it | Tools used by one person who left are common |
| What data it holds | This is what has to move, or be lost |
| What it connects to | Nothing, usually. That is the seam |
Then draw the workflow from enquiry to paid invoice across the top and mark every point where a human moves data between two tools. Those marks are the actual problem. The number of logins is a symptom.
What should you collapse, and what should you keep?
- Collapse: sales, marketing and communication. Forms, texting, email, calls, review requests, follow-up, pipeline. These share one dataset, the customer, and separating them is what creates most of the seams.
- Keep: design and proposal. Genuinely specialist. See how to choose solar proposal software.
- Keep: accounting. It already works and your accountant knows it.
- Decide case by case: project management. Worth collapsing in if your volume is modest, worth keeping separate if install operations are complex.
Migrating without losing a quarter
- 01
Clean the data first
Deduplicate, fix phone formats, remove test records. Bad data migrated is bad data permanently, and it is much harder to clean afterwards.
- 02
Point new leads at the new system
Before touching history. From day one, every new enquiry lands in the new place. The old system keeps running for existing deals.
- 03
Run both for a fortnight
Uncomfortable and necessary. This is when you find the automation nobody documented and the report somebody in accounts depends on.
- 04
Migrate history in batches
Active deals first, then the last twelve months, then the archive. Verify each batch before the next. Communication history often does not come across, so check.
- 05
Keep read access to the old system
For at least three months after cutover, and export a full backup before the contract ends. Access disappears the day billing stops.
The mistakes that cost the most
- 01Cutting over everything on the same day. Something breaks, and it breaks while leads are arriving.
- 02Migrating during your busy season. Do it in your quietest month, deliberately.
- 03Forgetting the integrations nobody documented. The Zap somebody built in 2023 that emails the scheduler is load-bearing and invisible.
- 04Not exporting before cancelling. The day the subscription ends, the data is gone. Export first, cancel second.
- 05Assuming communication history transfers. Contacts usually migrate; the text and call threads against them frequently do not.
What is consolidation actually worth?
The subscription saving is the smallest part and the one people quote. The real returns are elsewhere: leads that stop falling between systems, follow-up that fires because it lives with the data, and reports that are true because there is one source of truth rather than four.
At solar job values, one recovered lead a month pays for most stacks several times over. That is the number to put against the migration cost, not the difference between two subscription totals.
What if you cannot migrate yet?
Sometimes the migration is genuinely the wrong move this year: peak season, a contract with eight months left, or nobody with the time to run it. The seams can still be narrowed without replacing anything.
- 01Automate the worst seam first. Usually form to CRM, or CRM to texting. One connection removes most of the retyping.
- 02Pick one source of truth and say so out loud. When two systems disagree, everybody knows which one wins.
- 03Stop the bleeding at capture. Get every channel landing in one inbox even if the rest stays where it is. See choosing a CRM for a solar company.
- 04Document the undocumented integrations now, while the person who built them still works here.
- 05Diarise the migration for your quietest month, with a date. A consolidation with no date does not happen.
The sales, marketing and communication cluster, in one place
What the Volt system coversStop reading, start booking
Volt builds and runs the system this article describes: the site, the follow-up, the inbox and the review funnel, for $297 a month.
No contracts. Cancel anytime.
Common questions
- How many software tools should a solar company have?
- Around three for most installers: design and proposal, sales and marketing and communication, and accounting. The number matters less than how many places a human has to retype the same customer.
- When is the best time to migrate systems?
- Your quietest month, deliberately chosen, never during peak install season. Allow a fortnight of running both systems in parallel, and expect the first week to be worse than planned.
- What usually goes wrong in a migration?
- Undocumented integrations breaking, communication history not transferring, and cutting over everything at once. All three are avoided by moving new leads first and keeping the old system readable for three months.
