To qualify an installed base for cloud, you need to score every on-premise SAP Business One customer on two things: live trigger events, which include ageing hardware, end-of-support deadlines, security scares, growth, renewals, and ease of move. Then start with two or three customers who score high on both.
Your best cloud pipeline isn't new logos. It's the customers already running SAP Business One on-premise with you - businesses that already trust your team, already pay you for support, and are already sitting on the exact infrastructure risks that cloud removes. The question isn't whether that pipeline exists. It's the order you work it in.
This post is Step 2 of our Sales Playbook for SAP Business One partners, in full detail: the triggers to look for, a scoring model simple enough to run in a spreadsheet this week, and what to do with the customers who aren't ready yet.
Why not just announce cloud to the whole base?
A blanket announcement treats every customer as equally ready, but they won't all be ready. If you send the same 'we now offer cloud' email to a hundred customers and you'll get a handful of polite replies, a few awkward questions your team hasn't rehearsed yet, and silence from everyone else. Worse, if your first migration turns out to be your most complicated customer, you've made your hardest project your only reference story.
Sequencing does the opposite. Your first two or three moves should be chosen to succeed: warm relationships, live triggers, straightforward systems. Those wins give you tested answers to the seven objections you'll hear everywhere, a migration story told in your own customers' words, and a sales team that has seen the process work. Each conversation after that gets easier and faster.
What are the trigger events that make a customer ready now?
A trigger is anything that forces your customers to make an infrastructure decision anyway. You're not creating urgency - you're arriving when it already exists. Here are the five that matter most:
1. Hardware approaching end-of-life. A server bought four or more years ago has a refresh quote coming, and that quote is the single best opening for the cloud conversation: the money is being spent either way, so the question becomes 'spend it standing still, or make this the last refresh you ever fund?' If you don't know the purchase dates across your base, that's the first data-gathering job.
2. Windows Server or SQL Server end of support. End-of-support deadlines are calendar-driven, non-negotiable, and increasingly flagged by auditors and insurers. A customer facing a forced OS or database upgrade on-premise is already committed to a project. Moving to cloud, with SQL to HANA conversion bundled in on the C4P platform, turns that forced spend into a modernisation.
3. A security or continuity scare. A ransomware near-miss, a failed backup restore, a flood, a long outage — or, increasingly, a cyber-insurance renewal asking pointed questions about MFA, patching, and tested recovery. Fear fades fast; be the partner who turns the scare into a plan within the fortnight, not the one who mentions it at the next annual review.
4. Growth and change. New sites, hybrid working pressure, an acquisition, a spike in headcount, or an SAP Business One upgrade already on the table. Change projects open budgets and appetite; the move to cloud rides along instead of competing for attention.
5. Contract and relationship moments. Support renewals, annual account reviews, licence true-ups. These are the moments you're already in the room with permission to ask the strategic question: "what's the plan for the server?"
How do you score the base? A simple two-axis model
You don't need a scoring platform - a spreadsheet with two scores per customer will do.
Axis 1 - Trigger score (how ready are they?). One point per live trigger above, with hardware age and end-of-support deadlines weighted double because they're date-driven rather than mood-driven. Score 0–7.
Axis 2 - Ease score (how smooth will the move be?). Score 0–5, one point each for: a current or near-current SAP Business One version; light-to-moderate customisation and add-ons; a warm, responsive relationship with a decision-maker you know; decent site connectivity (or a willingness to add failover); and a user count that fits your standard offer.
Plot the two scores and your base falls into four groups:
Move first (high trigger, high ease): your first two or three conversations. Book them this month.
Nurture (high trigger, low ease): the need is real but the move needs planning - heavier customisation, an older version, a complex integration landscape. Start the technical groundwork now; these are often your most valuable customers, and on the platform side they frequently belong on C4P Advanced, where single-tenant infrastructure and customer-controlled upgrade timing absorb the complexity.
Schedule (low trigger, high ease): nothing forcing the decision yet, but hardware ages on a calendar. Diarise the conversation for 12–18 months before their likely refresh, and keep the cloud line in every renewal in the meantime.
Park (low trigger, low ease): revisit at the annual review. Don't spend your launch energy here.
One deliberate note on that first group: resist the temptation to lead with your biggest customer, even if they qualify. Lead with the smoothest customer. The biggest deal is worth more with three reference stories behind it than as your live experiment.
What does the first conversation actually sound like?
Not a pitch - a question inside a conversation you were having anyway. At the account review or renewal: "While we're looking ahead - the server's coming up on five years old. What's the current thinking on it?" Then listen. The triggers will surface on their own: the IT contact who's stretched, the insurance form nobody enjoyed filling in, the new starter who needs remote access.
From there, the playbook takes over: the commercial conversation with the owner, the reassurance conversation with IT, a per-user quote produced in minutes rather than days, a trial system to make it real, and the Migration Factory plan to de-risk the close. Because most first movers fit the standard profile, C4P Standard multi-tenant is usually the right home - fast to deploy, everything bundled, and live in hours rather than weeks, which means your first reference story arrives quickly too.
What about the customers who say "not yet"?
"Not yet" is a scheduling answer, not a rejection - treat it as data for the spreadsheet. Record the reason (mid-hardware-cycle, budget year, a bigger project in flight), set the follow-up date it implies, and keep two quiet habits running:
The cloud line stays in every proposal and renewal by default. It costs you nothing to include and keeps the option visible without pressure.
The refresh calendar gets maintained. Hardware purchase dates, OS and SQL versions, insurance renewal months. When the trigger fires, you're the first call because you predicted it.
Across an installed base, this is what 'land, expand, grow' looks like in practice: a handful of chosen first moves, a scored and scheduled pipeline behind them, and recurring revenue that compounds as each trigger comes due, on customer relationships that remain entirely yours.
Run the exercise this week
Pull the list: every on-premise SAP Business One customer, with hardware age, SAP version, SQL/OS version, user count, and renewal date. Gaps in the data are themselves a to-do list.
Score trigger and ease for each, and sort into the four groups.
Book the first three conversations from the 'move first' group - inside meetings you already have where possible.
If you'd like a second pair of eyes on the sequencing, talk to the team - we've helped partners of every size plan their first moves, and we've run this exact exercise on our own base as an SAP Business One partner ourselves. Or see the platform end-to-end first at a free partner webinar: C4P Standard, C4P Advanced, and the Migration Factory, demonstrated live. No obligation, no sales pitch.
FAQs
Which SAP Business One customers should a partner move to the cloud first? Customers who score high on both readiness and ease: a live trigger event (ageing hardware, end-of-support deadlines, a security scare, growth, or an upcoming renewal) combined with a current SAP Business One version, manageable customisation, and a warm relationship. Start with two or three such customers and use those wins as references for the rest of the base.
What trigger events indicate a customer is ready for cloud? The five most reliable are: server hardware approaching end-of-life, Windows Server or SQL Server versions nearing end of support, a recent security or continuity scare (including tough cyber-insurance questions), business growth or change such as hybrid working or acquisitions, and contract moments like support renewals and annual reviews.
Should a partner migrate its biggest customer first? Usually not. The smoothest customer makes the best first move, because early migrations become the reference stories that de-risk every later conversation. Larger or more complex customers, who often suit single-tenant hosting like C4P Advanced, close more easily once two or three successful moves are behind you.
What should partners do with customers who aren't ready to move yet? Treat "not yet" as scheduling data: record the reason, diarise the conversation for 12–18 months before their likely hardware refresh, keep a cloud option in every proposal and renewal by default, and maintain a refresh calendar of hardware ages, OS and SQL versions, and insurance renewal dates so the partner is first in when the trigger fires.
