Migrate from SAAS First to Freshdesk

SAAS First ticket records map to Freshdesk Case objects. The ticket subject becomes Case subject, ticket description maps to Case description, ticket status (open, pending, resolved, closed) maps to Freshdesk status values (open, pending, resolved, closed). Channel metadata (email, chat, WhatsApp, SMS, social) from SAAS First's unified inbox field populates the Freshdesk type or source field. Custom fields on SAAS First tickets migrate as Freshdesk custom fields if the destination plan supports them; if not, we flag them for manual reconstruction post-migration.

SAAS First conversation threads attached to tickets migrate as Freshdesk Conversation records linked to the corresponding Case. Each message in the thread (customer message, agent reply, private note) maps to the Freshdesk conversation body_text with the author_type field set to user (customer) or agent. Inbound and outbound direction preserves based on SAAS First sender metadata. Inline images within conversation threads migrate as attachments on the Conversation record.

SAAS First contact profiles migrate to Freshdesk Contact records. The contact name, email, phone, company name, and any custom properties map to Freshdesk Contact fields. SAAS First CRM-linked contact data (lifecycle stage, deal associations) migrates as custom fields on the Freshdesk Contact unless equivalent Freshdesk properties exist. Duplicate detection runs on email match during import to avoid creating duplicate Contact records.

SAAS First agent profiles (name, email, role, group assignment) migrate to Freshdesk Agent records. Agent groups in SAAS First map to Freshdesk Groups with agents assigned by email match. Any agent permission levels (admin, manager, agent) translate to Freshdesk roles where available; granular permission differences are noted in the migration inventory for admin review post-migration.

SAAS First agent groups migrate to Freshdesk Groups. Group names and member lists transfer directly. If SAAS First uses group-based routing rules, we document each routing rule in the automation inventory for the customer to rebuild in Freshdesk's workflow configuration, since routing rules do not migrate as code.

SAAS First ticket tags migrate to Freshdesk Tags. Tags on tickets are preserved as Freshdesk tag strings on the Case record. If SAAS First uses tags for content classification or filtering, the tag strategy transfers with the same labels to maintain consistency in Freshdesk's tag-based filtering and reporting.

File attachments on SAAS First tickets (images, PDFs, documents) migrate as Freshdesk Attachments linked to the corresponding Conversation or Case record. We download each file from SAAS First and upload to Freshdesk via the attachments API endpoint, preserving original filenames and MIME types. Large file batches use chunked upload handling with retry on failure.

SAAS First custom objects migrate to Freshdesk Custom Objects only if the destination Freshdesk plan is Forest or Enterprise (Custom Objects are not available on Sprout, Blossom, or Garden). We pre-create the destination schema including all custom fields and lookup relationships before data import. Custom object records that reference Tickets or Contacts migrate with lookup resolution against the newly created Case and Contact IDs. If the destination plan does not support Custom Objects, we flag each custom object for a separate migration plan post Freshdesk upgrade.