Migrate from IT Care Center to Freshdesk

Discovery and scoping

We audit the source IT Care Center environment across all active modules: Request Management (ticket volumes, status distribution, custom fields), Change Management (record count, change types, approval status), Problem Management (record count, linked incident references), Asset Management (CI types, custom field inventory), Knowledge Management (article count, folder hierarchy, published vs draft status), and user/agent accounts. We pair this with a Freshdesk plan assessment based on the migration scope: Sprout for basic ticket migration only, Blossom for API access, Growth+ for Asset Management and Custom Objects, or Pro/Enterprise for advanced automation and SLA tiers. The discovery output is a written migration scope and plan recommendation.

Schema design and Freshdesk plan provisioning

We design the destination Freshdesk schema based on the scoping output. This includes creating custom ticket fields to carry Change and Problem metadata (change type, risk level, approval status, problem root-cause text), configuring Freshdesk groups to match IT Care Center team structures, setting up the Knowledge Base category and folder hierarchy to mirror the source article taxonomy, and defining the tag vocabulary to preserve ticket and article classification. If the destination plan does not include Asset Management, we decide with the customer whether to use Freshdesk's custom object API or a text-based workaround before migration begins.

Data extraction and transformation

We extract data from IT Care Center using the method available to the customer (manual export, CSV download, or API if any undocumented endpoint exists). Each record type is then transformed: multi-channel conversation entries are consolidated per ticket; Change and Problem records are converted to tagged ticket variants; Asset records are prepared with field-level type mapping; Knowledge Articles are restructured to fit Freshdesk's folder-category hierarchy; tags are normalised for deduplication. We generate a source-destination field mapping document for the customer's review before any data is loaded.

Freshdesk trial or sandbox validation

We run a test migration into the customer's Freshdesk trial environment (14-day full-feature trial available on signup) or a fresh Blossom/Growth account to validate the mapping before production. The customer spot-checks migrated tickets, assets, and knowledge articles against the IT Care Center source, verifies that Change and Problem records carry the expected tagged metadata, and confirms that the knowledge base folder structure is correct. Mapping corrections identified during validation are applied to the production migration configuration before the cutover window.

Production migration in dependency order

We execute the production migration in dependency order: Agents and Groups (required for assignment), Contacts (from end users), Assets (if destination plan supports them), Tickets (with conversation threads consolidated and Change/Problem tags applied), Knowledge Articles (with folder hierarchy resolved), and Projects (as tagged tickets or custom objects). Each phase emits a row-count reconciliation report. Tags and custom fields are loaded in the same pass as their parent records. Any IT Care Center data that cannot be automatically migrated (automations, approval workflows, service catalogue links) is logged to the written inventory documents delivered at handoff.

Cutover, validation, and automation handoff

We freeze writes to IT Care Center during the cutover window, run a final delta migration of any records modified during the migration window, and confirm that all record counts match the source audit. We deliver the Change and Problem inventory document, the automation rule inventory, and the knowledge base service-link gap report. We support a one-week hypercare window where we resolve any data integrity issues raised by the customer's IT team. We do not rebuild Change Management approval workflows or Problem Management linkages in Freshdesk as part of the migration scope; those are rebuilt by the customer's admin using Freshdesk Rule Builder from the written inventories we provide.