Skip to content
Resources / GA Applications

Guide / System choice

Use a spreadsheet while it stays controlled; move when the work needs a shared operating record.

A spreadsheet can remain suitable for a small, well-owned list with simple updates. A CRM becomes more appropriate when several people manage relationships, records need linked histories, ownership and stages matter, permissions differ or automation depends on reliable events. The decision should follow workflow and governance, not fashion.

Questionwhat the reader needs
Evidencedefinitions and boundaries
Next stepa useful action path
Why it matters

Scope

One controlled list and limited relationships.

CHAPTER 01

Know when a sheet is enough.

Simple tools can be the responsible choice.

01.1

Scope

One controlled list and limited relationships.

01.2

Owner

A named person maintains structure and quality.

CHAPTER 02

Notice when the operating model has outgrown it.

Friction appears before a migration project.

02.1

Relationships

People, companies and activities need history.

02.2

Workflow

Stages, ownership and reminders drive work.

CHAPTER 03

Clean and model before migrating.

Do not copy every column blindly.

03.1

Profile

Measure duplicates and missing values.

03.2

Test

Map, migrate and reconcile a trial first.

Continue through the resources system.

Each route answers a different operating question while retaining the same standards for evidence, responsibility and a usable next step.

Questions worth resolving

What to clarify before committing.

Is CRM always better?
No. It adds cost and responsibility and must solve a real operating need.
Can existing sheets be imported?
Yes after profiling, mapping and test reconciliation.

Bring the real problem

Review whether the current spreadsheet has become an operating risk.

Bring a representative file and the workflow around it.