Skip to content

Migration guide · Customer Service

ServiceNow to Agentforce IT Service migration

ServiceNow ITSMSalesforce Agentforce IT Service

Short answer

Moving from ServiceNow to Salesforce's Agentforce IT Service brings incidents, requests, knowledge and the service catalog onto Salesforce, so firms already on Salesforce can run IT service management on the same platform with AI agents.

Why firms make this move

Salesforce entered IT service management with Agentforce IT Service. Firms invested in Salesforce look at it to consolidate tools and licences and to apply AI agents to employee support. The migration covers incidents and requests, the catalog, knowledge, assignment groups and integrations with monitoring and identity tools.

What moves

  • Incidents and requests with history
  • Service catalog items
  • Knowledge articles
  • Assignment groups and routing
  • Integrations with monitoring and identity tools

How the data maps

FromTo
IncidentIncident record
Request itemService request
Catalog itemCatalog item
Knowledge articleKnowledge article
Assignment groupQueue or group

See the field-by-field map ↓

What to watch out for

  • Feature parity for complex ITSM processes
  • Integrations with monitoring tools
  • Contract end dates
  • Change management for IT staff

How Vantage Point runs the migration

  1. Assess fit and feature gaps
  2. Design processes and catalog
  3. Migrate data and knowledge
  4. Rebuild integrations
  5. Configure AI agents and test
  6. Cut over and support

Typical timeline

Typically 8 to 16 weeks.

Frequently asked questions

Is Agentforce IT Service ready for us?

It depends on how complex your ITSM processes are. We start with a fit assessment.

Can AI agents resolve employee requests?

Yes, for well-defined requests with clear knowledge and permissions, with people handling the rest.

Last reviewed October 2, 2026 by the Vantage Point team. Browse all migration paths →

Field-level map

ServiceNow to Agentforce IT Service: field by field

3 mappings we start from on this migration, 2 of which need a transform, a lookup or a decision. Every project gets its own signed-off version; this is the baseline.

FromToHowNotes
Knowledge articleArticles Knowledge article— direct
Assignment groupGroups Queues— lookup
Business rule / flowAutomation Flow— rebuild

Field names are the platforms' standard API names; your org's custom fields are mapped during discovery. What the "How" labels mean

How labels
direct
Value copies across unchanged.
picklist map
Each source value is mapped to a target value.
lookup
Matched to an existing record, such as a user by email.
association
Becomes a relationship between records, loaded in a later pass.
derive
Calculated or cleaned during the load.
split / concat
One field becomes several, or several become one.
rebuild
Configuration or automation that is rebuilt rather than moved.
drop
Not migrated, deliberately.
manual review
Needs a decision with your team before the load.