FK Solution DesignSalesforce Architecture
DEBook a call
← All articles

ServiceMax vs Salesforce Field Service: which one?

Fabian Kramer6 min read

ServiceMax from PTC and Salesforce Field Service do not sit on separate platforms. According to PTC’s service description of February 2025, ServiceMax Core runs as a package in the customer’s Salesforce org, with its own data model. PTC runs scheduling and optimisation on AWS. So you always buy Salesforce licences plus a second vendor. In my view ServiceMax pays off when depot repair, returns and rule-based entitlements shape your service and your PLM comes from PTC. Otherwise Salesforce Field Service is the simpler choice.

Does ServiceMax still run on Salesforce?

Yes. The question is fair, because PTC adds to the confusion itself. The FAQ on the product page1 says ServiceMax was originally built on Salesforce and is now a standalone platform with its own roadmap. PTC’s technical documents say something else:

  • The ServiceMax SaaS Service Description2 of 1 February 2025 names Salesforce data centres as the hosting location of Core and Asset 360.
  • The installation guide3 describes Core as a managed package on the Force.com platform, installed from AppExchange.
  • The August 2026 patch4 fixes a defect for users with a Salesforce Platform licence.
  • PTC’s German product page5 states that ServiceMax was developed as an application on the Salesforce platform.

ServiceMax is standalone as a product: it has belonged to PTC since 4 January 20236, and PTC decides the roadmap. The technical base is still Salesforce. I found no primary source for a platform change.

What does ServiceMax consist of today?

ServiceMax is a product family. Two core products and several add-ons matter for manufacturers. The details come from PTC’s documentation7 and the service description, as of October 2026:

Product What it is Where it runs
ServiceMax Core Complete field service suite with installed base, contracts, dispatch, inventory, returns, depot repair Salesforce org, own data model (work order as object SVMXC__Service_Order__c)
ServiceMax Asset 360 Extension for Salesforce Field Service Salesforce org, on the standard Field Service objects
ServiceMax Go Technician app with offline storage Syncs through a PTC gateway
Service Board, Schedule Optimization Dispatch board and optimisation PTC platform on AWS in Ireland
ServiceMax AI Assistant for technicians, since February 2025 Own package, language model not documented

The key point is in the first row. The work order in Core8 is a separate object with 207 fields, and the installed base is a separate object called Installed Product. Core does not use WorkOrder, ServiceAppointment and Asset from Salesforce Field Service; it builds a parallel model in the same org. Asset 360 does the opposite and extends the standard objects, see ServiceMax Asset 360: worth adding to Field Service?.

ServiceMax Core brings depot repair, returns and entitlements

The gap is smaller than ten years ago. Salesforce Field Service includes assets with hierarchies, maintenance plans, service contracts and entitlements in the base licence. The differences are in the workflows around the installed base.

ServiceMax Core lists spare parts, returns and depot repair, contracts with a rule-based entitlement engine and a Service Flow Manager for your own workflows as core functions. At Salesforce, depot repair, repair quotes and coverage selection come with the Asset Service Lifecycle Management add-on at $75 per user and month. What the add-on contains is in Asset Service Lifecycle Management: worth the add-on?.

With release 26R2, PTC added work plans with dependencies, intraday optimisation as often as every 15 minutes and part filtering by asset configuration, according to its overview of new features9. That targets complex repairs on machines with many variants.

The second difference is the PTC portfolio. PTC sells Windchill and Servigistics. Asset 360 has had connections to both10 since release 24R2, and Core data flows through a documented integration11 into PTC Orbit, PTC’s asset data platform. If engineering and spare parts planning already run on PTC, the paths are shorter.

Salesforce Field Service has the platform on its side. Enhanced Scheduling and Optimization, the Field Service mobile app, Agentforce for Field Service and the new features of each release work on the standard objects. None of the sources I read says whether they work with the Core objects. I assume they do not, and I would get it in writing before any selection.

A second vendor changes operations and data protection

These are the points most often missing from selection projects. All of them are in the service description of February 2025:

  • Availability. The availability commitment of the PTC agreement does not apply to the ServiceMax suites, because PTC does not control the hosting environments. PTC commits to commercially reasonable efforts. Salesforce is responsible for the Salesforce environment.
  • Data locations. Service Board and Schedule Optimization run on AWS in Ireland, Zinc on AWS in the US with customer data in the US. The list of sub-processors12 also names map services and Twilio.
  • Licences. Service Board needs one Salesforce licence for the integration. Every user needs a ServiceMax licence and a Salesforce licence.
  • Releases. Salesforce ships three releases a year. From 2027, ServiceMax follows four major releases a year according to its release schedule13, each with a four-week preview, plus monthly patches. Your test team checks two calendars.

Then there is PTC’s strategy. PTC sold ThingWorx and Kepware to TPG, announced in November 202514 and completed in March 2026. According to the announcement, PTC focuses on CAD, PLM, ALM and service lifecycle management. ServiceMax is part of that core. The IoT platform that the ServiceMax page still names as a connection now belongs to another company.

What I take from Field Service projects

I have not implemented ServiceMax myself, and I have not seen it in a selection against Salesforce. What I know are the places where field service projects at manufacturers get stuck.

None of these three depends on the product. A better entitlement engine does not help when the serial numbers in the ERP are wrong. So in a selection I weigh the question which product needs the fewest workarounds with your data and your interface higher than the feature list. How parts flow between the ERP and Salesforce is in Spare parts between ERP and Salesforce.

How do you choose between ServiceMax and Salesforce Field Service?

ServiceMax Core

  • Depot repair, returns and entitlement engine in the core
  • Work plans with dependencies for complex repairs
  • Connections to Windchill, Servigistics and PTC Orbit

What you accept in return

  • Two vendors, two release calendars, no PTC availability commitment
  • Own data model next to the Field Service objects
  • Scheduling data on AWS, Zinc data in the US
  • No public prices

My rule of thumb: Salesforce Field Service is the default for manufacturers who already run sales and service on Salesforce and mainly schedule maintenance and breakdown jobs. Whether Field Service pays off at all is covered in Salesforce Field Service: when is it worth it?. ServiceMax Core belongs on the list when repairs in your own depot, returns and contractual entitlements shape your service and your PLM comes from PTC. If you want to keep Salesforce Field Service and only add asset depth, Asset 360 is the variant I would look at first.

Mark the service processes with depot, returns and contracts

  1. List your service processes and mark the ones that involve the depot, returns and entitlement checks.
  2. Request two quotes: PTC including all Salesforce licences, Salesforce Field Service including add-ons. The role logic for Salesforce is in Salesforce Field Service licences by role.
  3. Ask PTC four questions in writing: data locations, availability, the language model behind ServiceMax AI and how it works with Salesforce features.
  4. Have the comparison calculated independently. How I compare such options is described under make-or-buy and licence forecasts.
Sources14
  1. 1product pageptc.com
  2. 2ServiceMax SaaS Service Descriptionptc-p-001.sitecorecontenthub.cloud
  3. 3installation guidesupport.ptc.com
  4. 4August 2026 patchsupport.ptc.com
  5. 5German product pageptc.com
  6. 64 January 2023investor.ptc.com
  7. 7PTC’s documentationsupport.ptc.com
  8. 8work order in Coresupport.ptc.com
  9. 9overview of new featuresptc.com
  10. 10connections to botharcweb.com
  11. 11documented integrationsupport.ptc.com
  12. 12list of sub-processorsptc.com
  13. 13release schedulesupport.ptc.com
  14. 14November 2025ptc.com

Frequently asked questions

Does ServiceMax run on Salesforce?

Yes, as of October 2026. PTC states that ServiceMax Core and Asset 360 are hosted in Salesforce data centres, and Core is installed as a managed package from AppExchange. PTC also runs Service Board and Schedule Optimization on AWS in Ireland.

Do I need Salesforce licences for ServiceMax?

Yes. PTC's documentation assigns the ServiceMax licence to users with a Salesforce, Salesforce Platform or Community licence. For Asset 360, PTC also requires Service Cloud and at least one Field Service licence.

Is ServiceMax part of Salesforce?

No. ServiceMax has belonged to PTC since 4 January 2023; the deal was announced at $1.46 billion. Salesforce is the platform provider and a competitor with its own Field Service product.

How much does ServiceMax cost?

PTC does not publish prices. Expect a quote from PTC plus Salesforce licences for every user, and compare both with the list prices of Salesforce Field Service.

Related serviceArchitecture & solution design →

Contact

Does Field Service pay off for your technicians?

Whether scheduling and route optimisation pay off depends on a few numbers. With them I can give you a first assessment in 30 minutes.

What to bring

  • The typical job duration: closer to one hour or to several days per job
  • Travel time to the customer and how many jobs a technician completes per day
  • How you plan today, with how many dispatchers and how much effort per week

What we clarify

  • Whether your jobs benefit from Field Service or a leaner setup is enough
  • Which KPIs scheduling and route optimisation can improve
  • Which master data and interfaces, for example to the ERP, have to be in place first
Book a call

Pick a slot in my calendar via Microsoft Bookings. Prefer to write? Use the form and I’ll get back to you.

Rather talk right away? +49 221 98656758

Send a message

Your details are only used to answer your request. More in the privacy policy.