Migrate from ManageEngine SupportCenter Plus to Freshdesk

Discovery and database access setup

We audit the SupportCenter Plus instance: database version (PostgreSQL or MS SQL), schema version, active UDF columns, portal count, and record volumes for Requests, Accounts, Contacts, Products, KB articles, and attachments. We also retrieve the Field Labels admin table to resolve generic udf_* column names to human-readable names. The customer provides a read-only database user with access to the SupportCenter Plus schema. We simultaneously audit the Freshdesk destination: plan tier (confirming API rate limits), existing custom fields, groups, and SLA configuration.

Database extraction and transform

We run direct SQL queries against the SupportCenter Plus database to extract all records in dependency order: Accounts first (parent to Contacts), then Contacts, then Requests with their request-type and category assignments. Comments are extracted from the junction table and associated with the migrated request ID. Attachments are located from the disk store path (or blob storage if database-embedded) and batched for Freshdesk upload. Products and KB articles extract in parallel. We cross-reference every record against the Field Labels table to produce human-readable field names in the migration dataset.

Freshdesk custom field and schema provisioning

Before any data loads, we create all Freshdesk custom fields (for migrated UDFs), groups, and SLA policies via the Freshdesk API. Portal-specific SLA rules from SupportCenter Plus are consolidated into a single global SLA policy set in Freshdesk; we document which portal's rules took precedence for the customer's review. Custom ticket types and statuses are configured to match the SupportCenter Plus request lifecycle as closely as possible, flagging any states that cannot map 1:1.

Sandbox migration and reconciliation

We load all extracted records into the Freshdesk sandbox environment in dependency order: Companies (from Accounts), then Contacts, then Products, then Tickets (from Requests), then Conversations, then Attachments, then KB articles. Each phase emits a row-count reconciliation report. The customer's support operations lead spot-checks 25-50 records against the source and signs off before production migration begins. Any field-mapping corrections, SLA consolidation decisions, and channel normalization rules are confirmed here.

Production migration with rate-limit pacing

We run production migration in record-dependency order using Freshdesk API v2 with per-plan rate-limit pacing. Accounts load first, followed by Contacts (with company_id resolved), Products, and Tickets. Conversations load as a second pass using the dedicated conversations endpoint to avoid the ten-conversation ceiling. Attachments upload via the Freshdesk Attachments API and associate to the correct conversation ID. KB articles load last, with section assignments mapped from the SupportCenter Plus category hierarchy. We pause at each phase to emit a reconciliation report before proceeding.

Cutover, delta sync, and handoff

We freeze SupportCenter Plus writes during cutover, run a final delta migration of any records created or modified since the migration start timestamp, then enable Freshdesk as the system of record. We deliver a written inventory of SupportCenter Plus workflows, automations, SLA rules, and KB category structures that require rebuild in Freshdesk, with recommended Freshdesk equivalents (automation rules, SLA policies, Freshdesk Solution categories). We support a five-business-day hypercare window for reconciliation issues. We do not rebuild automations or SLA rules as Freshdesk configuration inside the migration scope; that is a separate engagement or an internal admin task.