How long does a SYDLE ONE to Freshdesk migration take?

Most migrations land between three and five weeks for accounts under 10,000 tickets and 5,000 contacts with no active SYBOX modules beyond the standard Service Desk. Migrations with active SYBOX HR Recruitment, Agile PM, or Service Portal modules, large document libraries (over 50,000 files), or multi-level ticket status hierarchies move to seven to twelve weeks because of the dependency-ordered extraction sequencing, custom status mapping work, and SYBOX module verification during scoping. The extraction phase is the longest part due to SYDLE ONE's lack of a public REST API.

Do SYDLE ONE BPM workflows and Service Portal routing rules migrate to Freshdesk?

No. BPM workflow definitions (BPMN process models, forms, and execution history stored in SYDLE ONE's process engine) and Service Portal page configurations and routing rules are not migrated as functional code. Freshdesk's Scenario Automations and Portal configuration use a different data model and cannot receive a direct import from SYDLE ONE's export format. We deliver a written inventory of every active BPM workflow, Service Portal page, and routing rule with a recommended Freshdesk equivalent so the customer's admin can rebuild them manually post-migration. SYBOX automations (Chatbot flows, Billing triggers) similarly require manual rebuild in Freshdesk's automation framework.

What does a SYDLE ONE to Freshdesk migration typically cost?

Migrations under 10,000 tickets, 5,000 contacts, and no SYBOX modules land between $3,500 and $5,500. Migrations with active SYBOX modules, large document volumes, or complex custom status hierarchies move to $7,000-$11,000. These ranges assume a single Freshdesk destination instance and standard data volumes. Freshdesk subscription cost (starting at $15/agent/month on Growth, $49 on Pro, $79 on Enterprise) is separate from the migration fee and is the customer's recurring cost.

Can we migrate SYDLE ONE Documents and Attachments to Freshdesk?

Yes, but with plan-level constraints. Freshdesk Sprout (free plan) does not support API-based attachment migration, so the destination account must be on Blossom or above. SYDLE ONE ECM Documents migrate as Freshdesk Ticket Attachments linked to their parent ticket via the cross-reference mapping table built during extraction. Standalone documents (not attached to a ticket) migrate as Freshdesk Attachments with a reference listing. We preserve document metadata (filename, upload date, uploader) as custom fields on the attachment record.

How do you handle SYDLE ONE ticket statuses that differ from Freshdesk's fixed vocabulary?

Freshdesk uses a fixed status vocabulary (Open, Pending, Resolved, Closed) by default, but Estate and above allow custom statuses. During scoping we query SYDLE ONE's live ticket status configuration to build an explicit mapping table. For example, a SYDLE ONE status 'Em Análise' might map to a Freshdesk custom status 'Under Review' that we create before migration. Statuses with no clear Freshdesk equivalent are flagged in the scoping report for the customer to decide whether to map to an existing status, create a new custom status, or consolidate similar statuses. Priority and source fields migrate directly as they use consistent value sets across both platforms.

Do we lose data migrating out of SYDLE ONE if we are on a lower-tier plan?

Possibly. SYBOX modules including HR Recruitment, Agile Project Management, Service Portal, Chatbot, Billing, and E-commerce are gated by pricing tier. During scoping we verify which SYBOX modules are active in the source instance. If the customer has downgraded tiers before migration, some modules may be inaccessible. We flag any inaccessible modules in the scoping report before beginning extraction. Standard CRM contacts, accounts, and Service Desk tickets remain accessible regardless of tier.

What happens to our SYDLE ONE data after the migration?

We recommend the customer freeze writes on SYDLE ONE at cutover and retains the instance for a minimum of 30 days post-migration as a fallback while the Freshdesk instance is validated. SYDLE ONE data remains in the customer's control on their SYDLE ONE instance until they decide to cancel the subscription. We do not take custody of SYDLE ONE data long-term; all extraction is performed in a single migration window and the data is transformed and loaded directly into Freshdesk. After cutover validation, the customer controls the SYDLE ONE decommission timeline.

Can FlitStack AI migrate from Freshdesk back to SYDLE ONE?

Yes. We support bidirectional migrations. Moving from Freshdesk to SYDLE ONE reverses the object mapping: Freshdesk Tickets become SYDLE ONE Service Desk tickets, Contacts and Companies map to SYDLE ONE CRM objects, and Freshdesk Custom Objects map to SYDLE ONE custom objects. The Freshdesk API is well-documented and supports bulk export via the v2 endpoints, which makes the Freshdesk-to-SYDLE ONE extraction more API-driven than the reverse direction. Contact us for a scoped quote on the reverse migration.

SYDLE ONE to Freshdesk Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Moving from SYDLE ONE to Freshdesk shifts from an integrated BPM-ECM-CRM-Service Desk suite to a dedicated help desk platform with a documented REST API. SYDLE ONE has no public REST API for bulk read/write operations — all migration work runs through JSON/XML import-export — while Freshdesk enforces per-minute API rate limits (200 calls/min on Growth, 400 on Pro, 700 on Enterprise) with per-endpoint sub-limits. We bridge this gap by extracting SYDLE ONE data in JSON batches, transforming in our staging layer, and loading into Freshdesk through the REST API with exponential backoff and batch chunking. SYDLE ONE's cross-module relationships (Documents tied to Processes, Tickets linked to Contacts) require an ordered export sequence to prevent orphaned records. Ticket statuses, custom fields, and parent-child ticket configurations require explicit mapping tables that we build during scoping. We do not migrate BPM workflow definitions, SYBOX automations, or Service Portal routing rules as code — these require manual rebuild in Freshdesk using its automation rules and scenario automations.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

SYDLE ONE

What's pushing teams away

Cross-module data integration is incomplete — raw data consolidates in a central location but analyzing or reporting on it requires external BI tools rather than native SYDLE ONE analytics.
The platform's wide range of tools can feel overwhelming at first, creating a steep onboarding curve for teams expecting a simpler CRM-only experience.
Pricing is tiered with minimum user counts starting at 20 for Rocket and escalating to 100 for Star, making cost unpredictable for organizations with fluctuating headcounts.

Choosing

Freshdesk

What's pulling them in

Free tier for 1-2 agents with no credit card makes initial evaluation risk-free and appeals to startups and small support teams.
Per-agent pricing is predictable and scales cleanly as teams grow from Growth at $15/agent/month to Enterprise at $89/agent/month.
Freddy AI Copilot and Email AI Agent bring AI assistance without forcing a full platform switch, appealing to teams already embedded in Freshdesk.
Multilingual help desk and customer portal features serve global SMB teams without requiring enterprise-level investment.
Collaborators up to 5,000 included in paid plans allow non-agent stakeholders to view tickets without additional licensing cost.

Object mapping

How SYDLE ONE objects map to Freshdesk

Each row shows how a SYDLE ONE object lands in Freshdesk, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

SYDLE ONE

Ticket

maps to

Freshdesk

Ticket

1:1

Fully supported

SYDLE ONE Service Desk tickets map to Freshdesk Tickets. The primary challenge is status mapping: SYDLE ONE tickets use instance-specific statuses defined by the administrator, while Freshdesk uses a fixed vocabulary (Open, Pending, Resolved, Closed) with custom status builder available on Estate and above. We build an explicit status-mapping table during scoping by querying the live SYDLE ONE status values and creating corresponding Freshdesk custom statuses. Priority, source (email, chat, phone), and custom fields migrate with type-matched Freshdesk field definitions.

SYDLE ONE

Contact

maps to

Freshdesk

Contact

1:1

Fully supported

SYDLE ONE CRM Contacts migrate to Freshdesk Contacts. Standard fields (name, email, phone, job title) map directly. Custom contact properties migrate to Freshdesk custom contact fields, which are available from Blossom tier onward. Any tag or label applied to the Contact in SYDLE ONE migrates as Freshdesk tags. We resolve the contact's associated Company to the Freshdesk Company lookup during import.

SYDLE ONE

Account

maps to

Freshdesk

Company

1:1

Fully supported

SYDLE ONE Account/Company records map to Freshdesk Companies. Company name becomes the Company name field; website, industry, and size migrate to corresponding Freshdesk Company fields. The Account-Contact relationship is preserved by resolving the Freshdesk Contact ID at the time of Contact import and writing the association back.

SYDLE ONE

Document

maps to

Freshdesk

Attachment

1:1

Fully supported

SYDLE ONE ECM Documents migrate as Freshdesk Ticket Attachments linked to the corresponding Ticket. Documents without a parent Ticket (standalone files in the ECM repository) migrate as standalone Freshdesk Attachments with a reference table linking the original SYDLE ONE document ID to the destination Freshdesk attachment ID. Note that API-based attachment migration is not available on Freshdesk Sprout plan; this requires Blossom or above.

SYDLE ONE

Tag / Label

maps to

Freshdesk

Tag

1:1

Fully supported

Tags applied to Contacts, Accounts, Tickets, and Documents in SYDLE ONE migrate as Freshdesk Tags. We normalize tag names that contain special characters or spaces before importing to avoid Freshdesk validation errors. Tags are scoped per object type in Freshdesk and migrate with the object so that the tag context is preserved.

SYDLE ONE

Custom Object

maps to

Freshdesk

Custom Object

1:1

Fully supported

SYDLE ONE custom objects migrate to Freshdesk Custom Objects (available from Blossom onward). We read the live SYDLE ONE instance schema during scoping to identify all custom object names and field definitions, then pre-create the corresponding Freshdesk Custom Objects including attributes, data types, and lookup relationships to native objects (Contact, Company, Ticket) before importing data. Any custom object without a clear Freshdesk equivalent is flagged in the pre-migration report for the customer to decide whether to migrate as a Custom Object or as custom fields on a native object.

SYDLE ONE

SYBOX Service Portal

maps to

Freshdesk

Portal Configuration

1:1

Fully supported

SYDLE ONE Service Portal records and portal page configurations export as JSON structures referencing ticket and contact IDs. Because portal routing rules, page layouts, and menu structures reference SYDLE ONE internal IDs, these do not migrate as functional portal configurations in Freshdesk. We deliver a written inventory of every active Service Portal page, routing rule, and form, with a recommended Freshdesk Portal equivalent (Freshdesk's own Customer Portal built into all tiers), so the customer's admin can rebuild the portal manually post-migration.

SYDLE ONE

SYBOX HR Recruitment

maps to

Freshdesk

Candidate (via Freshdesk Custom Object)

lossy

Mapping required

SYBOX HR Recruitment (available on Planet and Star tiers) stores Candidate records, job openings, and application statuses. Because Freshdesk is a help desk platform rather than an ATS, candidate records migrate as a Freshdesk Custom Object with fields mapped to the source candidate schema. Job openings and application status history migrate as related custom object records with lookup relationships. HR-specific fields (department, hiring manager, interview score) map to custom fields on the Candidate custom object. This module is gated by SYDLE ONE license tier, which we verify during scoping.

SYDLE ONE	Freshdesk	Compatibility
Ticket	Ticket1:1	Fully supported
Contact	Contact1:1	Fully supported
Account	Company1:1	Fully supported
Document	Attachment1:1	Fully supported
Tag / Label	Tag1:1	Fully supported
Custom Object	Custom Object1:1	Fully supported
SYBOX Service Portal	Portal Configuration1:1	Fully supported
SYBOX HR Recruitment	Candidate (via Freshdesk Custom Object)lossy	Mapping required

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

SYDLE ONE gotchas

High

No public REST API for programmatic migration

High

Tier-gated SYBOX modules require license verification

Medium

Cross-module data relationships break silently during manual export

Medium

Custom field schema varies per implementation

Freshdesk gotchas

High

API access is blocked on the free plan

High

Per-minute rate limits are account-wide and endpoint-specific

Medium

Multi-channel source types do not map 1:1 to all destinations

Medium

Custom objects created in-product cannot be accessed by other apps

Low

Contact import requires at least 10 existing tickets in the account

SYDLE ONE gotchas		Freshdesk gotchas
Severity	Issue	Severity	Issue
High	No public REST API for programmatic migration	High	API access is blocked on the free plan
High	Tier-gated SYBOX modules require license verification	High	Per-minute rate limits are account-wide and endpoint-specific
Medium	Cross-module data relationships break silently during manual export	Medium	Multi-channel source types do not map 1:1 to all destinations
Medium	Custom field schema varies per implementation	Medium	Custom objects created in-product cannot be accessed by other apps
		Low	Contact import requires at least 10 existing tickets in the account

Pair-specific challenges

SYDLE ONE has no public REST API for bulk extraction

SYDLE ONE does not publish a documented REST API for bulk read/write operations. All migration extraction runs through the platform's JSON/XML/Excel export mechanism. This is a structural constraint that affects the entire migration: throughput is lower than API-driven platforms, extraction must be performed in a strict dependency-ordered sequence to preserve referential integrity (Contacts and Accounts first, then Tickets, then Documents), and there is no programmatic way to query or paginate large exports beyond what the platform's UI export tool supports. We design our extraction pipelines around these constraints and inform the customer during scoping that the extraction phase may take longer than comparable migrations from API-first platforms.
Freshdesk API attachment support requires paid plan

Freshdesk Sprout (free plan) does not support API-based attachment migration. If the customer is on Sprout, all file attachments must be migrated manually or the customer must upgrade to Blossom or above before the migration runs. We confirm the destination Freshdesk plan during scoping and flag this constraint immediately. If the customer cannot upgrade, we document which attachments cannot be migrated via API and provide a file listing so the customer can manually re-upload the critical ones post-migration.
Parent-child ticket configuration can block Freshdesk import

Freshdesk Estate and Forest plans support Parent-Child ticketing where sub-tickets of type Task require a Parent-Child relation field. If any incoming SYDLE ONE ticket of type Task lacks parent-child metadata, the Freshdesk import will fail for that record. We recommend disabling Parent-Child ticketing in Freshdesk before migration begins. If the customer requires parent-child structure post-migration, we build the parent-child relationship as a post-import step using Freshdesk's ticket association API after all tickets are loaded.
Custom field naming diverges from UI labels in Freshdesk API

Freshdesk custom fields have a different API name from their display label. For example, a field titled 'Contract End Date' in the UI might have an API name like 'cf_contract_end_date'. We read the Freshdesk field definitions via the API before building field maps to ensure all custom field references in the migration use the API name. Any unmapped custom fields from SYDLE ONE are flagged in the pre-migration report for the customer to confirm whether they map to an existing Freshdesk field, a new custom field to be created, or a field to be dropped.

Migration approach

Six steps for a successful SYDLE ONE to Freshdesk data migration

Discovery and scoping

We audit the SYDLE ONE instance across active modules, custom object schemas, ticket status configurations, document volumes, and any active SYBOX licenses. We confirm the destination Freshdesk plan (Sprout through Enterprise) and verify which SYDLE ONE SYBOX modules are accessible given the current license tier. The discovery output is a written migration scope document listing all object types to migrate, the status-mapping table, custom field inventory, and a flag for any inaccessible SYBOX data. This phase also confirms the extraction method (JSON batch export) and the expected throughput constraints from SYDLE ONE's non-API export mechanism.
Destination schema setup

We create custom objects, custom fields, and custom ticket statuses in Freshdesk before any data import begins. Custom ticket statuses are built to match the SYDLE ONE status vocabulary mapped during discovery. Custom fields are created with the correct data types (text, number, date, dropdown, multi-select) and linked to the relevant object. We deploy these into a Freshdesk sandbox environment first for validation if available. This phase also confirms that the destination plan supports the required features (API attachments, custom objects, parent-child ticketing) and escalates any plan-level constraint to the customer before proceeding.
Dependency-ordered extraction from SYDLE ONE

We extract SYDLE ONE data in a strict dependency sequence to preserve referential integrity: Contacts and Accounts first, then Tickets with contact and account lookups resolved, then Documents and Attachments linked to their parent records. Each extraction batch writes a cross-reference mapping table alongside the data so that during the Freshdesk import we can resolve parent-record IDs and write the correct WhoId and WhatId on each ticket. This ordered extraction compensates for SYDLE ONE's lack of a programmatic API by ensuring that no record references an ID that has not yet been created in Freshdesk.
API-rate-limited import into Freshdesk

We import data into Freshdesk via the v2 REST API with per-minute rate limit handling and exponential backoff. Import order follows the same dependency sequence as extraction: Companies, then Contacts, then Tickets, then Attachments, then Custom Objects. We chunk large batches to stay within Freshdesk's per-endpoint sub-limits (for example, 80 ticket creates per minute on Growth, 160 on Pro) and pause between chunks to respect the account-level rate limit. Any record that fails import (due to validation rules, missing required fields, or duplicate detection) is written to a retry queue and re-attempted up to three times before being flagged in the reconciliation report.
Validation and reconciliation

We produce a row-count reconciliation report comparing source record counts against destination record counts for each object type. We spot-check 25-50 random records across Tickets, Contacts, and Companies to verify field-level accuracy, status mapping correctness, and attachment presence. Any records that failed import or were skipped due to unmapped fields appear in a separate exceptions report. The customer reviews the report and approves the migration result before we proceed to cutover. Parent-child ticket relationships are validated as a post-import step if the customer requires that structure in Freshdesk.
Cutover and workflow inventory delivery

We freeze writes on the SYDLE ONE instance during cutover, run a final delta extraction for any records modified during the migration window, and import the delta into Freshdesk. Freshdesk becomes the system of record at cutover. We deliver a written inventory of every active SYDLE ONE Service Portal page, BPM workflow definition, SYBOX automation, and routing rule with a recommended Freshdesk equivalent (Scenario Automations, Freshdesk Portal configuration, or manual rebuild guidance). We do not rebuild these as code. We support a five-business-day post-cutover window to resolve reconciliation issues raised by the customer's support team.

Platform deep dives

Context on both ends of the pair

SYDLE ONE

Source

Strengths

Visual BPMN editor enables non-developers to model, deploy, and iterate on business processes without code.
Pre-built SYBOX solutions for HR Recruitment, Agile PM, and Service Portal reduce time-to-value for common use cases.
Native ECM module keeps Documents and Content alongside CRM and Process data in one repository.
Supports JSON, XML, and Excel import formats for flexible bulk data loading from external systems.
Offers private cloud and on-premise deployment options on Star tier for organizations with data residency requirements.

Weaknesses

No publicly documented REST API — bulk data operations rely on JSON/XML import-export rather than programmatic API calls.
Integration between built-in modules is a documented weak point; data consolidates centrally but cross-module reporting often requires external BI tools.
Pricing tiers enforce minimum user counts of 20 to 100, creating cost inflexibility for smaller or growing organizations.
No official rate limit or API quota documentation publicly available, making migration throughput planning difficult.
Analytics and reporting are limited compared to dedicated BI platforms, leading some customers to maintain separate reporting stacks.

Freshdesk

Destination

Strengths

Generous free tier with no credit card required for 1-2 agents for 6 months.
Per-agent pricing model is transparent and scales linearly with team growth.
Freddy AI Copilot integrates assistance directly into the agent workspace without requiring separate tooling.
Multilingual help desk and customer portal serve global teams on Pro and Enterprise plans.
Shared inbox, threads, and tasks keep ticket context unified across multi-channel conversations.

Weaknesses

Freddy AI is a separate paid add-on charged per session, making AI costs unpredictable and hard to budget.
Performance issues including delayed loading and duplicate tickets are recurring user complaints during high-volume periods.
Customization is more limited than Zendesk, with fewer workflow options and reporting flexibility.
Add-ons for chat, advanced routing, and custom reporting are gated behind higher tiers or separate module purchases.
API access is completely disabled on the free plan, blocking any programmatic data export or migration tooling.

	SYDLE ONE Source	Freshdesk Destination
Strengths	Visual BPMN editor enables non-developers to model, deploy, and iterate on business processes without code. Pre-built SYBOX solutions for HR Recruitment, Agile PM, and Service Portal reduce time-to-value for common use cases. Native ECM module keeps Documents and Content alongside CRM and Process data in one repository. Supports JSON, XML, and Excel import formats for flexible bulk data loading from external systems. Offers private cloud and on-premise deployment options on Star tier for organizations with data residency requirements.	Generous free tier with no credit card required for 1-2 agents for 6 months. Per-agent pricing model is transparent and scales linearly with team growth. Freddy AI Copilot integrates assistance directly into the agent workspace without requiring separate tooling. Multilingual help desk and customer portal serve global teams on Pro and Enterprise plans. Shared inbox, threads, and tasks keep ticket context unified across multi-channel conversations.
Weaknesses	No publicly documented REST API — bulk data operations rely on JSON/XML import-export rather than programmatic API calls. Integration between built-in modules is a documented weak point; data consolidates centrally but cross-module reporting often requires external BI tools. Pricing tiers enforce minimum user counts of 20 to 100, creating cost inflexibility for smaller or growing organizations. No official rate limit or API quota documentation publicly available, making migration throughput planning difficult. Analytics and reporting are limited compared to dedicated BI platforms, leading some customers to maintain separate reporting stacks.	Freddy AI is a separate paid add-on charged per session, making AI costs unpredictable and hard to budget. Performance issues including delayed loading and duplicate tickets are recurring user complaints during high-volume periods. Customization is more limited than Zendesk, with fewer workflow options and reporting flexibility. Add-ons for chat, advanced routing, and custom reporting are gated behind higher tiers or separate module purchases. API access is completely disabled on the free plan, blocking any programmatic data export or migration tooling.

Complexity grading

How hard is this migration?

Standard Helpdesk migration. All 7 core objects map 1:1 between SYDLE ONE and Freshdesk.

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across SYDLE ONE and Freshdesk.

Object compatibility
A
All 7 core objects map 1:1 between SYDLE ONE and Freshdesk.
Field mapping clarity
C
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
B
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
B
SYDLE ONE: Not publicly documented.
Data volume sensitivity
A
SYDLE ONE exposes a bulk API — large-volume migrations stream efficiently.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from SYDLE ONE to Freshdesk

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

SYDLE ONE

Freshdesk

How SYDLE ONE objects map to Freshdesk

What specifically takes care here

Six steps for a successful SYDLE ONE to Freshdesk data migration

Context on both ends of the pair

How hard is this migration?

Estimate your SYDLE ONE to Freshdesk migration cost

What are you migrating?

Frequently asked questions about SYDLE ONE to Freshdesk data migrations

Can't find your answer?

Related migrations to explore

Move from SYDLE ONE.
Land in Freshdesk, intact.

Migrate from SYDLE ONE to Freshdesk

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

SYDLE ONE

Freshdesk

How SYDLE ONE objects map to Freshdesk

What specifically takes care here

Six steps for a successful SYDLE ONE to Freshdesk data migration

Context on both ends of the pair

How hard is this migration?

Estimate your SYDLE ONE to Freshdesk migration cost

Frequently asked questions about SYDLE ONE to Freshdesk data migrations

Can't find your answer?

How long does a SYDLE ONE to Freshdesk migration take?

Do SYDLE ONE BPM workflows and Service Portal routing rules migrate to Freshdesk?

What does a SYDLE ONE to Freshdesk migration typically cost?

Can we migrate SYDLE ONE Documents and Attachments to Freshdesk?

How do you handle SYDLE ONE ticket statuses that differ from Freshdesk's fixed vocabulary?

Do we lose data migrating out of SYDLE ONE if we are on a lower-tier plan?

What happens to our SYDLE ONE data after the migration?

Can FlitStack AI migrate from Freshdesk back to SYDLE ONE?

Related migrations to explore

Move from SYDLE ONE. Land in Freshdesk, intact.

Move from SYDLE ONE.
Land in Freshdesk, intact.