Skip to CRM content
121 CRM

Switching · From spreadsheets

Move from rows and versions to owned customer work.

A spreadsheet can be a sensible starting point. The pressure appears when several people need current context, permissions, reminders, conversation history and a reliable next action.

Subscribe to 121 CRMSeller, billing and cancellationPlan the full switch

Customer Thread

From worksheet columns to a working record

Illustrative example

  1. Inspect

    Files, sheets and owners

  2. Clean

    Duplicates and stale rows

  3. Map

    Fields and stages

  4. Resolve

    Ambiguity decided by people

    Human decision

  5. Reconcile

    Sample and totals checked

Illustrative mapping. No spreadsheet import is assumed to be lossless or included.

Spreadsheet mapping

Turn ambiguous columns into defined records and decisions.

The example keeps the source-to-destination mapping, sample status and open human decisions together.

121 CRM · Migration mapping
Source fieldCRM fieldStatus
Company nameOrganisationMapped
Primary emailContact emailSampled
Free-text notesHistory notesReview
Legacy stageOpportunity stageDecision
12 mapped4 sampled3 decisions open
Illustrative exampleSample records and field names are fictional. A real migration needs source-specific reconciliation.

What the destination needs

Move the relationships, not just the rows.

A useful migration preserves the meaning of contacts, active work, ownership and next actions. It also records what cannot move cleanly and who decides the treatment.

Capability 01

Import and export

Moves supported records through structured files, with mapping and validation needed before relying on the result.

How it works
Stores or organises supported business data under configured fields, permissions and record rules.
Why use it
Supports controlled migration and operational extracts when the data is prepared and reconciled.
Plan for
The platform does not make imported, duplicated or incomplete data accurate without review. Bulk migration requires mapping and reconciliation; do not treat a completed import as proof of accuracy or reversibility.
Your team owns
A data owner must define the record model and resolve quality, ownership and access exceptions.
Capability 02

Custom fields

Adds structured fields to supported record types so a business can capture information it actually needs.

How it works
Stores or organises supported business data under configured fields, permissions and record rules.
Why use it
Replaces important notes and spreadsheet columns with searchable, reusable data.
Plan for
The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns
A data owner must define the record model and resolve quality, ownership and access exceptions.
Capability 03

Duplicate management

Uses account rules and review steps to reduce or resolve repeated contact records.

How it works
Stores or organises supported business data under configured fields, permissions and record rules.
Why use it
Keeps teams from following up with the same person through conflicting records.
Plan for
The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns
A data owner must define the record model and resolve quality, ownership and access exceptions.
Capability 04

Tags

Applies controlled labels that can support filtering, workflow entry and operational categorisation.

How it works
Stores or organises supported business data under configured fields, permissions and record rules.
Why use it
Provides a simple way to group records when a full custom field is unnecessary.
Plan for
The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns
A data owner must define the record model and resolve quality, ownership and access exceptions.
Capability 05

Smart lists

Builds reusable contact views from saved filters and relevant record conditions.

How it works
Stores or organises supported business data under configured fields, permissions and record rules.
Why use it
Lets teams focus on a working group without maintaining separate copies of the same contacts.
Plan for
The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns
A data owner must define the record model and resolve quality, ownership and access exceptions.

When a sheet strains

The problem is shared work, not the spreadsheet itself.

Duplicates, version conflict and missing follow-up are common warning signs. The practical test is whether the team can reliably answer who owns what next.

Several versions

People cannot confidently identify the current row, latest note or authoritative copy.

Follow-up outside the sheet

Messages, calls and tasks live elsewhere, leaving status and ownership dependent on memory.

Access is too broad

A file-level permission cannot express which people should view or change particular customer information.

Prepare the workbook

Clean and explain the data before mapping it.

Importing every column can preserve ambiguity rather than solve it.

Choose the source

Identify the authoritative workbook, sheets, owners, last-update conventions and frozen copy.

Profile the rows

Find duplicates, blank identifiers, merged cells, inconsistent formats, formulas and hidden or obsolete fields.

Human decision

Decide what not to move

Exclude stale, unnecessary, unlawfully held or unexplained data instead of importing it by default.

The destination record

Move towards owned work, not simply a different table.

A useful CRM record connects identity, activity, opportunity and next action after the import is reconciled.

121 CRM · Contact workspace
AK

Alex King

Northstar Joinery

alex@example.test

Preferred: email

Contact confirmed

Activity thread

Newest first

Today · 10:05

Suitability reviewed by Amina

Today · 09:18

Record assigned to Amina

Today · 09:13

Acknowledgement recorded

Today · 09:12

Website enquiry captured

Human decision

Confirm fit and priority

Review the request before changing the opportunity stage.

Next action

Discovery call

Thursday · 11:30

Illustrative exampleThe workspace demonstrates information hierarchy rather than a fixed field set.

Map and prove

Turn columns into defined fields, relationships and actions.

A controlled sample shows whether the proposed structure supports the real work.

Field map

Document source column, destination field, format, transformation, default and exception owner.

Relationships and stages

Decide how organisations, contacts, opportunities, owners and next actions are constructed from rows.

Reconcile and cut over

Compare sample counts and values, test representative journeys, then agree the final export and fallback.

Questions about this page

Useful answers, without the sales fog.

1. Can we import a CSV into 121 CRM?

CSV-based migration may be possible, but the destination objects, mappings, duplicate rules, unsupported content and reconciliation process must be tested first.

2. Should we move every spreadsheet column?

No. Move fields with a clear purpose, definition and owner. Historical, sensitive, calculated or unexplained columns need separate decisions.

3. Will the original spreadsheet be deleted?

No deletion is implied. Archive, access, retention and disposal of source files remain customer decisions that should be documented in the cutover plan.

Read all CRM questions

Continue the journey

Migration checklistCustomer managementSales pipelines

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRMSeller, billing and cancellationCompare pricing

121 CRM

Your customers. Your conversations. Your business. Organised around clear ownership and human decisions.