From Excel to SAP Sales Cloud V2: A Migration Guide for SMEs

Every sales team has the spreadsheet. It starts as a simple list: company, contact, deal size, status. Then it grows. Formulas break, versions multiply, and someone emails “Pipeline_v3_FINAL_updated.xlsx” while nobody knows which file is current.

Most SMEs start there, and it works for a while. The breaking point usually comes at around 10 to 15 active deals, three or more salespeople, or the first time the board asks for a forecast it can rely on. From then on the spreadsheet costs more time than it saves.

SAP Sales Cloud V2 can replace that spreadsheet in weeks, not in an 18-month enterprise programme. This guide describes the five steps we follow, what each one takes, and where SME teams usually get stuck.

TL;DR: An SME team with 10 or more active deals can move from Excel to SAP Sales Cloud V2 in 4 to 8 weeks. Clean the spreadsheet first (1 to 2 weeks), configure V2 to your real sales process (1 to 2 weeks), import accounts, contacts and opportunities with the Data Workbench (3 to 5 days), train the team on its own data (2 to 3 days) and switch over on a fixed date. Keep the scope to the core pipeline; add features once the team uses the system every day.

Why do spreadsheets break for sales teams?

Spreadsheets are error-prone by nature. A systematic review of 35 years of research found errors in around 94% of the business spreadsheets that were examined, from broken formulas to typing mistakes (Poon et al., Frontiers of Computer Science, 2024). For a sales pipeline, the practical problems look like this:

No single source of truth. Several copies, several versions, conflicting numbers. “Which pipeline figure went to the board?” becomes a standing Monday question.

No current picture. The pipeline shows whatever someone last typed in. That might be yesterday or three weeks ago, and management decides on it without knowing which.

No collaboration. Two reps cannot work in the same file without conflicts. The context of a deal sits in email threads, not with the deal.

No mobile access. A field rep cannot update a deal from a phone between two meetings. It gets done “later”, which often means never.

No reliable forecast. Excel calculates what you type in. It does not learn from your win history, so the forecast rests on gut feeling.

No process. Nothing stops a rep from skipping stages, leaving fields empty or marking a deal as 90% likely with no evidence behind it.

What does Sales Cloud V2 give you instead?

Nucleus Research puts the average return on CRM at $3.10 per dollar spent, with productivity gains making up 51% of that return (Nucleus Research, 2024). For a team coming from spreadsheets, the gain starts with basic structure:

One pipeline, always current. Every deal lives in one system, every update is visible immediately, and management sees the same data as the sales team. No exports, no consolidation.

Mobile from day one. V2 runs in the browser and in the SAP Sales Cloud mobile app. Reps update deals between meetings, and selected data can be downloaded for offline use.

Forecasting and deal scoring. Pipeline management and the forecast tracker compare submitted forecasts with targets and the pipeline. Opportunity scoring estimates win probability from past deals; SAP’s readiness report shows whether your history is sufficient, and for small data sets SAP offers a pre-trained model (SAP Sales Cloud V2 solution guide).

A defined sales process. You define stages, mandatory fields and approvals, and V2 enforces them. Playbooks suggest the next activities per phase.

Collaboration on the deal. Notes, tasks, emails and calls sit on the opportunity. When a colleague takes over a deal, the history comes with it.

Ready for integration. V2 connects to SAP S/4HANA, Microsoft 365, email and telephony. The CRM does not stay an island.

If the difference between an account and a contact is not yet clear in your team, settle it before the import. Our explainer on accounts versus contacts covers it in five minutes.

How does the migration work?

We keep the process deliberately simple. Complexity is the enemy of adoption.

Step 1: Clean your data (1 to 2 weeks)

Before anything moves, clean the spreadsheet. It is the most important step and the most underestimated one.

• Remove dead deals. If nothing has happened in six months, it is not a deal.
• Standardise company names. “Müller AG”, “Mueller AG” and “Muller” should be one account.
• Fill in the gaps: contact person, email, phone, deal value, expected close date.
• Define your stages. Most SMEs need four to six: Prospecting, Qualification, Proposal, Negotiation, Won, Lost.

Dirty data in a CRM is worse than dirty data in Excel, because now everyone sees it. Our article on CRM data quality lists the rules that keep it clean after go-live.

Step 2: Configure Sales Cloud V2 (1 to 2 weeks)

We set up V2 to match how your team sells:

• Account and contact structure
• Opportunity stages and sales cycle
• Mandatory fields per stage
• Basic dashboards: pipeline by stage, by rep, by expected close date
• User roles and permissions

For an SME this is configuration, not development. The standard features cover what a sales team of 5 to 30 people needs to start. Custom requirements come later, once the team works in the system.

Step 3: Import your data (3 to 5 days)

V2’s Data Workbench imports CSV or Excel files for accounts, contacts and opportunities. We map your Excel columns to V2 fields, run a test import, check the result and then run the final import.

Typical sticking points:

• Duplicates. V2’s duplicate check flags likely duplicates with a confidence score, but it works best when the spreadsheet is already clean.
• Date formats. Swiss dates (DD.MM.YYYY) must match the format the import expects.
• Currency. A pipeline in several currencies needs a clear currency column.

Step 4: Train your team (2 to 3 days)

Short, focused sessions: creating and updating opportunities, using the mobile app, running pipeline reports, and the daily routine (what to do first thing in the morning).

Training works best in small groups of three to five people, with their own data. Abstract demos do not stick. Salesforce’s research found that reps spend only 30% of their time selling (Salesforce, 2024), so the CRM has to take admin work away, not add to it.

Step 5: Go live and support (1 week of active support)

On a fixed Monday, everyone switches. The spreadsheet is archived, not deleted, so it stays available for reference. We support the team on site or remotely during the first week to handle questions and edge cases.

This is roughly how it went at Nussbaum Matzingen: customer data, leads and opportunities spread across Excel files, Outlook folders and SAP ECC, consolidated from three data sources into one SAP Sales Cloud V2 platform, with full pipeline transparency for management, in five months.

What should you expect for timeline and cost?

Timeline: 4 to 8 weeks from kickoff to go-live for the core pipeline. Smaller teams (5 to 10 reps) tend towards four weeks; larger teams (15 to 30 reps) or messy data need six to eight. Integrations with ERP or telephony add time; our implementation guide shows how the phases fit together.

Licences: SAP Sales Cloud V2 is licensed per user. For SMEs, the monthly cost per user is in the range of other professional CRM systems. Our pricing guide explains the licence model, or contact us for current figures for your configuration.

Implementation: a focused SME project costs a fraction of an enterprise rollout because the scope stays tight: standard features, clean data, practical training. Our CRM in 10 Days programme is the fastest version of this for teams that want to start with the core.

Running costs: V2 is a cloud service. SAP runs the infrastructure, updates and security patches. What remains is the licence fee and some admin time.

What are the common concerns?

“Our team won’t use it.” They won’t if the CRM makes their job harder. That is why we start with the mobile app, a short list of mandatory fields and the team’s own data, and why a named CRM owner in the sales team matters more than any feature.

“We’ll lose flexibility.” Excel lets you do anything, which is exactly the problem. V2 gives you structure where you need it (pipeline, stages, mandatory data) and flexibility where it helps (extension fields, notes, attachments).

“It’s too expensive for our size.” Count the hours your team spends consolidating spreadsheets, searching emails for deal context and building reports by hand. For most SMEs with 10 or more active deals, that time is the business case.

“What if it doesn’t work?” Start small with the core pipeline and add features as you grow. V2 scales from a handful of users to several hundred on the same platform.

“We’re not an SAP company.” You don’t need to be. V2 works as a standalone cloud CRM. If you run SAP ERP, the integration is a clear advantage; without it, V2 works just as well.

How do you know it’s time to move?

If three or more of these sound familiar, it is time:

• Your pipeline report takes more than 10 minutes to produce
• You have had conflicting numbers from two spreadsheet versions
• A deal was lost because nobody followed up
• You cannot answer “what is our forecast for next quarter?” with confidence
• Your reps avoid updating the spreadsheet

Moving from Excel to a CRM is one of the most effective steps an SME sales team can take. The tools have never been better, the implementation is faster than most teams expect, and the difference shows from the first week.

---

Ready to replace the spreadsheet? We will show you what V2 looks like with your data and your process. Get in touch.

Frequently asked questions

How long does the move from Excel to SAP Sales Cloud V2 take?

For most SMEs, 4 to 8 weeks from kickoff to go-live. Data clean-up takes 1 to 2 weeks, configuration 1 to 2 weeks, the import 3 to 5 days and training 2 to 3 days. The biggest variable is the state of the spreadsheet: teams with consistent data move faster. We keep timelines short by sticking to V2’s standard features.

Do we need an IT person to run SAP Sales Cloud V2?

No. SAP operates the cloud service, including infrastructure, updates, security patches and backups. Day-to-day administration (adding users, adjusting fields, building reports) needs no developer. Most of our SME customers name one CRM owner in the sales team who handles it alongside their normal role.

Can we keep using Excel alongside Sales Cloud V2?

You can, but we advise against it. Two parallel pipelines drift apart within days. We archive the spreadsheet on go-live day for reference, and all active pipeline work moves to V2. A clean break leads to faster adoption and better data.

What data can we import from our spreadsheets?

Accounts (companies), contacts (people) and opportunities (deals) are the standard starting point. Notes, activities and custom fields can follow. V2’s Data Workbench imports CSV or Excel files. What matters is clean, structured data: one row per record, consistent formats, no merged cells. We handle the column mapping during the import.

How does SAP Sales Cloud V2 pricing compare to other CRM systems?

SAP Sales Cloud V2 is licensed per user and month. For SMEs, it is in the same range as Salesforce Sales Cloud or Microsoft Dynamics 365 Sales. The total depends on the number of users and add-ons. SME implementations cost considerably less than enterprise projects because we use standard configuration rather than custom development.

We already use SAP Cloud for Customer (V1). Does this guide apply?

Only partly. Moving from V1 to V2 uses SAP’s own Data Transfer Tool rather than a spreadsheet import. Our step-by-step guide to the Data Transfer Tool covers that path.