Migrate from ManageEngine SupportCenter Plus to Salesforce Service Cloud

SupportCenter Plus Requests map to Salesforce Case. The Request.ID becomes Case.CaseNumber preserved via a custom field (original_request_id__c) for cross-reference. Request status (Open, Pending, On Hold, Resolved, Closed) maps to Salesforce Case Status values that we configure in the destination org. Request priority maps to Case Priority. The Request.requester_id links to the migrated Contact, and the Account link resolves via Contact.AccountId at migration time.

SupportCenter Plus Accounts map directly to Salesforce Account. The Account name becomes Account.Name, and Account.site maps to Account.BillingAddress if applicable. Multi-portal architecture means one Account can appear in multiple portals with different SLA configurations; we consolidate these into a single Account record with entitlement rules applied based on the primary portal's SLA template, discussing with the customer which portal's terms take precedence.

SupportCenter Plus Contacts map to Salesforce Contact. Each Contact's AccountId is resolved at migration time by matching the Contact's parent Account in SupportCenter Plus to the migrated Salesforce Account. Email is the dedupe key. SupportCenter Plus allows contacts without accounts; these migrate as Contacts without an AccountId, which Salesforce permits but flags for admin cleanup.

SupportCenter Plus Contracts map to Salesforce Contract. Contract.AccountId resolves to the migrated Salesforce Account. Contract start and end dates map to Contract.StartDate and Contract.EndDate. Contract status (Draft, In Progress, Activated, Expired) maps to Salesforce Contract.Status. If the destination Salesforce edition lacks Contracts, we map to a custom Contract__c object during scoping.

SupportCenter Plus Product Catalog entries map to Salesforce Product2. Product.name becomes Product2.Name, and the product description maps to Product2.Description. We also create Standard Pricebook entries during import so that Products are available for Case Entitlements and Opportunity Products in the same org.

SupportCenter Plus SLA templates define response and resolution times per portal per Account tier. These do not migrate as code. We deliver a written inventory of every SLA template with its triggers, business hours, response times, and escalation rules, mapped to Salesforce Entitlement Processes and Business Hours. The customer's admin rebuilds these in Salesforce Setup under Entitlements.

SupportCenter Plus request templates (subject, category, default fields, pre-populated values) are portal-scoped configurations. We document each template's field structure, default values, and category assignments. These are rebuilt as Salesforce Flow with Screen Flow variants or as Quick Actions on Case, depending on whether the template requires guided agent input or automated case creation.

SupportCenter Plus KB articles map to Salesforce Knowledge with article type matching. Category-to-article associations map to DataCategoryGroup assignments in Salesforce Knowledge. Product-linked articles (where a SupportCenter Plus KB article is tied to a Product) map to Article-Product junction records via a custom field on the Knowledge article. Public/internal article visibility maps to Salesforce PublishStatus.

SupportCenter Plus Comments are conversation-thread entries on a Request. Each comment migrates as a Salesforce EmailMessage record linked to the Case. Comment.author resolves to the migrated Contact or User; internal-only comments in SupportCenter Plus map to EmailMessage.headers with a custom flag internal_note__c so that the customer's admin can apply visibility restrictions post-migration.

SupportCenter Plus attachments are stored either on disk (by file path) or in the database (base64-encoded). We locate the attachment store path during discovery and pull files in parallel batches, re-associating each with the migrated Case via Salesforce ContentVersion (file upload) and ContentDocumentLink (record attachment). Files over 25 MB chunk at Salesforce's ContentDocument size limit.

SupportCenter Plus support reps and admins map to Salesforce User records. We match by email address against the destination Salesforce org. Any SupportCenter Plus User without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role-based portal assignments from SupportCenter Plus are documented for RBAC rebuild.

SupportCenter Plus UDF columns use generic naming (udf_char1, udf_date2, udf_picklist3) in the database. We cross-reference the Field Labels admin table during discovery to resolve human-readable names, then create typed Salesforce custom fields (Text, Date, Picklist, Checkbox, Number) before migration. Picklist UDFs require value-set mapping against the SupportCenter Plus picklist options.