How to Set Up a Cross-Platform Integration Between Your ITSM Tools

Most IT organizations end up with at least 2 service management platforms: Jira internally, ServiceNow or Zendesk on the customer-facing side, Salesforce for the CRM layer, or some combination across teams, business units, and external partners. 

When that happens, the pressing question now boils down to keeping these systems in sync without copying things manually.

This surfaces in a few predictable ways. A company adopts a second platform (ServiceNow alongside Jira or Zendesk alongside Salesforce) and, within a few months, the manual overhead of keeping both systems current becomes a real drag on the team. 

The real difficulty is controlling what flows where and making sure both sides can manage their own rules without depending on each other. 

Why Most Integration Setups Break at the Control Layer

There are 3 common approaches, and each one fails at a different point.

1. Native connectors (built-in integrations between platforms) are quick to set up. But field mapping is shallow. You typically can’t control what goes out vs. what comes in independently. And for cross-company use cases, native connectors often fail because they assume both platforms are managed by the same organization.
2. iPaaS and middleware tools (Workato, MuleSoft, etc.) give you more flexibility. You can map fields, build conditional logic, and connect a wider range of platforms. But the integration logic lives in a shared config. You also don’t get independent control over what leaves your system vs. what enters theirs.
3. Custom API scripts give you full control to write exactly the integration you need. But now your engineering team maintains it as a side project. Every API version change, every new required field, every workflow update on either side requires developer time. 

The common thread across all 3: you either give up control over your data or you take on ongoing maintenance. A good integration needs both sides to manage their own sync rules independently, without creating engineering overhead every time something changes.

How a Centralized Console Approach Solves the Problem

A newer approach to cross-platform integration puts everything in a single web-based workspace. 

You no longer need to install anything on the other party’s platform. Just sign in to your console, initiate a connection to the target system, and configure your sync rules from one place.

Each side of the connection configures its own rules independently. You decide which work item types trigger a sync, which fields get sent, and how your statuses map to the other side’s statuses. The other team decides where tickets land, what fields populate, and how incoming data maps to their workflows.

This means you can change a status mapping or add a new field to the sync without coordinating with the other team. They can do the same on their end without breaking yours.

How to Set Up a Cross-Platform Integration Using Exalate

1. Sign in to the application’s console. Log in and link your platform instance (Jira, ServiceNow, Zendesk, Salesforce, Azure DevOps, etc.). The other party only has to accept the connection invitation from their side.
2. Initiate the connection from your side of the platform pair. When connecting to ServiceNow, you pick the ServiceNow instance to sync to. The connection is enabled between the two, and they don’t need admin privileges on the other side.
3. Configure your outgoing sync rules. Select the type of issues that will cause syncs (just incidents or incidents and service requests or all in a particular project). Map the fields using AI-powered scripting: summary, description, priority, status, comments, attachments. Change the status mapping: “In Progress” is equal to “Work in Progress”.
4. The other side configures its incoming rules. They set where incoming tickets will be placed, what fields will be filled and how they want to deal with incoming status changes. They don’t have to look at your configuration and you don’t have to look at their configuration.
5. Test with real tickets. On your side, create a test ticket and ensure that you see it on the other side with all of the correct fields in the correct project in the correct status. Before going live, add a comment to ensure that the bi-directional flow is working.
6. Set up triggers. Set up the conditions to which the synchronization will be applied, without the requirement to move the entities manually.

The result is a sync where both sides have full operational control over their own data, without either side depending on the other’s admin access or configuration decisions.

Some Practical Use Cases for Cross-Platform ITSM Integration

Cross-Company Ticket Sync

A managed services provider running ServiceNow needs to sync incidents and service requests with a client’s Jira instance. The MSP controls what gets sent to the client. The client controls how tickets are received on their side without sharing admin access. 

This is a common occurrence in outsourcing IT services, in which the MSP’s team carries out L1/L2 triage and the client’s internal team performs L3 engineering tasks. The tickets must be shared across systems but each must have their own data as well as their own workflows.

Post-Acquisition Tool Consolidation

If two companies were to merge, each with 1,400+ Jira users, and one company has Zendesk, and the other has a bunch of standalone Jira instances from previous acquisitions, a full migration may take a year or more. For the time being both parties must remain attuned to customer-related matters.

A bi-directional integration allows them to continue to work in their own tools, but keeps the tickets that should be visible on both sides synchronized. The sync rules are automatically updated for individual instances as they get migrated or retired without disruption to the rest of the integration.

Customer Support to Engineering Escalation

When your support team runs Zendesk and engineering works in Jira, escalations create friction unless the two systems talk to each other. An escalated support ticket automatically generates a Jira issue with the correct priority, context and customer details when synced bi-directionally.

If engineering resolves the issue, the status will be sent back to Zendesk, and the support agent will see the change without having to log into Jira. Comments are synced both ways and engineering and support are able to communicate through their tools.

This is a common pattern for teams with a few hundred active tickets at any given time, where manual copying between systems would take hours of overhead per week.

Partner or Vendor Collaboration

A contractual obligation means that both tickets must be synced to your system and a partner’s system. Incidents must be coming in and out, as must service requests and/or change records. You cannot publish your internal project structure, internal comments or custom field information to an external party.

Independent sync rules allow you to share only what is required (ticket summary, priority, status, and external-facing comments) and maintain all the other information internal. The partner sets up the other side in the same manner.

Common Mistakes to Avoid in Cross-Platform Integration

• Syncing everything at once. Teams that try to sync every field on day one spend more time troubleshooting mapping conflicts. Start with one issue type and a small set of fields. Get the core flow stable before adding complexity like attachments and custom fields.
• Ignoring status mapping. If your Jira workflow has 8 statuses and ServiceNow has 5, you need an explicit mapping for each one. Default mappings often pick the wrong target status, and tickets end up in the wrong queue or stuck in a transition.
• Skipping sandbox testing. Field behavior in production (character limits, mandatory fields, custom field types) doesn’t always match what you’d expect. A description field that accepts 50,000 characters in Jira might hit a character limit in ServiceNow and silently truncate. Test with real ticket data in a staging environment before going live.
• Single point of contact. If one person manages the entire integration, you’ve got a bottleneck. When that person goes on vacation or changes roles, nobody knows how the sync is configured or how to troubleshoot it. Make sure at least 2 people understand the connection setup, the sync rules, and where to look when something breaks.

What to Look for in an Integration Tool

If you’re evaluating tools for cross-platform ITSM integration, here’s what matters:

• Independent configuration on each side. You shouldn’t need to coordinate every change with the other team. Each side should control what gets sent, what gets received, and how fields and statuses map.
• A web-based console that doesn’t require installation on the other party’s platform. This is especially important for cross-company use cases. A unified console that handles the connection from one place removes that friction.
• Support for the specific platform pair you’re connecting. The tool should handle the pair you need today and the pairs you might need as your environment changes.
• Script-level control for complex field mappings. Basic field mapping gets you started, but real-world sync rules often need conditional logic. You need the ability to write those rules.
• Version history for configuration changes. When a sync breaks after someone updates a rule, you need to see what changed and roll it back. 

Before You Go

Exalate handles cross-company ITSM integration through a unified web console, with independent sync rules on each side and support for 36 platform pair combinations across Jira, ServiceNow, Zendesk, Salesforce, Azure DevOps, and more. 

If you have a cross-company integration scenario you want to implement, reach out to us to discuss the details.