--- title: "Freshdesk Omni Forced Upgrade (2026): What Breaks & How to Migrate" slug: freshdesk-omni-forced-upgrade-2026-what-breaks-how-to-migrate date: 2026-07-10 author: Raaj categories: [Freshdesk] excerpt: "Freshworks is force-upgrading all Freshdesk accounts to the new platform. Here's what breaks — SLA math, phone fields, Freshchat data — and how to migrate." tldr: "The mandatory Freshdesk Omni upgrade changes SLA calculations, enforces strict phone validation that breaks integrations, and leaves Freshchat customers with no automatic migration path — audit your data now." canonical: https://clonepartner.com/blog/freshdesk-omni-forced-upgrade-2026-what-breaks-how-to-migrate/ --- # Freshdesk Omni Forced Upgrade (2026): What Breaks & How to Migrate # Freshdesk Omni Forced Upgrade (2026): What Breaks & How to Migrate Freshworks is force-upgrading every legacy Freshdesk account to the new platform and pushing customers toward Freshdesk Omni. There is no opt-out. If you're running standalone Freshdesk, classic Freshdesk Omnichannel, or Freshchat, your account is either already upgraded or will be within weeks. Freshworks frames this as a "no action needed" event with zero downtime. That does **not** mean zero migration work. The vendor's own documentation shows changed SLA behavior, routing logic, agent status handling, and strict new contact validation rules. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000011818-how-to-upgrade-to-the-new-freshdesk-or-freshdesk-omni-)) This upgrade changes SLA math, breaks phone-field integrations, can orphan Marketplace apps, and leaves Freshchat customers stranded on separate infrastructure with no automatic migration path. **Disclosure:** This blog is published by ClonePartner, a help desk migration services vendor. All technical claims are cited to Freshworks' own documentation. Our service-specific content is confined to a [clearly labeled section](#how-clonepartner-handles-the-freshdesk-omni-transition) near the end so you can evaluate the technical analysis independently. This article covers exactly what changes, what breaks, and what your options are — whether you plan to stay on Freshdesk Omni or leave entirely. ## The Three Waves of the 2026 Freshdesk Omni Upgrade Freshworks split this transition into three overlapping waves, each affecting a different customer segment with a different risk profile. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000011818-how-to-upgrade-to-the-new-freshdesk-or-freshdesk-omni-)) ### Wave 1: Standalone Freshdesk (December 2025 – April 2026) All standalone Freshdesk customers who signed up before December 1, 2025 are being automatically upgraded to the latest Freshdesk platform. This is mandatory. Freshworks says there is no downtime and no plan or price change for this step. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000011818-how-to-upgrade-to-the-new-freshdesk-or-freshdesk-omni-)) What actually changes: your account gets enhancements in SLA, Omniroute, and agent status modules. It also migrates your contact and company data model to the **Neo platform**. This is the wave that silently rewrites how your SLA timers calculate "days" and enforces strict phone number validation on every contact record. ### Wave 2: Classic Omnichannel → Freshdesk Omni (April – June 2026) Classic Freshdesk Omnichannel customers can upgrade through a self-serve flow rolling out between April and June 2026. Unlike Wave 1, this isn't fully automatic — you may need to reconfigure channels in the new Freshdesk Omni workspace and review and align settings with the new unified experience. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000011818-how-to-upgrade-to-the-new-freshdesk-or-freshdesk-omni-)) ### Wave 3: Freshdesk Omni 2025 (May 2026 Onward) Starting in May 2026, Freshworks began phased upgrades to the full Freshdesk Omni 2025 experience based on account complexity. This introduces the **Freshdesk Command Center** — a unified workspace where every interaction across email, chat, WhatsApp, Facebook, Instagram, and other channels is converted into a ticket. Agents work from one screen instead of switching between channel tabs. It also layers in **Freddy AI** capabilities (AI agents, AI Copilot, AI Insights) and a single admin workspace for all channels. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000012004-overview-of-freshdesk-omni-2025-upgrade)) The word *upgrade* hides three different realities: 1. **A mandatory platform upgrade** for old Freshdesk tenants. 2. **A configuration project** for classic Omnichannel customers. 3. **A net-new migration** for Freshchat customers. > [!TIP] > Two easy-to-miss details: Freshworks says Omni 2023 accounts will move to a Freshdesk-hosted domain, so verify anything that hard-codes account URLs or allowlists. And Freshdesk's Free Program is for **Freshdesk only** — it is **not available in Freshdesk Omni**. Do not assume there is a free Omni tier for staging or fallback. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000012004-overview-of-freshdesk-omni-2025-upgrade)) ## What Breaks: The Neo Platform Contact Data Model This is where the upgrade creates the most unexpected damage. Freshworks is introducing an upgraded contact and company experience powered by the Neo platform, designed to improve data consistency and streamline customer interactions. The intent is sound. The execution catches teams off guard. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000011077-freshdesk-upcoming-changes-2025)) ### Strict Phone Number Validation The new data model enforces hard validation on all phone fields (Work Phone and Mobile Phone): - **Only digits and `+` are allowed** - **No letters or special characters** (no parentheses, dashes, spaces, or dots) - **Length must be 6–30 characters** (digits only, excluding the `+`) Phone numbers can be blank, but if you fill them, they must validate. To create a contact, at least one identity field must be present: email, work phone, mobile phone, X handle, or unique external ID. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000011077-freshdesk-upcoming-changes-2025)) This sounds reasonable until you realize how many teams have been using phone fields as general-purpose text fields for years. Sales reps or legacy APIs injected extensions (e.g., "ext 123"), formatting characters, branch codes, or even addresses into these fields. That has three direct consequences: - If an integration writes `+1 (555) 123-4567 ext 9`, you need to strip formatting and move the extension somewhere else. - If someone used `work_phone` as a generic text bucket for addresses, branch codes, or notes, the new contract is no longer compatible. - If your integration creates placeholder contacts with just a name and nothing else, those creates now fail the stricter identity requirements. A fast pre-upgrade audit usually starts with something like this: ```sql -- Adjust for your source system before the upgrade SELECT id, work_phone, mobile_phone FROM contacts WHERE work_phone REGEXP '[^0-9+]' OR mobile_phone REGEXP '[^0-9+]' OR LENGTH(REPLACE(work_phone, '+', '')) NOT BETWEEN 6 AND 30 OR LENGTH(REPLACE(mobile_phone, '+', '')) NOT BETWEEN 6 AND 30; ``` > [!CAUTION] > **Integration Failure Risk:** Any custom app, CRM sync, or API integration that attempts to POST or PUT invalid data into a phone field will return an HTTP 400 Bad Request. If your Salesforce or HubSpot integration pushes unformatted phone numbers, the sync will fail. This includes Zapier zaps, Make scenarios, and custom middleware. ### What Happens to Existing Invalid Contacts Freshworks documents a staged enforcement model. During early rollout, invalid contacts are surfaced in a banner and filtered list. Once hard validation turns on, contacts with invalid phone numbers are moved to a separate **"Contacts that need action"** view. These records won't appear in the main contact list, can't be filtered, and are blocked from some search and merge actions until you fix them. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000011077-freshdesk-upcoming-changes-2025)) Those contacts become operationally degraded data — hidden from your main list, excluded from contact-related workflows, and effectively invisible until manually corrected. For teams with large contact databases, the scale of this problem can be significant: if even 5% of your contacts have non-compliant phone fields, a 100,000-record database means 5,000 contacts vanish from your active views overnight. If you've used phone fields to store other data (e.g., addresses), Freshworks suggests creating a new custom field or using one of the default fields to store and sync that data instead. ### Duplicate Dropdown Values Get Renamed Duplicate dropdown values in contact and company fields are automatically renamed with a `_copy` suffix to prevent database conflicts. If your downstream reporting, Zapier workflows, API scripts, or BI tools match on exact dropdown string values — and many do — this silent rename will break those syncs without warning. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000011077-freshdesk-upcoming-changes-2025)) You must audit your custom fields and consolidate duplicates before the forced upgrade hits your instance. ### Custom Phone Fields Frozen After the upgrade, you can no longer create new custom phone-type fields. Existing custom phone fields remain but are treated as string fields. If you had logic that relied on the "phone" field type for formatting or validation, that logic is now operating on a different field type. The "we'll just create another phone field" workaround is gone. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000011077-freshdesk-upcoming-changes-2025)) ### API Endpoints Stable — Payloads May Not Be One subtle point worth calling out: Freshworks says existing integrations continue to function and API endpoints remain unchanged after the Omni 2025 upgrade. Read that carefully. It means the transport layer is stable. It does **not** mean your payloads are still valid. If your integration keeps writing bad phone values, the URL stays the same while the workflow still fails. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000012004-overview-of-freshdesk-omni-2025-upgrade)) ### Marketplace App Compatibility Freshworks has not published a comprehensive compatibility list for the Freshdesk Marketplace after the Neo platform migration. This is a significant blind spot. If your workflow depends on Marketplace apps — particularly those that interact with contact or company records, custom fields, or SLA automation — you should: - **Inventory every installed Marketplace app** and note which ones read or write contact/company data - **Check each app's update history** on the Marketplace for Neo platform or Omni 2025 compatibility notes - **Contact the app vendor directly** for apps critical to your operations — especially apps that write to phone fields or depend on specific dropdown values - **Test in a sandbox** if possible before the forced upgrade hits your production instance Apps that use the Contacts or Companies API to write phone numbers in formatted strings (e.g., `(555) 123-4567`) will fail under the new validation rules even if the app itself hasn't changed. The failure is at the platform layer, not the app layer. ### Reporting and Analytics Continuity Freshworks' upgrade documentation does not explicitly address whether saved reports, custom dashboards, or scheduled report exports survive the Neo platform migration intact. This matters because: - **SLA-based reports will produce different numbers** post-upgrade due to the day-to-hour calculation change, even if the reports themselves are technically preserved. Any pre/post comparison of SLA compliance metrics is invalid unless you account for the definitional change. - **Reports filtered by dropdown values** that get the `_copy` suffix may return zero results or incomplete data sets. - **Scheduled exports** that run during the upgrade window may capture data in an inconsistent state. **Action required:** Before the upgrade, export snapshots of all critical dashboards and scheduled reports. After the upgrade, compare output row counts and key metrics against these baselines. Do not assume continuity. ## SLA and Routing Changes in the Command Center The SLA change is the one most likely to cause operational pain without anyone noticing until tickets start breaching. ### How SLA "Days" Calculation Is Changing Under the old model, when SLAs are configured in days, one business day equals the total working hours defined in your Business hours schedule (e.g., 8 or 9 hours). So if your team works 9 AM–5 PM, one business day = 8 hours. After the update, Freshdesk treats **1 day as 24 business hours**. SLA calculations use the configured Business hours until 24 hours are accumulated, which may span multiple working days. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000011682-freshdesk-upcoming-changes-december-2025-march-2026-)) Here's the practical impact with concrete numbers: | Business Hours Schedule | Old "1 Day" SLA | New "1 Day" SLA | Actual Working Days | |---|---|---|---| | 8 hours/day (9 AM–5 PM) | 8 hours | 24 business hours | 3 working days | | 9 hours/day (8 AM–5 PM) | 9 hours | 24 business hours | 2.67 working days | | 10 hours/day (8 AM–6 PM) | 10 hours | 24 business hours | 2.4 working days | | 12 hours/day (7 AM–7 PM) | 12 hours | 24 business hours | 2 working days | | 24/7 support | 24 hours | 24 hours | No change | Your SLA compliance rate might suddenly look great on paper while actual customer wait times double or triple. A ticket with a "1 day" resolution SLA that previously needed to be resolved within a single 8-hour working day now has **24 business hours** — which spans three actual working days on an 8-hour schedule. If you have contractual SLAs with customers defined in "days," the platform change may put you in compliance technically while violating the spirit of your agreement. To prevent unintended changes, SLA configurations currently defined in days must be converted to hours. All SLA policies must also be mapped to Groups that share the same Business hours. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000011682-freshdesk-upcoming-changes-december-2025-march-2026-)) **Action required:** Convert every SLA policy that uses "days" to the equivalent number of hours using this formula: `current days × your daily business hours = new hours value`. For example, if you work 8-hour days and have a "2 day" resolution SLA, set it to 16 hours. ### Omniroute Unification The routing engine is now consolidated into a single **Omniroute** dashboard that unifies round-robin, skill-based, and load-based assignment. The newer round-robin logic uses real-time workload, availability, and assignment preferences instead of just cycling by creation time. Admins can choose which statuses affect agent load and whether routing should prioritize created time, response SLA, or resolution SLA. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000011682-freshdesk-upcoming-changes-december-2025-march-2026-)) Agent availability is now managed globally rather than per channel. If you have complex automation rules that route emails differently than chats based on specific agent statuses, those rules require a complete audit. The new engine defaults to a unified capacity model, which can easily overwhelm agents if chat concurrency limits are not properly reconfigured alongside email ticket limits. **Example risk scenario:** An agent previously handled a maximum of 3 concurrent chats OR 20 open email tickets independently. Under unified Omniroute, both channels draw from the same capacity pool. Without reconfiguration, the agent could receive 3 chats AND 20 emails simultaneously, since the system doesn't inherently know your old per-channel limits. What to audit after the upgrade: - Any SLA defined in days, especially if it drives automations or customer commitments - Any queue or dashboard that assumes legacy round-robin behavior - Any supervisor workflow that depends on old group-level availability controls - Any analytics comparison where pre-upgrade and post-upgrade SLA calculations are being treated as apples-to-apples - Per-channel capacity limits that need to be translated into unified Omniroute capacity settings For a thorough post-upgrade validation process, see our [Post-Migration QA: 20 Tests to Run After Your Help Desk Data Migration](https://clonepartner.com/blog/blog/help-desk-data-migration-qa-checklist/). ## Pricing and Feature Gating Implications While Wave 1 (standalone Freshdesk upgrade) does not change your current plan or pricing, teams evaluating the full Freshdesk Omni platform need to understand the pricing structure differences: - **Freshdesk standalone** plans (Growth, Pro, Enterprise) are priced lower per agent than the equivalent **Freshdesk Omni** plans, which bundle ticketing, chat, telephony, and AI into a single SKU. - **Freddy AI capabilities** — AI agents (customer-facing bots), AI Copilot (agent assist), and AI Insights (analytics) — are **not uniformly available across all Omni tiers**. AI agent sessions and Copilot features may require the Enterprise tier or carry separate usage-based charges depending on your contract date. Check your specific plan's feature comparison on [freshworks.com/freshdesk/pricing](https://www.freshworks.com/freshdesk/pricing/). - **Freshdesk's Free plan** (up to 2 agents) exists for standalone Freshdesk but is **not available in Freshdesk Omni**. Teams that used a free account for testing, staging, or lightweight internal support will need to purchase a paid Omni plan or maintain a standalone Freshdesk instance. **Action required:** Before deciding between "stay and upgrade" vs. "switch platforms," request an updated quote from Freshworks for your specific agent count on the Freshdesk Omni plan tier that matches your current feature set. Compare this against per-agent pricing from Zendesk ($55–$115/agent/month for Suite plans), Intercom ($29–$132/seat/month), or Help Scout ($50–$65/user/month) to understand total cost of ownership. ## The Freshchat Trap: No Direct Upgrade Path This is the part Freshworks buries in their FAQ. **There is no direct upgrade path from Freshchat to Freshdesk Omni.** Freshchat and the new Freshdesk Omni are on separate platforms. You must sign up for a new Freshdesk Omni account, and the setup must be done manually from scratch. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000011818-how-to-upgrade-to-the-new-freshdesk-or-freshdesk-omni-)) If you're running Freshdesk and Freshchat together — a common setup for teams that added live chat after adopting Freshdesk — Freshworks says your Freshdesk data and configurations will be retained and upgraded, but you still need to manually transfer all Freshchat configurations into the new Freshdesk Omni experience. Classic Omnichannel customers are not fully spared either. Freshworks says live chat is available as a native channel in the unified workspace, but existing chat configurations will not be carried over and must be set up again in Freshdesk Omni 2025. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000012004-overview-of-freshdesk-omni-2025-upgrade)) The operational reality: - **Chat history**: Existing Freshchat conversation data does not carry over automatically. You need to export and migrate it separately. - **Bot configurations**: Freshchat bots, flows, and canned responses must be rebuilt inside Freshdesk Omni. - **Channel setup**: WhatsApp, Facebook Messenger, and widget configurations from Freshchat need to be reconnected from scratch. - **Retention clock**: For accounts with no new chat conversations in the last 90 days, Freshworks states that previous chat data will be deleted from the current account and remain available for **30 days in a separate Freshchat trial account**. If you don't export or migrate that data within 30 days, it's gone. ([support.freshdesk.com](https://support.freshdesk.com/support/solutions/articles/50000012004-overview-of-freshdesk-omni-2025-upgrade)) > [!CAUTION] > If you are coming from Freshchat, plan for a real migration project: export history, rebuild bots and channel settings, remap identities, and validate transcripts before the old environment ages out. Freshchat's API rate limits are hourly and plan-specific, and list APIs are paginated — on large chat histories, "we'll just export it later" becomes a scheduling and throttling problem. ([developers.freshchat.com](https://developers.freshchat.com/api/)) This is not an upgrade. It is a full-scale data migration masquerading as one. If you're already being forced to rebuild your chat infrastructure from scratch, it's worth evaluating whether Freshdesk Omni is even the right destination — or whether [migrating to Intercom](https://clonepartner.com/blog/blog/freshdesk-to-intercom-migration-guide/) or [migrating to Zendesk](https://clonepartner.com/blog/blog/freshdesk-to-zendesk-migration-guide/) makes more sense while you're already doing the work. ## Multi-Product Freshworks Customers: Additional Risk If you're using Freshdesk alongside **Freshsales** (CRM) or **Freshservice** (ITSM), the Neo platform migration introduces additional data flow risks: - **Contact sync between Freshdesk and Freshsales**: If Freshsales syncs contacts to Freshdesk and any of those contacts have non-compliant phone numbers, the sync will start failing post-upgrade. The failure occurs on the Freshdesk side, but the root cause is dirty data in Freshsales. - **Shared contact records**: If contacts exist in both Freshdesk and Freshsales with different phone number formats, the Neo platform's stricter validation may create divergence between the two systems. - **Custom integrations between products**: Any middleware or Zapier flows that move data between Freshworks products and touch phone or dropdown fields need to be audited for the same validation issues described above. **Action required:** Audit not just Freshdesk contacts, but every upstream system that writes to Freshdesk contact records. ## Migration Options: Upgrade, Reconfigure, or Switch Faced with a mandatory upgrade that requires significant manual reconfiguration, you have three paths forward. Use the decision tree below to identify which path fits your situation, then review the detailed breakdown. ### Decision Tree ``` START: Do you use Freshchat or classic Omnichannel chat? ├── NO → Do you have clean contact data + simple SLAs? │ ├── YES → Option 1 (Accept and fix) │ └── NO → Option 1, but budget 2–3 weeks for cleanup ├── YES → Are you committed to staying on Freshworks? │ ├── YES → Do you have >10,000 chat conversations to migrate? │ │ ├── YES → Option 2, budget 4–6 weeks │ │ └── NO → Option 2, budget 2–3 weeks │ └── NO → Are you already evaluating other platforms? │ ├── YES → Option 3 (Use as exit ramp) │ └── NO → Compare total effort: Option 2 vs Option 3 │ (If chat rebuild effort ≈ platform switch effort, evaluate Option 3) ``` ### Option 1: Accept the Upgrade and Fix What Breaks **Best for:** Teams with clean data, simple SLA policies, no Freshchat dependency, and few Marketplace apps. **Effort required:** - Audit and clean all contact phone fields - Convert SLA policies from days to hours - Test automation rules post-upgrade - Review dropdown field values for `_copy` renames - Verify all third-party integrations still write valid data - Snapshot all saved reports and dashboards for post-upgrade comparison - Test Marketplace app functionality, especially apps that write to contacts **Timeline:** 1–3 weeks of admin work, depending on data volume and integration count. ### Option 2: Upgrade to Freshdesk Omni and Migrate Freshchat **Best for:** Teams committed to the Freshworks ecosystem who want the unified Command Center and cross-channel tickets. **Effort required:** - Everything from Option 1, plus: - Export all Freshchat conversation history before the 30-day access window closes - Rebuild bot flows and canned responses - Reconnect all messaging channels (WhatsApp, Messenger, widget) - Retrain agents on the Command Center interface - Re-map any Freshchat-specific automations - Evaluate Freddy AI feature availability on your specific plan tier **Timeline:** 2–6 weeks, depending on Freshchat complexity and conversation volume. ### Option 3: Use the Forced Upgrade as an Exit Ramp **Best for:** Teams already frustrated with Freshworks, teams with complex Freshchat setups that would require full rebuilds anyway, or teams whose integration stack aligns better with another platform. If you're being forced to rebuild your chat infrastructure and re-audit your entire SLA and contact configuration regardless, the incremental effort of switching to Zendesk, Intercom, or Help Scout is smaller than it would be in normal times. You're already eating the disruption. | Factor | Stay on Freshdesk Omni | Switch to Zendesk | Switch to Intercom | |---|---|---|---| | Data model rework | Required (Neo platform) | Required (new schema) | Required (new schema) | | Chat rebuild | Required (from scratch) | Included in migration | Included in migration | | SLA reconfiguration | Required (new math) | Required (new rules) | Different model (conversation-based) | | Historical data | Retained (except Freshchat) | Must be migrated | Must be migrated | | Marketplace/app ecosystem | ~1,200 apps (compatibility uncertain) | ~1,600+ apps (mature ecosystem) | ~400+ apps (growing) | | Per-agent cost (mid-tier) | Check current Omni pricing | $89/agent/month (Suite Growth) | $85/seat/month (Advanced) | | AI capabilities | Freddy AI (plan-dependent) | Zendesk AI (add-on, $50/agent/month) | Fin AI ($0.99/resolution) | | Contractual leverage | None (forced upgrade) | New customer negotiation power | New customer negotiation power | For teams evaluating alternatives, our [Zendesk vs Freshdesk decision matrix](https://clonepartner.com/blog/blog/zendesk-vs-freshdesk-2026-the-operations-leads-decision-matrix/) covers the architectural differences in detail. If you're leaning toward Intercom, especially from Freshchat, our [Freshdesk to Intercom migration guide](https://clonepartner.com/blog/blog/freshdesk-to-intercom-migration-guide/) maps the data model differences. And for a complete pre-migration audit, use the [Freshdesk Migration Checklist](https://clonepartner.com/blog/blog/freshdesk-migration-checklist/). ## Why DIY Migration Scripts Fail on the Neo Platform The strict validation rules in the Neo platform make DIY migrations and AI-generated scripts especially risky. A script that worked perfectly against the old Freshdesk API will start throwing silent failures the moment it encounters a contact phone field with parentheses, dashes, or letters. Common failure patterns: - **Phone number formatting**: Scripts that pass `(555) 123-4567` or `+1-555-123-4567` will fail. Only `+15551234567` is accepted. The API returns a 400 error with a validation message, but bulk scripts often log and continue — meaning you end up with partial data loads. - **Dropdown value mismatches**: If your source data has dropdown values that matched pre-upgrade but now have `_copy` appended, your field mapping breaks. A script inserting `region: "APAC"` will fail if the field now only accepts `"APAC_copy"`. - **Contact deduplication conflicts**: The Neo platform's new unique field constraints (admins can mark up to two fields as unique) create merge conflicts that basic scripts don't handle. - **Rate limiting**: Freshdesk's API enforces per-minute rate limits that vary by plan (e.g., Freshdesk Free: 50 calls/minute, Growth: 200, Pro: 400, Enterprise: 700) — and even invalid requests count against the limit. If you bulk-push dirty contact updates and let retries thrash, you burn rate-limit budget while still failing validation. ([developers.freshdesk.com](https://developers.freshdesk.com/api/)) - **Partial state on failure**: Scripts that create a contact, then update it with phone numbers in a second call, can leave orphaned contact records if the update fails validation. You end up with contacts that exist but have no phone data — and no easy way to identify which ones are incomplete. For a deeper analysis, see [Why DIY AI Scripts Fail and How to Engineer Accountability](https://clonepartner.com/blog/blog/why-ai-migration-scripts-fail/). ## How ClonePartner Handles the Freshdesk Omni Transition We treat the Freshdesk Omni move as four separate workstreams: **data contract cleanup**, **workflow parity**, **channel rebuild**, and **cutover control**. **Neo platform data cleanup**: We programmatically clean and transform legacy contact data before it hits Neo validation — normalizing phone numbers to E.164 format, splitting extensions into separate custom fields, remapping non-phone data out of phone fields, and resolving `_copy` suffix conflicts in dropdown values. **Freshchat extraction**: We extract full conversation history, metadata, and contact associations from Freshchat's API, transform the data to match Omni's ticket-based model, and load it with correct threading and timestamps — before your data access window closes. **SLA and routing validation**: We replay SLA and routing scenarios against the new 24-business-hour logic and Omniroute behavior instead of assuming legacy automations still mean the same thing. **Zero-downtime cutover**: We run migrations in the background with delta syncs so live support keeps moving while historical data, identities, and configuration are validated. Your agents keep working in the legacy system until the exact moment of cutover, and we catch any tickets created during the migration window to ensure zero data loss. Every migration includes a sample run, field-by-field validation, and a full [QA checklist](https://clonepartner.com/blog/blog/help-desk-data-migration-qa-checklist/) before go-live. ## What to Do This Week Regardless of which path you choose, do these seven things now: 1. **Identify your wave.** Legacy Freshdesk, classic Omnichannel, and Freshchat do not share the same path. Check for an in-product banner — once the upgrade is complete, Freshworks notifies you there. If you don't see it, your account is likely still in queue. 2. **Export your Freshchat data immediately** if you're on classic Omnichannel or running Freshchat. The retention window starts when your account upgrades — not when you notice. 3. **Audit every SLA policy** that uses "days" as the time unit. Convert to hours using the formula: `current days × your daily business hours = new hours value`. Retest any automation tied to due times. 4. **Run a contact export** and filter for invalid phone numbers. Fix them before hard validation kicks in, or they'll disappear from your main contact list into the "Contacts that need action" view. Use the SQL query above or export to CSV and filter for any phone field containing characters other than digits and `+`. 5. **Test every integration** that writes to contact or company records. Send a test contact with your current phone format and confirm it's accepted. Check Zapier zaps, Make scenarios, CRM syncs, and any custom middleware. 6. **Inventory your Marketplace apps** and check each one for Neo platform compatibility. Contact vendors of critical apps directly. Do not assume that "the app still installs" means "the app still works correctly." 7. **Snapshot your reports and dashboards.** Export key metrics (SLA compliance rates, ticket volumes by status, CSAT scores) now so you have a pre-upgrade baseline. After the upgrade, compare outputs to catch any silent changes from the SLA recalculation or dropdown renaming. The Freshdesk Omni upgrade isn't optional, and the clock is already running. The teams that come through it cleanly are the ones that audit their data, integrations, and app dependencies *before* the upgrade hits their account — not after tickets start failing silently. > Whether you're migrating Freshchat to Freshdesk Omni, cleaning up contact data for the Neo platform, or using this forced upgrade as the push to switch platforms entirely — our team has done this before. Book a 30-minute call and we'll map out your specific situation. > > [Talk to us](https://cal.com/clonepartner/meet?duration=30) ## Frequently asked questions ### Is the Freshdesk Omni upgrade mandatory? Yes. All standalone Freshdesk customers who signed up before December 1, 2025 are being automatically upgraded between December 2025 and April 2026. There is no opt-out. Classic Omnichannel customers have a self-serve upgrade flow rolling out between April and June 2026. ### Can I upgrade from Freshchat to Freshdesk Omni directly? No. Freshworks confirms there is no direct upgrade path because Freshchat and Freshdesk Omni run on separate platforms. You must sign up for a new Freshdesk Omni account and manually transfer all configurations, bot flows, and channel setups from scratch. ### How does the Freshdesk SLA calculation change in 2026? Previously, 1 business day equaled your configured working hours (e.g., 8 hours). After the upgrade, 1 day equals 24 business hours, which may span multiple working days. You must convert SLA targets from days to hours to preserve your current response expectations. ### What happens to contacts with invalid phone numbers after the Freshdesk upgrade? Contacts with invalid phone numbers (containing letters, special characters, or outside the 6–30 character range) are moved to a separate 'Contacts that need action' view. They won't appear in the main contact list and can't be filtered or used in some workflows until corrected. ### Will my Freshdesk integrations still work after the Omni upgrade? Freshworks says API endpoints remain unchanged, but integrations can still fail if they create or update contacts with data that no longer passes Neo validation rules — for example, phone numbers with parentheses, dashes, or letters.