RReshape.
← All articles

Spreadsheet to CRM Migration for Landscaping Companies: Staging Every Sold Job

By Alex Regueiro · October 25, 2026 · 6 min read

A landscaping company can move to a new CRM and still lose track of the jobs it had already sold. Jobs that exist only as rows in a spreadsheet, or as names on an office whiteboard, do not make the trip unless someone carries them over by hand.

This story is about the owner of a landscaping company and an office manager who were moving to a GoHighLevel pipeline alongside new field-service software. We walked the spreadsheet job by job, then set a documentation habit so the same blind spots would not return. If you run a trade or outdoor business, our page for home service businesses shows the wider system.

The situation

Every existing project lived in a spreadsheet job tracker. The company was in the middle of moving to a GoHighLevel pipeline plus field-service software, which meant two new systems and one old spreadsheet. For some jobs, the spreadsheet was the only place they were recorded.

Day-to-day scheduling ran off a whiteboard in the office. That works while everyone is in the building. It stops working when people are off-site and need to know what is booked.

What was broken

A pipeline only helps with the jobs that are inside it. Four problems showed up together.

  • Jobs that were sold but existed only in the spreadsheet could be missing from both new systems.
  • The whiteboard schedule could not be seen from a job site.
  • Finished work was not documented the same way twice, so it was hard to turn into content.
  • Asking customers for reviews was ad hoc, done when someone happened to remember.

What we built

We worked in two passes, one on the data and one on habits.

  • We walked the full spreadsheet job tracker with the owner and the office manager, so every existing project is staged accurately in GoHighLevel and in the field-service software.
  • We set up free scheduling accounts for call routing and walkthrough scheduling.
  • We locked a standard format for documenting every job in three parts: before, during and after.
  • We agreed a review follow-up process, so asking for a review is a step in the job and not a memory test.
  • We locked two video concepts: a recruitment video, scripted with camera angles and a call to action, and a featured-partner video meant to build goodwill ahead of a later partnership conversation.
  • We set the twice-weekly working meetings to be recorded on video calls with an auto-transcription tool, so action items do not fall through.

What changed

No measured result came out of these calls, such as time saved or jobs recovered, and we are not going to supply one. What changed is how the work is organized. Before, a sold job could exist as one row in one spreadsheet. Now every existing project has a place in the pipeline and in the field-service software, and each new job has a fixed before, during and after documentation format and a defined review step.

Two follow-ups were set. The first is an audit of this year's job spreadsheet, with a cleaner tracking system proposed afterward. The second is a test of a sales presentation workflow built around AI with the estimator, who already uses AI chat tools to create client-facing design visuals.

Check your own tracker in ten minutes

This section is advice for your own business, not a record of what the client found. Pick five jobs that are sold but not finished. Look each one up in your CRM. Any job you cannot find is a blind spot, and it is better to find it now than when a customer calls about it.

Then ask whoever is on a job site right now how they would learn tomorrow's schedule. If the answer is to call the office, your schedule lives in one building. Finally, look at your last finished job and ask whether anyone could build a before, during and after story from what was saved.

Frequently asked questions

How do you move jobs from a spreadsheet tracker into a CRM pipeline?

Walk the whole tracker with the person who knows the jobs best, one row at a time, and give each job the pipeline stage that matches where it really stands. Do it in every system you use so the CRM and the field-service software agree. Skipping the walk is how sold jobs get lost.

Why document landscaping jobs as before, during and after?

A fixed format means every job leaves behind the same three kinds of material. That gives a content team something consistent to work from instead of whatever photos happened to be taken, and it makes finished work easier to reuse.

Do I need paid scheduling software for walkthrough bookings?

Not to start. Free scheduling accounts were enough for call routing and walkthrough scheduling in this case. Move to something heavier only when the free tier blocks a specific need you can name, and not before.

Why record team meetings with auto-transcription?

Recorded and transcribed meetings give you a written trail of what was decided and who owns each task, so nothing depends on someone's memory. In this case the twice-weekly working meetings were set up that way so action items do not fall through.

If your jobs live in a spreadsheet, a whiteboard and a CRM that do not agree, book a 30-minute AI follow-up and reporting audit. We compare what you have sold with what your systems know and show you where jobs fall through.