On a Friday afternoon, the IT director of a mid-sized distribution company in Bavaria receives the resignation of the only ABAP developer on the team. In a month, nobody will know the interfaces to the warehouse system, the custom controlling reports or the dozens of enhancements added over the last ten years. A permanent opening for a second developer has been advertised for four months without a single credible candidate. And the board has just approved the budget for the move from SAP ECC 6.0 to S/4HANA, with the assessment due to start in spring.
The IT director has three questions. Will a contract SAP consultant solve the problem faster than recruiting? What will it cost compared with a permanent hire or a systems integrator? And how can she be sure the person who arrives really knows what the system needs, rather than just having “SAP” on the CV?
This article is for the IT director or SAP team lead facing that decision. We explain where today’s pressure on SAP skills comes from, how the most commonly requested roles differ, what a contract consultant costs and what drives the rate, how to write the brief and vet candidates, what to put in the contract and which mistakes to avoid.
Why is demand for SAP consultants rising right now?
Because SAP’s calendar forces thousands of companies to make the same decision at the same time. In February 2020 SAP announced the timeline that, with minor additions, still applies. Mainstream maintenance for SAP Business Suite 7, including SAP ECC 6.0 on the latest enhancement packages, ends at the end of 2027. Optional extended maintenance runs from 2028 to the end of 2030 at a premium of two percentage points on the maintenance basis. Customers who do not opt for extended maintenance but keep running Business Suite 7 move to customer-specific maintenance, a narrower service.
In January 2025 SAP added another path: a transition option for SAP ERP, private edition covering 2031 to 2033. According to SAPinsider’s September 2026 summary, it is a subscription that can be bought from 2028 and used from 2031 to 2033, and requires moving to SAP ERP, private edition on SAP HANA before the end of 2030. SAP stresses that it is not a maintenance extension for SAP ERP, and CEO Christian Klein described it as aimed at “very few large customers”. For S/4HANA, SAP has committed to maintenance until at least the end of 2040.
What does that mean for an IT department? A company on ECC now has roughly four years until the end of extended maintenance and a little over a year until mainstream maintenance ends. In that time it has to assess its options, choose a path (new implementation, system conversion or a selective approach), clean up data and custom code, train people and migrate. Every stage needs SAP consultants, and the supply of experienced specialists is not growing as fast as demand.
The choice of migration path also shapes who you need. A greenfield implementation redesigns processes, so functional consultants who can run workshops with the business and consciously drop old solutions matter most. A brownfield conversion carries existing processes and code across, so Basis administrators and ABAP developers who can analyse and adapt custom code come first. A selective approach needs both, plus data migration specialists. Before hiring anyone, it helps to know which way the decision is heading, because it sets the order of roles.
Market data reflects the squeeze. The Freelancer-Kompass 2026 by freelancermap, based on a survey of 5,412 freelancers in the DACH region, found that SAP and ERP specialists have the highest median hourly rate in IT: EUR 120, up from EUR 115 a year earlier. The median for all IT freelancers is EUR 95, and the average rate across the whole freelance market fell for the first time. In other words, the IT market is cooling, but SAP is not.
Which SAP roles are requested most and how do they differ?
“SAP consultant” is as broad a label as “doctor”. Before you request a specialist, decide which of the roles below you need. Getting this wrong is the most expensive mistake in the whole process.
ABAP developer. Writes and maintains code in the SAP system: enhancements to the standard, reports, interfaces, forms, data conversions. In the S/4HANA world this increasingly means modern ABAP syntax, CDS views, the ABAP RESTful Application Programming Model and extensions that respect the “clean core” principle. A developer who spent fifteen years writing classic ECC reports and a developer with S/4HANA experience are two different roles, even if the job titles match.
FI/CO consultant. Finance and controlling: general ledger, accounts payable and receivable, fixed assets, cost accounting, product and profitability controlling. A functional consultant who talks to accounting and controlling and turns their requirements into configuration. Particularly important in an S/4HANA migration, because the financial data model changes.
SD/MM consultant. Sales and distribution (orders, pricing, deliveries, billing) and materials management (purchasing, inventory, stock valuation). Often requested alongside warehouse logistics consultants when a company has complex distribution processes.
Basis administrator. SAP infrastructure and technology: installations, upgrades, transports between systems, performance, backups, databases, technical authorisations. In a migration to S/4HANA and SAP HANA, Basis is one of the critical roles.
S/4HANA migration architect or lead. Runs the readiness assessment, choice of migration path, project plan and coordination of teams. In this role, experience from previous migrations matters more than depth in one module.
SAP BTP and Fiori/UI5 developer. Extensions built outside the core on SAP Business Technology Platform, and modern Fiori user interfaces. Under a clean-core approach, this is where some of the logic goes that in ECC went straight into ABAP inside the system.
The table below matches roles to situations and shows what to check in a candidate.
| Role | When you need it | What to check in the candidate |
|---|---|---|
| ABAP developer | Maintaining enhancements, interfaces, preparing custom code for migration | S/4HANA experience, CDS, RAP; examples of custom code analysis |
| FI/CO consultant | Changes to finance processes, year-end close, financial data migration | Number of full close cycles, ECC migration projects, local GAAP and tax requirements |
| SD/MM consultant | Changes to sales, purchasing, inventory, integration with logistics systems | Pricing and delivery configuration, WMS and EDI integrations |
| Basis administrator | Upgrades, transports, performance, move to HANA | System conversion, database migration and upgrade experience |
| S/4HANA migration lead | Assessing and planning the move from ECC | How many migrations led, which path, with what outcome |
| BTP and Fiori/UI5 | Clean-core extensions, new user interfaces | BTP projects, Fiori apps in production |
Contract consultant, systems integrator or permanent hire?
A contract consultant is one of three routes and not always the best one. An honest comparison looks like this.
A systems integrator takes responsibility for the project outcome: it brings a methodology, a team, project management and often part of the licences or cloud services. It is the right choice when the company has no capable in-house SAP team and needs someone to run the whole migration. It costs the most, and many project decisions sit with the integrator.
A contract consultant (staff augmentation) strengthens your team. They work under your management, in your processes and tools, and responsibility for the outcome stays with you. It is the right choice when you have an SAP lead or architect and need specific skills: a second ABAP developer, an FI/CO consultant for a finance change, a Basis administrator for an upgrade window. It also works alongside an integrator when you want your own people in the project who understand the system and stay after go-live.
If you already work with an integrator, a contract consultant does not need to compete with it. A common and sensible setup: the integrator owns the methodology, plan and delivery of the migration, while consultants hired by the client sit in the client’s team as its experts. They review the integrator’s proposals, prepare data and code on the client side, run acceptance tests and absorb the knowledge that stays in the organisation after the project. That setup needs a clear split of responsibilities agreed up front, so nobody has to argue later about who owns a configuration error: the integrator who designed it or the client’s consultant who approved it.
A permanent hire is best for stable roles with ongoing demand over years. The problem is that recruiting experienced SAP specialists takes a long time, and during the migration peak competition for the same people is intense. Our own pricing page is explicit that for a stable role lasting several years, direct hiring is usually cheaper per productive hour.
In practice many companies combine the three: an integrator runs the migration, contract consultants reinforce the client team, and permanent staff take over knowledge and maintenance. The broader trade-offs are covered in our glossary entry on staff augmentation, and how risk is shared across billing models in our article on team subscription, time and materials and fixed price.
What does a contract SAP consultant cost?
At ARDURA Consulting, according to our pricing page, a senior SAP specialist costs EUR 465–745 per 8-hour day, net. The roles we list for SAP are ABAP, SAP S/4HANA, SAP BTP and Fiori/UI5. Junior and architect rates are quoted on request. The rate covers everything: the specialist’s pay, taxes, insurance, equipment and our management overhead. There are no recruitment fees, no setup costs and no termination penalties. You pay for days worked, invoiced monthly, and the rate is locked for the duration of the engagement.
For context, senior rates for other roles on the same page are EUR 335–485 per day for developers and EUR 485–650 for tech leads and architects. The SAP rate is clearly higher than for a typical developer, which matches the market picture above.
How does that compare with local options? The Freelancer-Kompass 2026 median of EUR 120 per hour for SAP and ERP freelancers in DACH comes to about EUR 960 for an eight-hour day. Keep in mind that this is a freelancer who carries their own bench risk, not a service with a replacement guarantee, and that a median hides a wide spread: experienced S/4HANA migration specialists in Germany or Switzerland often charge well above it. We have not found an equally robust public survey for UK SAP contractor rates, so we do not quote one; ask two or three agencies for current day rates in your module before comparing.
How to budget? Day rate × working days per month × months. For one senior at 21 working days a month and a rate within ARDURA’s range, that is EUR 9,800 to 15,600 per month. As an illustration of the method for a whole pre-migration phase: an ABAP developer and an FI/CO consultant for six months plus a Basis administrator for three months is 15 person-months. At 21 days a month and a mid-range rate of EUR 600 per day, the budget would be about EUR 189,000; at the bottom of the range about EUR 146,000, at the top about EUR 235,000. Treat that as an order of magnitude for a board discussion, not a quote. Add your own team’s time for onboarding, an SAP user licence of the right type for the external consultant (check with your licensing team) and travel if part of the work is on site.
What drives an SAP consultant’s rate?
The range is wide because “SAP specialist” covers very different profiles. Several factors set where in the range a person lands.
Module or technology. Rare skills cost more than common ones. Experienced consultants in narrow areas, such as industry-specific solutions, cost more than those in the most widely implemented modules.
S/4HANA experience. A consultant who has migrated a system from ECC to S/4HANA is worth more today than one with equally long ECC-only experience, because that knowledge is what the market lacks.
Role in the project. Someone executing tasks within an agreed design costs less than someone creating the design and running workshops with the business.
Working language. A project run in English, German or another language draws on different candidate pools. A German-language requirement narrows the choice most. Some of our engineers speak German; tell us if your team works in German and we will shortlist for it.
Length and form of engagement. Longer commitments may qualify for volume discounts. Remote work widens the pool; on-site requirements narrow it.
Urgency. A start next week narrows the pool of available people. If you can plan the start three or four weeks ahead, you have more choice.
Industry and regulation. An FI/CO consultant who already knows your local accounting and tax reporting, or a logistics consultant with batch traceability experience in pharma or food, brings knowledge you do not have to teach. That specialisation pushes the rate up, but usually shortens onboarding and reduces errors in the first months.
When comparing vendors, ask not only about the rate but about the profile behind it. Two identical rates can mean very different experience.
How do you brief the role to get the right candidate?
The best vendor cannot find the right person from a request that says “we need an SAP consultant urgently”. A good role brief takes an hour and saves weeks. It should cover:
System version and landscape. ECC 6.0 on which enhancement package, or S/4HANA and which release, cloud or on-premises, and the surrounding systems (warehouse, e-commerce, CRM, BI).
Modules and processes. Not just “FI/CO” but specific areas: “accounts receivable, credit management, bank integration”. Not just “ABAP” but “IDoc interfaces to the warehouse system and invoice forms”.
Tasks for the first three months. A list of concrete tasks tells a vendor more than a list of technologies. “Take over maintenance of 40 enhancements from the departing developer and inventory them for migration” is a clear brief.
Level of autonomy. Will the consultant work under your architect’s direction, or run workshops and make design decisions?
Language, location, working hours. Language of documentation and meetings, remote or on site, any on-call duties during month-end close.
Start date and expected duration. Even if approximate.
An example of a good brief, in short: “SAP ECC 6.0 EHP7 on Oracle, conversion to S/4HANA planned for 2027. Senior ABAP for six months, start 1 December. Tasks: take over maintenance of about 40 enhancements and 12 IDoc interfaces from a departing developer, inventory custom code for migration, fixes raised by controlling. Works under our SAP team lead, in English, remote with one day a week on site during onboarding. Custom code analysis before conversion is a plus.” A brief like that lets a vendor judge in a day whether it has the right person, and lets the candidate decide whether the project interests them.
For migrations, add one more item: the state of the assessment. A consultant joining after the migration path is chosen needs different skills from one who is meant to help choose it.
How do you vet an SAP consultant before signing?
SAP CVs tend to be long and similar. Vetting should establish what the candidate actually did, not which projects they watched from a distance. Some questions that work well:
For an ABAP developer: “Describe the last enhancement you wrote from scratch: what was the business problem, which techniques did you use and how did you test it?” “How would you approach custom code analysis before an S/4HANA migration?” “When would you use a CDS view instead of a classic query?” A short practical task or a code review exercise also helps.
For an FI/CO or SD/MM consultant: “Walk me through the configuration of the last process you implemented, from business requirement to acceptance test.” “What was the hardest year-end close problem you dealt with and how did you solve it?” “What changes in your module when moving from ECC to S/4HANA?”
For a Basis administrator: “Describe the last upgrade or conversion you ran: how long was the downtime, what went wrong, how did you fix it?” “How do you manage transports across a multi-system landscape?”
For a migration lead: “How many migrations have you led, by which path, and why that one?” “What would you do differently on your last project?”
References and projects. Ask for two or three recent projects with the candidate’s role, system size and SAP version. Probe for details only someone inside the project would know: how long the system freeze lasted, how a master data conflict was resolved, what went wrong in the first migration test. Generic answers to specific questions suggest the candidate observed the project rather than shaped it.
Vetting should include someone from your side who knows the system: the SAP team lead, an architect or an experienced key user. The vendor does the first screening, but you decide who joins the team. At ARDURA Consulting the shortlist is two to four vetted seniors, and you interview and approve every candidate.
Which engagement model suits SAP roles?
Three models are common for contract SAP consultants. ARDURA Consulting offers all three for IT staff augmentation from Poland.
Time and materials. Billing against timesheets, invoiced monthly. The most flexible option when scope is evolving or capacity varies.
Capped time and materials. Time and materials with a pre-agreed monthly cap. It combines cost certainty for you with flexibility on hours within scope, which suits a budgeted pre-migration phase.
Dedicated team. A multi-person team committed full-time to your project, with a single team lead and a lower effective rate, typically for engagements of six months or more. Assembling it takes four to six weeks.
Whatever the model, be clear about who owns the outcome. In staff augmentation, the client does: the consultant does the work, but design decisions and acceptance are yours. If you want the vendor to own the outcome, you need a project contract, not augmentation.
What should the contract with the vendor include?
A service agreement with a company supplying a specialist is not the same as a freelancer contract. Your counterparty is a company, not an individual. Check a few provisions carefully.
Ownership of code and documentation. Every enhancement, report and configuration document should transfer to you, ideally on creation or payment. Check that the vendor has matching agreements with the specialist.
Confidentiality and data. An SAP system holds financial, HR and commercial data. The contract should cover an NDA, GDPR data processing terms if the consultant accesses personal data, and an obligation to return or delete data at the end.
Access and authorisations. Who grants the consultant system access, with what scope, and when it is revoked. In SAP, segregation of duties matters: a consultant who can change production configuration should not also approve their own transports.
Contractor status rules. In the UK, IR35 off-payroll rules, and in Germany, the rules on disguised self-employment (Scheinselbstständigkeit), affect how contractors are engaged. With ARDURA Consulting the engagement is a B2B service agreement between two companies, so you do not contract an individual or their personal company. That changes who your counterparty is but does not make the rules irrelevant, and our article on IR35 and engineers from Poland explains where the line runs. For German, Austrian and Swiss buyers, our overview of nearshoring contract models for DACH covers the options.
Replacement and continuity. What happens if the consultant is not a fit or leaves. ARDURA Consulting provides a two-week satisfaction guarantee with free replacement and a replacement within five business days if a specialist leaves mid-engagement.
Notice period and knowledge transfer. Notice should be long enough to hand over knowledge; with ARDURA it is 30 days. Write in an obligation to prepare documentation and run handover sessions before the end.
Rate and changes. Whether the rate is fixed for the engagement and how overtime, month-end on-call and travel are billed.
How do you onboard an SAP consultant in the first two weeks?
A contract consultant costs the same in week one as in week ten, so fast onboarding translates directly into value. Before day one, prepare:
Accounts and access. Users in the development, test and, if needed, production systems with the right authorisations for the role. VPN, email, ticketing and documentation access. An SAP user licence of the right type.
A system map. Landscape overview, interface list, list of enhancements with business owners, the transport process and release rules.
A buddy. One person on your team who answers questions in the first days and introduces the consultant to key users.
A first task. A small, concrete task for week one that lets the consultant learn the system and lets you judge their work. The satisfaction guarantee runs for the first two weeks, so this is the moment to see real work, not just an interview.
After the first month, hold a short review: what the consultant delivered, where they needed most help, and whether the scope still matches the brief. If the scope has shifted, for example from maintenance to migration work, check with the vendor whether the profile still fits. It is better to adjust early than after six months in the wrong configuration.
If the consultant is taking over from someone who is leaving, plan an overlap. Even a week of working side by side is worth more than the best documentation.
Which mistakes do companies make when hiring SAP consultants?
Requesting “SAP” instead of a role. A request for “an SAP consultant” without module, version and tasks produces candidates who do not fit. The role brief is the best investment in the whole process.
Confusing ECC tenure with S/4HANA experience. Fifteen years in ECC is valuable process knowledge, but it does not replace experience with the new data model, new development tools and migration paths.
Nobody on the client side to vet candidates. A vendor can screen, but only your team knows what the system really needs.
Waiting until 2027. The closer the end of mainstream maintenance, the fiercer the competition for the same specialists. Companies that start earlier get better choice and lower risk.
Depending on one outsider. A contract consultant should strengthen the team, not replace the company’s knowledge. Plan knowledge transfer from the first month.
No plan for after the migration. Consultants hired for a migration leave after go-live, and the support team must know the new data model and tools. Decide who takes over after go-live and whether you need a consultant for the stabilisation period, usually the first few month-end closes.
Forgetting licences. Every additional SAP user, including external ones, needs an appropriate licence. Better to know before your licensing team discovers it during an audit.
How do you hire an SAP consultant through ARDURA Consulting?
The process starts with a conversation about the role and follows our two-week onboarding SLA.
Days 1–3: role specification. You tell us the module or technology, system version, tasks and start date, and we sign off the role spec together. For SAP, we confirm availability for your module and start date on this call.
Days 4–6: shortlist. Two to four vetted senior candidates.
Days 7–9: your interviews. You interview the candidates and choose who joins your team.
Days 10–12: contracts. A B2B service agreement between your company and ARDURA Consulting.
Days 13–14: onboarding. The consultant has access and a first task.
Guarantees and terms. A two-week satisfaction guarantee with free replacement, a replacement within five business days if a specialist leaves, 99% specialist retention, a one-month minimum on a rolling monthly contract and 30 days’ notice. No recruitment fees.
For an overview of senior rates across other roles from Poland, see our article on body leasing rates in Poland in 2026, and for more on the model itself, our staff augmentation hub.
What should you remember before hiring a contract SAP consultant?
SAP’s calendar is unforgiving: mainstream maintenance for ECC 6.0 ends at the end of 2027, extended maintenance at the end of 2030, and the 2031–2033 transition subscription is for a few large customers and is not a maintenance extension. Demand for experienced consultants is rising, and market rates show it.
Before you request a specialist, define the role: ABAP developer, FI/CO or SD/MM consultant, Basis administrator, migration lead or BTP and Fiori developer. Brief the system version, modules, first three months of tasks, level of autonomy, language and start date. Vet candidates with questions about specific projects, with someone from your team who knows the system. An hour on a good brief and two on a proper interview are the cheapest insurance against months of paying for the wrong person.
A contract consultant works when you have your own SAP leadership and lack specific skills. A senior SAP specialist from ARDURA Consulting costs EUR 465–745 per day. In the contract, cover IP, confidentiality, authorisations, contractor status, replacement, notice and knowledge transfer.
If you need a contract SAP consultant, see how IT staff augmentation from Poland works with ARDURA Consulting or book a call about the role. Tell us the module and the start date, and we will confirm availability and put candidates in front of you.