I need to migrate from our old ERP to a new system. How do I hire a good SAP implementation consultant?

Migrating to a new ERP is a massive undertaking, and finding the right SAP implementation consultant can make or break your project timeline, budget, and overall sanity.

Here is a step-by-step roadmap to finding, vetting, and hiring a top-tier SAP professional or partner:

1. Define the Scope and SAP Specialization

Before searching, you need absolute clarity on what you actually need. SAP is a vast ecosystem, and a "generalist" might not have the chops for your specific requirements.

• Identify the Product: Are you implementing SAP S/4HANA (Cloud or On-Premise), SAP Business ByDesign, or legacy ECC?
• Define the Modules: Pinpoint your primary functional needs (e.g., FI/CO for finance, MM/SD for supply chain/sales, EWM for warehouse management, SuccessFactors for HR).
• Determine the Engagement Model: Decide whether you need an individual independent contractor, a boutique consulting firm, or a major system integrator (SI) like Accenture or Deloitte.

2. Establish Essential Qualification Criteria

A good SAP consultant doesn't just know how to configure the software; they understand business process re-engineering . Look for:

• Certified Expertise: Check for active SAP Certifications relevant to your targeted modules and deployment type (especially S/4HANA).
• Industry Experience: Prior experience in your exact vertical (e.g., manufacturing, retail, life sciences) means they already know your industry's compliance standards and best practices.
• Full-Lifecycle Implementations: Ensure they have walked through the entire Activate methodology —from "Discover and Prepare" through "Explore, Realize, Deploy, and Run"—multiple times, not just maintenance or minor support tickets.

3. Sourcing Channels

Where you look depends on the scale of your hire:

• Niche IT Staffing Agencies: Specialized recruiters who focus strictly on SAP ecosystems (e.g., Lawrence Harvey, Mason Frank, or regional equivalents) often have pre-vetted freelance talent ready to deploy.
• Professional Networks: Leverage LinkedIn by searching for verified consultants with specific tags like "SAP S/4HANA Program Manager" or functional module codes.
• SAP Partner Finder: If looking for a consulting firm or implementation partner, use the official SAP Partner Finder to locate certified partners with verified customer success stories.
• Peer Referrals: Ask industry peers who recently underwent an SAP migration which independent advisors or consulting arms they trusted.

4. Rigorous Vetting and Interviewing

When you get candidates in front of you, skip generic interview questions and test for real-world scars:

• The "Failed Project" Question: Ask them to describe an implementation that went off the rails and specifically how they course-corrected it.
• Data Migration Strategy: Ask how they handle legacy data cleansing and master data governance—this is where 80% of implementations stall.
• Change Management: A great technical consultant who alienates your end-users will lead to low adoption rates. Gauge their communication and training skills.
• Check References: Call past project sponsors and ask about their punctuality, budget discipline, and problem-solving under pressure.

If you want, I can:

• Provide a list of key interview questions specifically for SAP project managers
• Break down the pros and cons of independent contractors vs. large consulting firms
• Help outline your project scope and module requirements

The biggest mistake is hiring someone because they have “SAP experience.” You want a consultant or implementation partner who has successfully migrated companies similar to yours, on the specific SAP product you’re buying, at roughly your scale and complexity.

SAP itself recommends using its Partner Finder and evaluating partners by competencies, specialization, expertise, proficiency, and maturity.

1. Define the project before you interview consultants

Create a 1–2 page brief covering:

• Current ERP: vendor/version and how heavily customized it is
• Target SAP system: e.g. SAP S/4HANA Cloud Private Edition, SAP Cloud ERP, SAP Business One, etc.
• Company size: employees, revenue, number of entities/plants/warehouses
• Countries and currencies
• Modules: Finance, Procurement, Sales, Manufacturing, Supply Chain, HR, etc.
• Integrations: CRM, payroll, e-commerce, banking, EDI, MES, logistics, tax systems
• Data migration: approximate transaction/master-data volumes and historical data requirements
• Major customizations: especially anything you consider “mission critical”
• Desired go-live date
• Budget range
• Post-go-live support requirements

This prevents consultants from giving you wildly different proposals because they're solving different problems.

2. Decide whether you need an individual consultant or an implementation firm

For a serious ERP migration, I'd generally favor an SAP implementation partner rather than hiring one independent consultant.

A good partner can provide the project manager, functional consultants, technical/integration specialists, data migration team, testing resources and change-management expertise. SAP specifically distinguishes “Consult and Implement” partners as those that design, build and integrate SAP solutions.

An independent consultant can make sense if:

• your implementation is relatively small;
• you already have a strong internal IT/ERP team;
• you need an independent SAP architect to oversee a larger implementation partner; or
• you need specialist expertise for one module.

For a major migration, an independent SAP advisor + implementation partner can actually be an excellent combination: the advisor represents you, while the partner executes the project.

3. Build a shortlist of 4–6 candidates

Start with SAP's official sap.com rather than relying solely on Google or consultant directories. SAP lets you filter for consult-and-implement partners and relevant SAP solutions/competencies.

Then ask each candidate for three references from customers similar to you.

Don't accept:

“We have 500 SAP customers.” Ask:

“Give me three customers that migrated from a comparable legacy ERP to the same SAP product, with similar company size and complexity, and let me speak with them.” That distinction is extremely important.

4. Interview the actual project team—not just the sales team

This is one of the best ways to avoid a bad hire.

During the sales process, insist on meeting:

• proposed project manager;
• SAP solution architect;
• lead Finance/Operations functional consultants;
• data migration lead;
• integration lead;
• testing lead;
• change-management/training lead.

Ask:

“Who exactly will be working on our project, and what percentage of their time will be allocated to us?”

Get those names into the contract if possible.

A common failure mode is having an impressive senior team sell the project and then discovering that most of the implementation is performed by much more junior resources.

5. Ask these interview questions

I'd use questions that force them to demonstrate experience rather than give you sales pitches.

Experience

• “Tell me about the last three ERP migrations you personally led.”
• “Which one was most similar to ours?”
• “What went wrong?”
• “What would you do differently now?”
• “How many SAP implementations have you taken through go-live?”

Migration

• “Walk us through your data-migration methodology.”
• “How will you determine which historical data should actually be migrated?”
• “How many mock migrations do you recommend?”
• “How will we reconcile the old ERP to SAP before go-live?”

Customization

Ask:

“Show me how you decide whether something should be standard SAP, configured, extended, or customized.” This is particularly important because SAP's current methodology emphasizes fit-to-standard and clean-core principles rather than simply recreating the old ERP inside SAP.

A consultant who responds, “We'll customize SAP to match everything you do today,” would concern me.

Testing

Ask:

• “Who writes the test scripts?”
• “Who owns UAT?”
• “How many testing cycles?”
• “How will integrations be tested?”
• “What are your go/no-go criteria?”

Go-live

Ask:

“Give me your detailed cutover plan from the final day of the old ERP through the first week of SAP.” A genuinely experienced implementation team should be able to talk about this in considerable detail.

6. Require a realistic implementation plan

Don't select the consultant with the prettiest PowerPoint.

Have each finalist produce a preliminary plan showing:

SAP Activate itself uses structured phases including Discover, Prepare, Explore and Realize, with subsequent deployment/operations activities.

7. Score them objectively

I'd use a weighted scorecard rather than choosing based on chemistry.

For example:

Don't make price the dominant factor. A consultant who costs 20% more but avoids a six-month delay can be dramatically cheaper overall.

8. Check references aggressively

Don't just ask whether the client was happy.

Ask the reference:

• Did they hit the original go-live date?
• Did they hit the original budget?
• How much did the final cost differ from the proposal?
• How many consultants were actually assigned?
• Was the data migration successful?
• How disruptive was go-live?
• How many critical issues remained afterward?
• What did the consultant do poorly?
• Would you hire them again?
• What do you wish you had known before signing the contract?

That last question is particularly revealing.

9. Be very careful about the contract

Make sure the contract clearly defines:

• scope and deliverables;
• assumptions;
• responsibilities of your team vs. consultant;
• named personnel;
• milestones;
• acceptance criteria;
• change-control process;
• travel/expense rules;
• data-security requirements;
• intellectual property;
• documentation requirements;
• knowledge transfer;
• warranty/defect remediation;
• post-go-live support;
• termination rights.

For a fixed-price project, be especially careful about an overly broad list of “assumptions” that allows the consultant to turn half the project into change orders.

10. My ideal hiring process

I'd run it like this:

Week 1: Define requirements and project brief ↓ Week 2: Identify 6–8 SAP partners ↓ Week 3: Narrow to 3–4 ↓ Week 4: Deep-dive interviews + proposed architecture ↓ Week 5: Customer reference calls ↓ Week 6: Final proposal + contract negotiation ↓ Week 7: Select partner and begin planning

For a major ERP transformation, I'd also seriously consider hiring a small independent SAP program advisor before signing the implementation contract. Their job is to help you evaluate vendors, challenge the proposed architecture and protect your interests throughout implementation.

The three things I'd prioritize

If you remember nothing else, evaluate the candidates on:

1. Have they done this exact kind of SAP migration before?
2. Are the people who sold you the project actually going to deliver it?
3. Do they have a disciplined approach to data, testing, integration, cutover and change management—not just SAP configuration?

SAP also offers packaged partner solutions and qualified partners that combine SAP software with industry/line-of-business expertise, which can be worth investigating if you're a midsize organization.

If you tell me your current ERP, the SAP product you're considering, company size, industry, number of locations/countries, and approximate budget, I can turn this into a specific SAP consultant RFP with evaluation criteria, interview questions, and a scoring spreadsheet structure.

I'd use a weighted scorecard rather than choosing based on chemistry.

For example:

Don't make price the dominant factor. A consultant who costs 20% more but avoids a six-month delay can be dramatically cheaper overall.

8. Check references aggressively

Don't just ask whether the client was happy.

Ask the reference:

• Did they hit the original go-live date?
• Did they hit the original budget?
• How much did the final cost differ from the proposal?
• How many consultants were actually assigned?
• Was the data migration successful?
• How disruptive was go-live?
• How many critical issues remained afterward?
• What did the consultant do poorly?
• Would you hire them again?
• What do you wish you had known before signing the contract?

That last question is particularly revealing.

9. Be very careful about the contract

Make sure the contract clearly defines:

• scope and deliverables;
• assumptions;
• responsibilities of your team vs. consultant;
• named personnel;
• milestones;
• acceptance criteria;
• change-control process;
• travel/expense rules;
• data-security requirements;
• intellectual property;
• documentation requirements;
• knowledge transfer;
• warranty/defect remediation;
• post-go-live support;
• termination rights.

For a fixed-price project, be especially careful about an overly broad list of “assumptions” that allows the consultant to turn half the project into change orders.

10. My ideal hiring process

I'd run it like this:

Week 1: Define requirements and project brief ↓ Week 2: Identify 6–8 SAP partners ↓ Week 3: Narrow to 3–4 ↓ Week 4: Deep-dive interviews + proposed architecture ↓ Week 5: Customer reference calls ↓ Week 6: Final proposal + contract negotiation ↓ Week 7: Select partner and begin planning

For a major ERP transformation, I'd also seriously consider hiring a small independent SAP program advisor before signing the implementation contract. Their job is to help you evaluate vendors, challenge the proposed architecture and protect your interests throughout implementation.

The three things I'd prioritize

If you remember nothing else, evaluate the candidates on:

1. Have they done this exact kind of SAP migration before?
2. Are the people who sold you the project actually going to deliver it?
3. Do they have a disciplined approach to data, testing, integration, cutover and change management—not just SAP configuration?

SAP also offers packaged partner solutions and qualified partners that combine SAP software with industry/line-of-business expertise, which can be worth investigating if you're a midsize organization.

Hiring a top-tier SAP implementation consultant can make or break your migration. You need someone who doesn't just know the software, but understands your business processes inside and out.

Here is a structured, step-by-step roadmap to finding, vetting, and hiring the right consultant for your ERP migration:

1. Define Your Scope and Requirements

• Role definition: Decide whether you need an individual functional/technical expert, a project manager, or an entire implementation partner firm.
• Module expertise: Identify the specific SAP modules required for your migration (e.g., SAP S/4HANA, FI/CO, MM, SD, PP).
• Project scope: Outline whether you need end-to-end implementation, data migration support, customization, or post-go-live hypercare.

1. Source Qualified Candidates and Partners

• Professional networks: Leverage platforms like LinkedIn to search for certified SAP consultants with specific S/4HANA credentials.
• Specialized staffing agencies: Partner with niche IT recruitment firms that specialize strictly in ERP and SAP talent placement.
• SAP Partner Finder: Explore official implementation partners via the SAP Partner Finder if you prefer a firm over an independent contractor.

1. Screen for Essential Qualifications

• Certifications: Verify active official certifications, such as SAP Certified Application Associate or Professional for relevant modules.
• Industry experience: Prioritize consultants who have successfully migrated companies of a similar size and in your exact industry vertical.
• Track record: Ask for proof of full-lifecycle implementations (from blueprinting to go-live and support) rather than just partial module tweaks.

1. Conduct Rigorous Technical and Cultural Interviews

• Scenario-based questioning: Present a past migration bottleneck or data-cleansing nightmare from your business and ask how they would resolve it.
• Change management skills: Ensure they possess soft skills to train your internal team and manage pushback from reluctant department heads.
• Communication style: Verify that they can bridge the gap between deep technical jargon and executive-level summaries.

1. Check References and Validate Past Projects

• Client testimonials: Request contact information for at least two past clients where the consultant managed a comparable migration.
• Scope delivery: Directly ask previous employers if the project stayed on schedule, within budget, and met initial quality expectations.

If you'd like, let me know:

• What SAP version/product you are migrating to
• The current size of your company and industry
• Whether you are looking for an independent contractor or an implementation firm

I can give you tailored interview questions or help refine your job description.

Hiring the right SAP implementation consultant is less about finding someone who “knows SAP” and more about finding someone who has successfully migrated companies like yours onto the specific SAP product you’re buying.

SAP itself recommends using its Partner Finder and evaluating partners on competency, specialization, expertise, and maturity.

1. Define the project before you interview anyone

Write down these basics:

• Current ERP: e.g. Oracle, NetSuite, Microsoft Dynamics, legacy SAP, custom system
• Target SAP product: S/4HANA Cloud, SAP Business One, SAP Business ByDesign, SuccessFactors, etc.
• Company size: employees, revenue, number of legal entities
• Locations/countries: especially important for tax, payroll, and statutory requirements
• Modules: Finance, Procurement, Manufacturing, Sales, Supply Chain, HR, etc.
• Integrations: CRM, e-commerce, banks, payroll, warehouse systems, EDI, reporting/data warehouse
• Data migration: approximate number of customers, vendors, SKUs, transactions and years of history
• Target go-live date
• Budget range
• Whether you want implementation only or ongoing support

This prevents a consultant from selling you a generic SAP implementation.

2. Look for an SAP partner, not just an individual freelancer

Start with partnerfinder.sap.com and filter for the particular SAP product, industry, geography and competencies you need. SAP distinguishes specifically between consult-and-implement partners and other types of partners.

For a substantial ERP migration, I'd normally interview 3–5 firms rather than choosing the first SAP consultant you find.

You don't necessarily need a giant firm. A smaller specialist can be excellent if it has deep experience with your particular SAP product and industry.

3. The most important interview question

Ask:

“Show me three implementations you've completed that are comparable to ours. Who was the client, what was the starting ERP, what SAP product did you implement, how many users/entities did it involve, and what went wrong?” The last part is particularly revealing.

A good consultant should be able to discuss failures, scope changes, data problems, integration problems and user adoption issues without blaming the customer for everything.

Then ask to speak directly with 2–3 former customers.

Don't accept only references selected by the sales team if you can avoid it.

4. Evaluate the actual people—not the firm's logo

This is a common trap.

A large consulting firm may put senior people in the sales presentation and then staff your project with relatively inexperienced consultants.

Put these requirements into the contract:

• Named project manager
• Named solution architect
• Named functional leads
• Required experience/certifications
• Minimum percentage of project time from senior personnel
• Approval required before key personnel are replaced
• Explicit responsibility for data migration
• Explicit responsibility for integrations
• Knowledge-transfer requirements for your internal team

SAP says qualified implementation partners can be evaluated through competency and specialization information, and for some SAP programs qualification includes trained/certified implementation personnel and successful customer-project experience.

5. Test their implementation methodology

Ask them to walk you through the project from day one to go-live.

You want to hear a structured methodology rather than:

“We'll configure the system, migrate your data and train everyone.” For S/4HANA implementations, SAP's SAP Activate methodology provides a structured implementation approach spanning discovery, preparation, exploration, realization, deployment and running the solution.

A good consultant should be able to explain:

Discover → Prepare → Explore/Fit-to-Standard → Build/Realize → Test → Deploy → Stabilize

And they should be very clear about what your employees must do versus what the consultant does.

6. Pay special attention to these five areas

I'd weight your evaluation roughly like this:

I'd actually consider lowering the price weighting if this is a business-critical ERP replacement.

A cheap SAP implementation that takes 18 months longer or requires extensive rework is extremely expensive.

SAP itself has emphasized that implementation quality and expertise shouldn't be judged primarily by implementation price.

7. Make them demonstrate how they'd handle your migration

Give the finalists a realistic mini-case.

For example:

“We currently have 15 years of customer/vendor/product/GL data in our old ERP. We have 250 users, three legal entities and integrations with Salesforce and our warehouse. We need to go live within 12 months.” Then ask each consultant to produce a high-level:

• Project plan
• Team structure
• Data migration strategy
• Integration strategy
• Testing strategy
• Training/change-management approach
• Cutover plan
• Major risks
• Assumptions
• Customer responsibilities
• Estimated cost

You'll learn much more from this exercise than from another two-hour sales presentation.

8. Ask these questions before signing

Some particularly useful ones:

Scope

• What's explicitly included?
• What's excluded?
• How are change requests priced?

Data

• Who cleans the legacy data?
• Who maps legacy fields to SAP?
• How many mock migrations will we perform?
• Who validates migrated data?

Integrations

• Who owns integration architecture?
• Are third-party systems included in the price?
• Who tests end-to-end processes?

Testing

• Who writes the test scripts?
• Who manages UAT?
• What constitutes acceptance?

Go-live

• Who makes the go/no-go recommendation?
• How long is hypercare?
• How many consultants remain after go-live?

Commercials

• Fixed price, time-and-materials, or hybrid?
• What's the payment schedule?
• What happens if the project is delayed?
• What happens if the named consultants leave?

Knowledge transfer

• Will our employees be able to administer and modify the system without you?
• What documentation do we receive?
• Do we get training for our internal IT/business teams?

9. Watch for these red flags 🚩

I'd be cautious if a consultant:

• Promises an unrealistically short implementation
• Gives you a very low fixed price without understanding your requirements
• Can't produce comparable customer references
• Talks mostly about SAP configuration rather than your business processes
• Has no clear data-migration methodology
• Treats integrations as an afterthought
• Wants to heavily customize SAP to reproduce every feature of your old ERP
• Won't commit to the actual people who will deliver the project
• Can't clearly explain what you need to do internally
• Says everything will be “standard” without demonstrating how your business fits the standard processes

The last one is especially important. For modern SAP implementations, you generally want a consultant who can distinguish between legitimate business requirements and unnecessary customization rather than simply rebuilding your old ERP inside SAP.

My recommended hiring process

I'd use this sequence:

1. Define your requirements and project constraints.
2. Find 5–8 potential SAP partners through SAP Partner Finder and industry referrals.
3. Narrow that to 3–5 finalists.
4. Give all finalists the same project brief.
5. Interview the actual delivery team, not just salespeople.
6. Check customer references yourself.
7. Have each finalist present their migration, integration, testing and cutover approach.
8. Score them using a common scorecard.
9. Negotiate a contract with named personnel, milestones, acceptance criteria, deliverables and change-control rules.
10. Keep ownership of the business decisions and data with your company—the consultant should implement the solution, not decide what your business should look like.

If you tell me (1) your current ERP, (2) which SAP product you're moving to, (3) approximate company size/users, (4) industry, and (5) country/countries involved, I can help you build a shortlist criteria and interview scorecard specifically for your migration.

Hiring a great SAP implementation consultant (or an implementation partner firm) is the single most critical inflection point in an ERP migration. Because the SAP ecosystem is massive and highly fragmented, a generic "SAP expert" posting rarely works.

A structured, step-by-step approach ensures you secure the right expertise for your specific migration:

1. Define Your Exact Scope and Modules First
   Don't post a generic job description. Clarify whether you need a functional consultant (who understands business processes like FICO, MM, SD), a technical consultant (ABAP, integration, data migration), or a solution architect . Pinpoint the target SAP version (e.g., SAP S/4HANA) and industry-specific requirements before writing the requisition.
2. Target Proven End-to-End Implementation Experience
   An operational support consultant who only fixes day-to-day tickets is very different from an implementation consultant who has taken a company live from a legacy system. Insist on candidates (or partner teams) who have completed at least 2 full lifecycle implementations in your specific industry.
3. Verify Certifications and Credentials
   Don't just take a resume at face value. Use the official SAP Certification Verification Service to validate that their claimed credentials are active and up to date.
4. Conduct Scenario-Based Technical Screenings
   Because you might lack deep internal SAP expertise, consider bringing in an independent third-party advisor or niche digital transformation recruiter to help screen. Ask candidates how they handled specific migration roadblocks: data cleansing failures, scope creep, user resistance, or integration snags with non-SAP legacy software.
5. Test for Crucial Soft Skills and Change Management
   A brilliant configurator who cannot communicate complex processes to floor-level stakeholders will sink adoption. Look for strong translators who excel at change management, user training, and cross-functional collaboration.
6. Check Detailed References
   Always speak directly with past project managers or sponsors from previous implementations. Ask specifically about their adherence to timelines, budget control, and composure under high-pressure go-live scenarios.

To help narrow this down, could you tell me:

• What legacy ERP are you migrating from, and what SAP product/version are you moving to?
• Are you looking for an independent contractor/individual consultant or a full-service implementation partner/consulting firm?

Hiring the right SAP implementation consultant (or implementation partner) is one of the most important decisions in an ERP migration. A strong consultant does more than configure SAP—they help redesign processes, migrate data, manage change, and get users adopted. SAP itself recommends evaluating partners based on fit, expertise, and demonstrated capability rather than simply choosing a large brand name.

Here is a practical hiring approach:

1. Define your migration before interviewing consultants

Prepare a short project brief:

• Current ERP system (e.g., Oracle, Dynamics, Infor, custom ERP)
• Target SAP product (e.g., SAP S/4HANA Cloud, SAP S/4HANA Private Cloud, SAP Business One)
• Implementation type:
  • Greenfield — redesign processes and start fresh
  • Brownfield — convert/migrate existing SAP
  • Selective data transition — keep some history/processes while redesigning others
• Countries, business units, and legal entities involved
• Modules needed:
  • Finance (FI/CO)
  • Procurement (MM)
  • Sales (SD)
  • Manufacturing (PP)
  • Supply chain (EWM, TM)
  • HR, analytics, integrations, etc.
• Timeline and budget range

A consultant who cannot quickly understand your scope is unlikely to manage the complexity later.

2. Decide whether you need a firm or an independent consultant

Large SAP implementation partner

Good for:

• Multi-country rollouts
• Complex integrations
• Regulatory requirements
• Large user populations

Tradeoffs:

• Higher cost
• Possible staff turnover after the contract is signed

Boutique SAP consultancy

Good for:

• Mid-size companies
• Specialized modules
• More senior hands-on consultants

Tradeoffs:

• May need additional vendors for large integrations or support

Independent SAP consultant

Good for:

• Architecture reviews
• Project recovery
• Specialized expertise
• Acting as your advisor while you manage vendors

Tradeoffs:

• Usually not enough capacity for a full ERP migration alone

3. Look for these qualifications

Proven migration experience

Ask:

“Show me three ERP migrations similar to ours. What went wrong, and how did you fix it?”

Look for:

• Same industry
• Similar company size
• Similar ERP being replaced
• Similar SAP version
• Similar data complexity

Do not accept generic references like “we have 500 SAP projects.”

4. Verify the actual team, not just the company

A common mistake is buying a famous consulting brand and receiving a junior delivery team.

Ask:

• Who will be our project manager?
• Who is the lead SAP architect?
• Who owns data migration?
• Which consultants worked on the reference projects?
• Are they employees or subcontractors?
• How much of their time is guaranteed to our project?

5. Evaluate their methodology

A good SAP consultant should have a structured approach covering:

1. Discovery and process assessment
2. Solution design
3. Configuration/build
4. Data migration
5. Testing
6. Training/change management
7. Cutover
8. Hypercare/support

For S/4HANA projects, ask how they use SAP Activate methodology and what deliverables they produce at each stage.

6. Make data migration a separate evaluation area

Legacy ERP migrations often fail because of data, not configuration.

Ask:

• How will you profile our legacy data?
• Who owns data cleansing?
• How many migration cycles are planned?
• How will you validate balances and master data?
• What tools do you use?
• Who signs off that migrated data is correct?

7. Ask these interview questions

Delivery experience

• “Tell us about your last SAP migration that went badly. What did you learn?”
• “What risks do you see in our project?”
• “What would you do differently if you started this project?”

Technical

• “What integrations do you expect?”
• “How will you handle customizations?”
• “What is your approach to keeping SAP clean-core?”

Commercial

• “What assumptions are built into your estimate?”
• “What typically causes change orders?”
• “What percentage of projects exceed their original budget?”

Support

• “Who supports us after go-live?”
• “What does your 90-day hypercare plan look like?”

8. Request references and call them

Do not just read case studies. Speak with former customers.

Ask:

• Did they finish on time?
• Did the budget increase?
• Were the promised consultants actually assigned?
• How did they handle problems?
• Would you hire them again?

9. Use a scoring model

Example:

Avoid choosing solely on lowest price.

10. Build a shortlist through SAP’s partner ecosystem

SAP maintains a partner directory where customers can find implementation partners and filter by capabilities.

A good shortlist often includes:

• 2–3 large system integrators
• 2–3 specialized SAP boutiques
• 1 independent SAP advisor (to help you evaluate vendors)

Red flags to avoid

🚩 “We can implement SAP in a few months” without understanding your processes
🚩 Heavy reliance on offshore junior resources with no clear leadership
🚩 No named data migration lead
🚩 No customer references with similar complexity
🚩 A proposal focused on software configuration but ignoring change management
🚩 A sales team that cannot introduce the actual delivery team

If you share your current ERP, industry, company size, countries involved, and which SAP product you are considering, I can suggest what type of SAP consultant/partner profile would fit best and what a reasonable selection process should look like.

Migrating to a new ERP is a massive undertaking, and finding the right SAP implementation consultant can make or break the project. Here is a clear, actionable guide to hiring a top-tier professional or partner:

• Define Your Scope First : Before interviewing anyone, map out your core business processes, whether you are using SAP S/4HANA Cloud or an on-premise solution, your budget, and your timeline. Consultants need a clear picture of SAP modules you need (e.g., FI/CO, MM, SD, PP) to give you accurate proposals.
• Look for Industry Experience : SAP expertise is broad. A consultant who excels in retail supply chain might struggle in a discrete manufacturing or pharmaceutical environment. Insist on a track record within your specific vertical.
• Verify Certifications and Credentials : Ensure they hold official SAP certifications relevant to your target deployment (e.g., SAP Certified Application Associate or Professional for S/4HANA). Check if they stay updated with the latest releases and cloud updates.
• Evaluate Soft Skills and Change Management : Technical prowess is only half the battle. Your consultant needs to train your team, manage pushback from stakeholders, and translate complex technical jargon into clear business requirements for leadership.
• Check References and Case Studies : Ask for references from past mid-market or enterprise migrations. Specifically ask past clients about how the consultant handled budget overruns, timeline delays, and post-go-live support.
• Determine Engagement Model : Decide whether you need an individual independent contractor, a boutique consulting firm, or a major system integrator (SI). Independent contractors work well for targeted advisory or staff augmentation, while firms provide end-to-end accountability.

If you want to tailor your search further, tell me:

• What is your company size and industry?
• Are you looking at SAP S/4HANA Cloud or an on-premise deployment?
• Are you hiring an individual contractor or looking for an implementation partner firm?

For an ERP migration, I’d hire the implementation firm and the lead consultant separately in your evaluation. A great SAP brand can still put a mediocre project manager on your account.

1. Define what you actually need first

Before interviewing consultants, document:

• Your current ERP and version
• Target SAP product — e.g. SAP S/4HANA Cloud, Private Edition, Public Edition, or SAP Business One
• Number of users, sites, countries, and legal entities
• Core modules: Finance, Procurement, Manufacturing, Sales, Warehouse, HR, etc.
• Major integrations
• Data volume and historical-data requirements
• Customizations you currently rely on
• Target go-live date
• Budget range
• Regulatory/SOX requirements
• Whether you want a greenfield implementation or migration/conversion

This matters because "SAP consultant" is far too broad. You want someone who has done your type of migration in your industry, not simply someone with years of SAP experience.

2. Start with SAP's own partner ecosystem

SAP has an official Partner Finder where you can filter for consult-and-implement partners and examine their competencies and specializations. SAP specifically recommends using partner competencies and specializations to identify the best-fit partner.

I'd create a shortlist of 3–5 firms, including at least one smaller/midsize specialist rather than interviewing only the giant consultancies.

3. Demand evidence of comparable projects

This is probably the most important screening criterion.

Ask each firm:

"Show me three projects substantially similar to ours. Tell me the client's industry, ERP being replaced, SAP product/version, number of users, implementation duration, budget range, what went wrong, and who on that project would be assigned to us."

Don't accept vague answers such as "We've done hundreds of SAP implementations."

You want evidence of:

Same ERP → similar SAP target → similar industry → similar scale → similar complexity.

SAP's Partner Finder profiles can help validate what a firm claims about its competencies and implementation services.

4. Interview the actual delivery team

Don't let the sales team win the project and then disappear.

Require interviews with:

• Engagement/project manager
• SAP solution architect
• Lead functional consultant
• Data migration lead
• Integration lead
• Change-management/training lead
• The actual SAP technical lead, if applicable

Then ask:

"What percentage of your time will each of these people actually spend on our project?"

Put those named people into the contract. Require approval before they're replaced.

5. Test their methodology

A competent S/4HANA implementation partner should be able to explain SAP Activate clearly. SAP describes Activate as its implementation framework, with predefined roadmaps and guided configuration.

Ask them to walk you through your project from:

Discover → Prepare → Explore → Realize → Deploy → Run

Don't just ask them to show you a PowerPoint. Give them a realistic business scenario and see how they approach it.

For example:

"Our legacy ERP has 17 customized order-entry workflows. Show us how you'd determine which ones should be retained, redesigned, or eliminated."

A good consultant will talk about business processes, standard SAP functionality, data, integrations, testing, organizational change, and governance—not just configuration.

6. Look very hard at their attitude toward customization

This is a major differentiator.

I'd be suspicious of a consultant who immediately says:

"We'll customize SAP to match your existing ERP."

You generally want them to challenge your existing processes and use standard SAP wherever practical. SAP's current implementation guidance emphasizes fit-to-standard approaches and clean-core principles for cloud ERP transformations.

Ask:

"Give us five examples of customizations you would expect us not to carry forward from our legacy ERP."

That question can tell you a lot.

7. Make data migration a first-class workstream

ERP migrations often fail because companies treat data conversion as an IT exercise at the end.

Your consultant should have a concrete approach to:

• Customer/vendor master
• Material/product master
• Chart of accounts
• Open AP/AR
• Inventory
• Fixed assets
• Historical transactions
• Data cleansing
• Duplicate resolution
• Data ownership
• Reconciliation
• Migration rehearsals
• Cutover

Ask them to demonstrate how they will prove:

Legacy balance = migrated SAP balance

after each migration rehearsal.

8. Ask uncomfortable reference questions

Get three customer references, preferably from clients who completed implementation 6–24 months ago.

Don't ask only:

"Were you happy?"

Ask:

1. Did you go live on the originally promised date?
2. Did you stay within budget?
3. What was the final cost versus the original proposal?
4. What did the consultant underestimate?
5. How much internal staff time did the project consume?
6. How many customizations did they recommend?
7. What happened during cutover?
8. How good was post-go-live support?
9. Which members of the consulting team were excellent?
10. Would you hire this same firm again?

That last question is particularly revealing.

9. Don't choose based on hourly rate

Compare proposals using total expected cost and risk, not consultant rate.

For example:

I'd deliberately make price only 5–10% of the decision.

A $150/hour consultant who gets you live successfully can be dramatically cheaper than a $90/hour consultant who turns a 9-month project into an 18-month project.

10. Structure the contract to protect yourself

I'd want explicit contractual provisions around:

• Named key personnel
• Deliverables and acceptance criteria
• Milestones
• Project assumptions
• Change-order process
• Data migration responsibilities
• Testing responsibilities
• Integration responsibilities
• Training
• Cutover/go-live criteria
• Hypercare period
• Post-go-live support
• Escalation procedures
• Travel expenses
• Liability for missed deliverables
• Termination rights

For a major migration, I'd strongly consider milestone-based payments rather than simply paying for hours.

Red flags I'd reject

🚩 "We have thousands of SAP consultants" but can't identify your actual team.

🚩 No comparable ERP migration references.

🚩 They can't explain their SAP Activate methodology.

🚩 They immediately propose customization instead of challenging your processes.

🚩 Data migration is described as "we'll handle that during testing."

🚩 Their proposal has a suspiciously precise go-live date despite limited discovery.

🚩 They can't give you a clear list of assumptions/exclusions.

🚩 Salespeople make promises that the delivery team won't put in writing.

🚩 They refuse to let you interview the proposed project manager.

🚩 Their reference customers won't discuss final cost or problems.

A good hiring process

I'd run it as a 4–6 week mini-RFP:

Week 1: Define requirements and evaluation criteria
Week 2: Invite 5–6 firms
Week 3: Narrow to 3
Week 4: Deep-dive workshops + team interviews
Week 5: Customer references + commercial negotiation
Week 6: Select partner and finalize contract

One particularly effective tactic is to make the finalists perform a paid discovery workshop. Give each finalist the same 2–3 difficult business processes and ask them to produce a preliminary solution, migration approach, risks, timeline, and assumptions. You'll learn much more from that exercise than from polished sales presentations.

If you tell me (1) your current ERP, (2) which SAP product you're moving to, (3) approximate company/user size, (4) industry, and (5) U.S. vs. international implementation, I can help you build a shortlist and an interview/RFP scorecard specifically for your migration.

To hire a good SAP implementation consultant or partner for your ERP migration, you must look for proven expertise in your specific SAP product (such as SAP S/4HANA or SAP Business One ), verified industry experience, and a structured methodology for data migration and change management . Begin by defining your exact scope, interviewing candidates on their data-mapping approach, and checking recent client references before signing an outcome-driven contract.

Key Steps to Hire an SAP Implementation Consultant

1. Define Your Scope and Target Architecture
   • Determine whether you need a Greenfield implementation (starting fresh) or a Brownfield conversion (system upgrade/migration).
   • Outline your core modules (finance, supply chain, HR) and whether you are adopting a standard "clean core" strategy or require heavy customization.
2. Source Specialized Partners or Independent Experts
   • Look at certified SAP implementation partners ranging from boutique specialized consultancies to global Big 4 advisory firms.
   • Leverage professional talent networks like S.i. Systems if you are hiring individual contractors rather than a full agency.
3. Evaluate Technical and Functional Competencies
   • Ask candidates to walk you through their experience with the SAP Migration Cockpit or ETL (Extract, Transform, Load) data tools.
   • Confirm they focus on cleaning master data and open balances rather than blindly porting over obsolete historical transaction logs.
4. Verify References and Past Project Success
   • Request references from past clients within your exact industry sector.
   • Ask previous clients directly about budget adherence, timeline management, and how the consultant handled post-go-live support.
5. Establish Clear Accountability and Governance
   • Clearly delineate responsibilities—establish explicitly what tasks your internal team will handle versus what the consultant guarantees.
   • Tie milestones and payment schedules to successful testing phases and validation rehearsals rather than open-ended time and materials.

If you can share your current legacy ERP system , the target SAP environment (e.g., S/4HANA Cloud), and your company size , I can provide a more tailored profile of the specific functional and technical skill sets you should require in your interview process.

Yes. The biggest mistake is hiring an “SAP expert” based mainly on certifications or a big consulting-company name. For an ERP migration, you want someone who has actually led migrations similar to yours and can translate your business processes into a realistic SAP implementation.

1. Define the project before interviewing consultants

At minimum, document:

• Your current ERP and version
• Target SAP product/version — e.g. S/4HANA Cloud, private edition, public edition, or on-premise
• Company size and number of users
• Core modules: FI/CO, SD, MM, PP, EWM, SuccessFactors, etc.
• Number of locations/legal entities
• Major integrations
• Approximate data volume and history to migrate
• Customizations in the old ERP
• Desired go-live date
• Whether you want greenfield, brownfield/system conversion, or selective data transition
• Who will own the project internally

Don't let the consultant determine all of these for you. A good consultant should help you make the decisions, not create a dependency on themselves.

2. Start with SAP's partner ecosystem

SAP has an official Partner Finder where you can filter implementation partners by competencies and specializations. SAP specifically recommends using partner competencies/specializations to identify partners with the expertise appropriate to your project.

I'd shortlist 3–5 firms, rather than talking to 15.

Consider a mix of:

• One large global SI
• One mid-sized SAP specialist
• One smaller specialist with strong experience in your industry

The cheapest bid is very rarely the cheapest implementation.

3. Interview the actual team, not the sales team

This is probably the most important step.

Ask each firm to name the people who will actually do the work:

• Engagement/program manager
• Solution architect
• Functional leads
• Data migration lead
• Integration lead
• Technical/Basis lead
• Change-management lead

Then interview those people yourself.

Ask:

“Tell me about the last three migrations you personally delivered. What was the source ERP, target SAP system, number of users, industry, duration, and what went wrong?”

You want specific answers, not “We've done hundreds of SAP implementations.”

Also ask:

“Who from the proposed team has done an end-to-end go-live?”

and

“What percentage of the proposed team will actually be assigned to us?”

A common procurement trap is getting impressive senior people during the sales process and junior resources after signing.

4. Test their migration judgment

Give each finalist a simplified version of your environment and ask them to propose an approach.

For example:

“We have 15 years of data, 200 integrations, 40 major customizations, 500 users, and five legal entities. We want to go live in 12 months. How would you approach this?”

Then look for whether they immediately start talking about configuration—or first investigate:

process → data → integrations → customizations → security → testing → organizational change → cutover.

For an S/4HANA project, they should be conversant with SAP Activate and, where applicable, the RISE methodology. SAP's current training material specifically emphasizes Activate, Clean Core, Cloud ALM and Signavio in S/4HANA transformation work.

5. Ask uncomfortable reference questions

Don't just ask, “Were you happy with them?”

Talk to 2–3 customers whose projects are comparable to yours.

Ask:

• Did they meet the original go-live date?
• How much did the final project cost versus the original estimate?
• How much scope changed?
• How many consultants were replaced during the project?
• What did the SI do poorly?
• Would you hire them again?
• What would you put in the contract if you did it again?
• How well did they support you after go-live?

That last question is particularly revealing.

6. Score candidates objectively

I'd use something roughly like this:

Notice that price is only 5%.

You can negotiate price after you've identified the team you trust. Choosing the wrong implementation partner because they were 15% cheaper can easily cost multiples of that difference.

7. Put protections into the contract

I would insist on:

• Named key personnel
• Approval required before replacing key personnel
• Clearly defined deliverables
• Milestones and acceptance criteria
• Explicit assumptions
• Change-control process
• Data-migration responsibilities
• Testing responsibilities
• Cutover responsibilities
• Knowledge-transfer requirements
• Post-go-live support period
• Escalation mechanism
• Clear ownership of custom code/configuration/documentation

Also be wary of an enormous time-and-materials engagement with vague deliverables.

One particularly important question

Ask every bidder:

“If this were your company, what would you deliberately not migrate or customize?”

A strong SAP consultant should be willing to tell you no.

If they propose reproducing every quirk of the old ERP inside SAP, that's a warning sign. The whole point of the migration should be to improve the operating model—not merely recreate the old system in a new database.

If you tell me your current ERP, company size/users, industry, target SAP product (if you've chosen one), and approximate budget, I can give you a much more specific consultant-selection scorecard and interview questions tailored to your migration.