How to Migrate from Excel to a Solar CRM in

The decision to switch from Excel to a solar CRM is not the hard part. The hard part is the Monday morning after you have decided, when you realise you have 400 rows in a Google Sheet, three different column naming conventions across three sales reps' files, and a team that will resist learning new software unless the transition is completely painless.

This guide makes the migration painless. The 3-Day Excel Migration Sprint is a practical, hour-by-hour plan for taking your solar EPC from a messy spreadsheet to a fully configured CRM over one weekend, without disrupting a single live deal.

The framework is built from the actual migration process QuickEstimate uses with Indian EPCs onboarding from spreadsheets. Most complete it in a single weekend. A few do it in one Saturday. Here is exactly how.

If you have not yet decided whether to switch, read the Solar CRM vs Spreadsheet comparison first, it includes the ₹ ROI calculation that makes the business case. If you have already decided, read on.

Who This Migration Guide Is For

This guide is written for Rohit: a scaling EPC owner in a city like Surat, Pune, or Jaipur, running a team of 5–15 people, with a messy but functional Google Sheet that the team updates inconsistently. You have probably already tried one CRM that did not stick. You do not want that to happen again.

The migration principles apply regardless of which CRM you choose. The specific import steps reference QuickEstimate because that is the solar-specific CRM with Indian context, PM Surya Ghar subsidy fields, WhatsApp integration, and an Android-first interface built for field teams. The conceptual framework works for any tool. According to JMK Research's 2025 India solar SMB report, the average Indian EPC that switches from spreadsheets to a CRM recaptures 3–5 lost leads per month within the first 90 days, at a median deal size of ₹1.5 lakh, that is ₹4.5–7.5 lakh per month in additional revenue. And per MNRE's PM Surya Ghar portal, over 1.4 crore households have registered, creating a pipeline of demand that only organised EPCs with scalable tracking systems can fully service.

Before the Sprint, What to Prepare

Before Friday, spend 30 minutes on preparation. This saves hours of confusion during the sprint itself.

Gather all your lead sources. Your data is probably in more than one place: a master Google Sheet, individual Excel files on sales reps' laptops, WhatsApp contacts (saved as names only), and possibly IndiaMART CRM notifications. List every source. You will consolidate them on Friday.

Decide on your canonical fields. Every CRM needs a minimum set of fields for each lead. For Indian solar, the canonical set is: Lead Name, Phone, Email (optional), Source, Stage, System Size (kW), Property Type (residential/commercial/industrial), Address (rough), PM Surya Ghar Eligible (yes/no/unknown), Owner, Last Contact Date, Notes.

Assign a migration owner. One person is responsible for the Friday data work. For most EPCs, this is the owner or the ops manager. Sales reps are not involved until Sunday onboarding. Their job is to keep selling; your job is to build the system they will use.

Friday: Export and Data Cleaning

Friday evening is the unglamorous foundation of the entire migration. Skipping or rushing it is the single most common reason CRM migrations fail. Dirty data, duplicate entries, inconsistent stage names, missing phone numbers, stale leads mixed with live ones, breaks automation and erodes rep trust in the system before it has a chance to prove itself.

Step 1: Export All Lead Sources to One CSV

Open every file where leads currently live. Export each as CSV. If leads are on individual reps' phones or personal spreadsheets, ask them to share the list by WhatsApp or email, do not try to do this in real time during the sprint.

Create one master CSV with these exact column headers (capitalised exactly as shown, because your CRM's import mapper will look for these field names):

Lead Name, Phone, Email, Source, Stage, System Size kW, Property Type, Address, PM Surya Ghar Eligible, Owner, Last Contact Date, Notes

Step 2: Clean the Data, Five Passes

Run through the master CSV five times, one issue per pass:

Pass 1, Duplicates. Search for duplicate phone numbers. Keep the most recent record; delete the older one. In Google Sheets, use =COUNTIF($B$2:$B$1000, B2) in a helper column to flag phones that appear more than once.

Pass 2, Stage standardisation. Your sheet probably has stages named "new lead", "new", "NEW", "prospecting", and three other variants. Replace all of them with the exact 7-stage names from the solar pipeline stages framework: New, Contacted, Site Survey Scheduled, Site Survey Done, Proposal Sent, Negotiation, Closed Won, Closed Lost.

Pass 3, Source standardisation. Consolidate your source names: WhatsApp Organic, WhatsApp Ad, Facebook Ad, IndiaMART, Referral, Walk-in, Other. This lets your CRM's reports sort by source correctly.

Pass 4, Stale lead culling. Any lead with no contact in 90+ days and Stage = New or Contacted is probably dead. Move these to a separate tab called "Archive" rather than deleting them, you will want to run a reactivation campaign later. Delete them from the import CSV.

Pass 5, Phone number formatting. Indian mobile numbers should all be 10 digits (no country code needed for WhatsApp integration). Remove leading zeros, spaces, and dashes. A formula like =TEXT(B2,"0000000000") standardises formatting.

By the end of Friday evening, you should have one clean master CSV with only active leads, standardised fields, and no duplicates. Back it up to Google Drive.

Saturday: Import, Configure, and Test

Saturday morning is when the CRM comes alive. The import itself takes 10–15 minutes if the Friday data is clean. The rest of the day is configuration.

Step 1: Create Your QuickEstimate Account and Team

Sign up at quickestimate.co. Use your business email. Add your company name, your DISCOM region (this configures default net-metering timelines for your area), and your business logo (this appears on every proposal PDF).

Add your team members under Settings → Team. Each sales rep gets their own login. Assign them their default territory or lead source if you have geographic splits.

Step 2: Import Your Clean CSV

Go to Leads → Import → CSV Upload. Map your CSV columns to the CRM fields. The standard mapping for the 12-column template above is direct: "Lead Name" → Name, "Phone" → Phone, "Source" → Source, "Stage" → Stage, and so on.

QuickEstimate's import mapper auto-detects column names that match its field labels. Any column it does not recognise goes to a "custom field" bin, review these manually before completing the import.

After import, do a spot check: open 5 random leads and confirm the data looks correct. Check that stages were imported correctly (your standardised stage names should map cleanly). Check that owners are assigned.

Step 3: Configure Your Pipeline Stages and SLA Timers

Go to Pipeline → Settings. Confirm the 7 stages are present. Set dwell-time alerts for each stage using the benchmarks from our solar pipeline stages guide:

• New: alert after 3 days
• Contacted: alert after 7 days
• Site Survey Scheduled: alert after 7 days
• Site Survey Done: alert after 3 days (proposal should go out fast)
• Proposal Sent: alert after 7 days
• Negotiation: alert after 14 days

When a lead exceeds its stage SLA, the pipeline card shows a red clock. This is your daily morning check, 5 minutes to review all red cards and assign next actions.

Step 4: Configure the Proposal Generator

This is the QuickEstimate feature that saves the most time post-migration. Go to Proposals → Settings and configure:

• Your company branding: logo, colours, address, GST number
• Your standard panel and inverter options with pricing
• PM Surya Ghar subsidy slabs (these are pre-filled from pmsuryaghar.gov.in but you can override with your state's current rates)
• Your terms and warranty text

Once configured, any rep can create a full proposal in under 60 seconds from a lead card, system size in, PDF out. See our guide on how to write a solar proposal for what the best proposals include.

Step 5: Run One End-to-End Test Deal

Before Sunday, create a test lead (use a dummy name), run it through every stage from New to Proposal Sent, send a test proposal to your own WhatsApp number, and confirm it looks right. Fix any configuration issues now, while there is no pressure.

Sunday: Team Onboarding in 60 Minutes

Most CRM adoptions fail because training is either too long (sales reps lose interest) or too short (reps do not know how to do the basics and revert to WhatsApp). The 60-minute Sunday session hits the sweet spot.

1. 1

   Minutes 0–15: "This is your pipeline"

   Show each rep their own leads on the screen. Do not show a blank demo pipeline, show their actual data. This immediately makes the tool feel real, not theoretical. Walk through the 7 stages and confirm each rep understands the exit criteria for each stage they own deals in.

2. 2

   Minutes 15–35: Three core tasks

   Train on exactly three things: (1) how to add a new lead from WhatsApp in 20 seconds, (2) how to advance a lead's stage and log a next action, and (3) how to create and send a proposal. That is it. Do not train on reports, settings, or advanced features, they can wait.

3. 3

   Minutes 35–50: Each rep does it live

   Have every rep add one real lead from their phone right now, advance one existing lead's stage, and send a test proposal. Watching is not learning, hands on the phone is learning. Fix any confusions in real time.

4. 4

   Minutes 50–60: Monday morning ritual

   Explain the new morning routine: open the app, check red cards (overdue actions), confirm or update next actions for each. The entire team does this together for the first two weeks, then each rep does it independently. You are not training software, you are training a habit.

Comparison: Migration With vs Without the Sprint Framework

The First Week After Migration, What to Expect

Monday will feel slow. Reps will be slightly hesitant, occasionally asking "can I just check the old sheet?" Say no. By Wednesday, the morning review will be faster than it ever was with the spreadsheet. By Friday, the red-card system will have surfaced at least one lead that would have been forgotten.

CEEW's 2025 Indian solar market report notes that Indian solar businesses adopting structured CRM tools show improved customer follow-up compliance within two weeks, an outcome that compounds over quarters as follow-up habits become default behaviour, not exceptional effort.

The Mercom India Q1 2026 tracker shows residential rooftop solar growing at 38% year-on-year in FY2027. The EPCs capturing that growth are not doing it on spreadsheets. They are doing it with tools that make their teams faster, their proposals sharper, and their pipelines visible.

For context on where India's solar market is heading, see our solar business trends report and the PM Surya Ghar vendor registration guide for why your CRM needs to handle subsidy workflows natively.

For understanding what to look for in a solar CRM before committing, read the Solar CRM Buyer's Guide, it includes a 25-question evaluation checklist.

How QuickEstimate Fits the Migration Sprint

QuickEstimate is built specifically for the 3-Day Sprint workflow. The import, configuration, and onboarding steps in this guide map exactly to QuickEstimate's interface.

• Lead Capture, CSV import from Google Sheets with automatic field mapping for the 12-column template. IndiaMART and Facebook Lead Ads connect in under 10 minutes for future auto-import.
• Pipeline Management, the 7-stage solar pipeline is pre-configured on signup. Stage SLA alerts are set with default Indian residential benchmarks, override them to your market in Settings.
• Proposal Generator, configured with your branding and PM Surya Ghar subsidy slabs on Saturday. Live for reps to use from Monday morning. See our [solar proposal best practices guide](/blog/solar-proposal-best-practices) for what to include in each proposal.
• WhatsApp Follow-up, integrated from day one. Reps send proposals and follow-up messages from inside the app, logging every interaction automatically. No double entry.

Start the migration at quickestimate.co, the free plan gives you up to 10 proposals per month while you test the workflow before committing to the Pro plan.

What to Do This Week

1. 1

   This Friday: run your data through the 5-pass cleaning process

   Export your master sheet, create the 12-column CSV template, and run all five cleaning passes. Budget two hours. This is the most important part of the entire sprint, a clean import makes everything else straightforward.

2. 2

   Saturday: import, configure, and send yourself a test proposal

   Create your QuickEstimate account, import the clean CSV, configure the proposal generator with your branding and subsidy slabs, and send one test proposal to your own WhatsApp. By Saturday evening, the system should be fully ready for your team.

3. 3

   Sunday: 60-minute team session, then close the old sheet

   Run the structured onboarding session covering the three core tasks. Have every rep practice live. Then archive the Google Sheet and confirm with the team: Monday morning, the CRM is the only tool. No exceptions for the first two weeks.

Frequently Asked Questions

How long does it take to migrate from Excel to a solar CRM?

With the 3-Day Excel Migration Sprint framework, most Indian EPCs complete the migration in one weekend: Friday evening for data export and cleaning (2 hours), Saturday for import and configuration (3 hours), and Sunday for team onboarding (1 hour). The critical path is data cleaning on Friday, EPCs who skip this step typically spend an additional 2–3 weeks cleaning data after the migration and seeing lower rep adoption in the interim.

What data should I migrate to my solar CRM?

Migrate only active, open leads, not closed or dead ones. The 12 canonical fields are: Lead Name, Phone, Email, Source, Stage, System Size (kW), Property Type, Address, PM Surya Ghar Eligible, Owner, Last Contact Date, Notes. Closed Lost leads should be archived separately for a future reactivation campaign, not imported as active leads.

What if my team resists the new CRM?

The most effective response is to show each rep their own leads on the CRM screen during the Sunday session, not a generic demo. When reps see their actual pipeline, not dummy data, resistance drops significantly. Also, keep the first-week training to exactly three tasks: add a lead, advance a stage, and send a proposal. Feature overload is the second most common cause of CRM abandonment after dirty data.

Can I import IndiaMART leads into QuickEstimate?

Yes. QuickEstimate supports CSV import for IndiaMART exports, and can be connected for future auto-import. During the sprint, import IndiaMART leads as part of your Friday data consolidation using the same 12-column CSV template. Going forward, configure the IndiaMART integration to auto-populate new leads directly into the pipeline.

What happens to leads added during the migration weekend?

Have your team log new leads in the new CRM from Saturday onwards (after the import is complete). Any lead added on Friday goes into the master CSV before the import. There is a 24-hour window on Friday where new leads should be added directly to the master CSV you are building, brief your team on this before you start.

How is a solar CRM different from a general CRM for this migration?

A solar-specific CRM like QuickEstimate has PM Surya Ghar subsidy fields, DISCOM region configuration, system size and kW fields, and proposal generation built into the lead card. A general CRM (Zoho, HubSpot) requires custom field setup for all of these, adding 4–8 hours to the migration and creating fields that your team will not understand or use correctly. For Indian solar EPCs, a solar-specific CRM is significantly faster to configure and adopt.

Do I need to stop selling during the migration weekend?

No. The migration is designed to happen over the weekend specifically to minimise disruption. Keep selling normally on Friday. The only restriction is logging new Friday leads into the master CSV (not the old sheet) before Saturday's import. From Saturday onwards, all new leads go directly into the CRM.