Migrate from ManageEngine SupportCenter Plus to Zendesk

SupportCenter Plus Requests map directly to Zendesk Tickets. We map status (Open, Pending, Resolved, Closed) to Zendesk Ticket Status values, priority (Low, Medium, High, Urgent) to Zendesk Priority, and category/subcategory to a combination of Zendesk Tags and custom fields depending on the destination field structure. All Request UDFs cross-reference the Field Labels admin table against raw udf_* column names during discovery so we map to correctly labeled Zendesk custom fields. Conversation threads migrate as Zendesk Comments linked to the Ticket.

SupportCenter Plus Accounts represent customer organisations and serve as the parent entity for Contacts and Contracts. They map to Zendesk Organizations (or optionally to Zendesk Companies if the Zendesk Suite Professional or higher is in use and the Companies feature is enabled). We use Account Name as the dedupe key during import and preserve any Account-level custom fields. Multi-portal accounts that exist under different portals are consolidated into a single Organization in Zendesk unless the customer opts for a multi-brand setup.

SupportCenter Plus Contacts map to Zendesk End Users. The Contact-to-Account relationship becomes the User-to-Organization relationship in Zendesk. We resolve the organization_id at import time so that every Contact lands under the correct Zendesk Organization. Any custom contact fields migrate as typed Zendesk user fields.

SupportCenter Plus Contracts define SLA terms and billing periods per Account. Zendesk has no native contract object. Contracts migrate as a custom Zendesk field (dropdown or text based on contract type) on the Organization or Ticket, referencing the contract identifier and entitlement tier. We flag expired or inactive contracts during scoping so they can be archived or excluded from active billing scopes. For customers with complex entitlement logic, we discuss whether a separate contract tracking tool is preferred.

SupportCenter Plus Products are linked to Accounts and used to scope support entitlements. Zendesk has no native product catalog. Product associations migrate as a custom Ticket field (dropdown) referencing the product name, with the product-to-account relationship preserved by cross-referencing the source Product-Account linkage. Customers with complex product-entitlement rules may choose to maintain a separate product database and link via Zendesk's Sunshine Objects API.

KB articles are organized into categories and linked to Products or general topics in SupportCenter Plus. Category structure and article-to-product associations require field-level mapping to match the Zendesk Help Center taxonomy. We migrate articles as HTML content into Zendesk Guide sections, preserving author, last-modified date, and attachment links. Portal-specific KB categories are consolidated into a single Help Center structure unless the customer requires multi-brand KB separation available via Zendesk Suite add-ons.

SupportCenter Plus User accounts carry role-based permissions and portal assignments. We map technician identity by email match to Zendesk Agents. Permission structures do not translate 1:1 because SupportCenter Plus RBAC and Zendesk's agent role model (Agent, Admin,light agent) differ in granularity. We flag role discrepancies during scoping and deliver a written recommendation for Zendesk role assignment based on each user's SupportCenter Plus permissions.

SupportCenter Plus Comments are linked to Requests via a junction table. We extract all comments with the original author (agent or end user), timestamp, and visibility (internal or public), and associate them with the migrated Ticket ID in Zendesk. Public comments from the requester become requester comments in Zendesk; internal comments become agent comments. The chronological order of the thread is preserved by setting the Zendesk comment timestamp to the original SupportCenter Plus timestamp.

Attachments in SupportCenter Plus are stored on disk or in the database depending on installation configuration. We locate the attachment store path during discovery and pull all files linked to Requests and KB articles. Files are re-associated with the correct Zendesk Ticket using the Zendesk Attachments API. Files exceeding Zendesk's 20 MB per-attachment limit are flagged for the customer's admin to handle separately.

SupportCenter Plus UDFs are stored as generic udf_char, udf_date, udf_picklist, udf_numeric, and udf_boolean columns in the database. We discover all active UDFs during the discovery scan, cross-reference the Field Labels admin table to resolve human-readable names, and create equivalent typed custom fields in Zendesk before data import begins. Picklist UDFs require value mapping because SupportCenter Plus picklist values and Zendesk custom field dropdown options rarely align exactly.