{"id":2371,"date":"2026-05-10T10:00:00","date_gmt":"2026-05-10T10:00:00","guid":{"rendered":"https:\/\/aaxonix.com\/resources\/?p=2371"},"modified":"2026-05-14T15:32:11","modified_gmt":"2026-05-14T15:32:11","slug":"freshdesk-to-zoho-desk-migration","status":"publish","type":"post","link":"https:\/\/aaxonix.com\/resources\/freshdesk-to-zoho-desk-migration\/","title":{"rendered":"Freshdesk to Zoho Desk Migration: Move Your Support Tickets Without Downtime"},"content":{"rendered":"<style>\n.aax-post{font-family:'Poppins',sans-serif;color:#1a2332;max-width:820px;margin:0 auto;line-height:1.75}\n.aax-post h2{font-size:1.55rem;font-weight:600;margin:2.5rem 0 .9rem;color:#0a1628}\n.aax-post h3{font-size:1.15rem;font-weight:600;margin:1.8rem 0 .6rem;color:#1a2332}\n.aax-post p{margin:0 0 1.1rem}\n.aax-post ul,.aax-post ol{margin:0 0 1.1rem;padding-left:1.5rem}\n.aax-post li{margin-bottom:.45rem}\n.aax-post table{width:100%;border-collapse:collapse;margin:1.5rem 0;font-size:.93rem}\n.aax-post th{background:#0a1628;color:#fff;padding:.6rem 1rem;text-align:left}\n.aax-post td{padding:.55rem 1rem;border-bottom:1px solid #e8edf4}\n.aax-post tr:nth-child(even) td{background:#f5f7fb}\n.aax-post .faq-section{background:#f5f7fb;border-radius:10px;padding:1.8rem 2rem;margin:2.5rem 0}\n.aax-post .faq-item{margin-bottom:1.2rem;border-bottom:1px solid #e0e6ef;padding-bottom:1.2rem}\n.aax-post .faq-item:last-child{border-bottom:none;margin-bottom:0;padding-bottom:0}\n.aax-post .faq-question{font-weight:600;color:#0a1628;margin-bottom:.5rem}\n.aax-post .faq-answer{color:#3a4a5c;line-height:1.65}\n.aax-post .aax-cta{background:linear-gradient(135deg,#0a1628 0%,#1a3a5c 100%);border-radius:12px;padding:1.8rem 2rem;margin:2.5rem 0;text-align:center}\n.aax-post .aax-cta p{color:#e8edf4;margin:0 0 1.2rem;font-size:1.05rem}\n.aax-post .aax-cta a{display:inline-block;background:#fff;color:#0a1628;font-weight:600;padding:.65rem 1.6rem;border-radius:6px;text-decoration:none;font-size:.95rem}\n<\/style>\n<div class=\"sp-toc-wrap\"><nav class=\"sp-blog-toc\" id=\"spBlogToc\" style=\"display:none\">\n  <h4><svg width=\"14\" height=\"14\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><line x1=\"8\" y1=\"6\" x2=\"21\" y2=\"6\"\/><line x1=\"8\" y1=\"12\" x2=\"21\" y2=\"12\"\/><line x1=\"8\" y1=\"18\" x2=\"21\" y2=\"18\"\/><line x1=\"3\" y1=\"6\" x2=\"3.01\" y2=\"6\"\/><line x1=\"3\" y1=\"12\" x2=\"3.01\" y2=\"12\"\/><line x1=\"3\" y1=\"18\" x2=\"3.01\" y2=\"18\"\/><\/svg> On this page<\/h4>\n  <ol class=\"sp-toc-list\" id=\"spTocList\"><\/ol>\n<\/nav><\/div>\n<div class=\"aax-post\">\n\n<p>A <a href=\"https:\/\/aaxonix.com\/resources\/zoho-desk-vs-freshdesk-india\/\" class=\"sp-content-link\">Zoho Desk vs Freshdesk comparison<\/a> to Zoho Desk migration is one of the more common helpdesk switches businesses make when moving their entire stack to Zoho One or when Freshdesk&#8217;s pricing no longer fits their growth trajectory. The concern that comes up most often is not whether Zoho Desk can handle the workload \u2014 it can \u2014 but whether the move will disrupt open tickets, break SLA timers, or confuse agents mid-shift. With the right preparation, none of those things need to happen. This guide walks through the complete migration process: what to export, how to map it, how to <a href=\"https:\/\/aaxonix.com\/resources\/zoho-desk-setup-india\/\" class=\"sp-content-link\">Zoho Desk setup for Indian teams<\/a>e Zoho Desk before cutting over, and what to check after the migration is done.<\/p>\n\n\n<figure style=\"margin:36px 0;text-align:center;line-height:0;\"><img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/04\/inline_freshdesk-to-zoho-desk-migration_1.jpg\" alt=\"Detailed view of a server rack with a focus on technology and data storage.\" style=\"width:100%;max-width:820px;height:auto;border-radius:10px;box-shadow:0 4px 20px rgba(10,22,40,.13);\" loading=\"lazy\" \/><\/figure>\n<h2>Why Teams Switch from Freshdesk to Zoho Desk<\/h2>\n\n<p>Most migrations start with a commercial trigger. Freshdesk&#8217;s per-agent pricing on its Growth and Pro plans can become expensive as headcount scales, particularly for teams needing automation, analytics, and multi-channel support simultaneously. Zoho Desk, priced from $14 per agent per month on the Standard plan, typically comes in 20\u201340% lower when bundled with Zoho One.<\/p>\n\n<p>Cost is not the only driver. Teams already using Zoho CRM find the native CRM-Desk sync genuinely useful: ticket context, contact history, and deal stage are visible from within the ticket interface without any third-party connector. Freshdesk offers a Zoho CRM integration, but it requires setup and does not offer the same field-level depth as Zoho&#8217;s native bridge.<\/p>\n\n<p>Other reasons teams cite:<\/p>\n<ul>\n  <li>Zoho Desk&#8217;s Blueprint feature for multi-step ticket workflows with conditional branching<\/li>\n  <li>Better round-robin and skill-based assignment rules on the Enterprise plan<\/li>\n  <li>Zia, Zoho Desk&#8217;s AI assistant, for sentiment analysis and suggested responses<\/li>\n  <li>Unified Zoho billing instead of managing separate vendor contracts<\/li>\n<\/ul>\n\n<p>None of these advantages matter if the migration is botched. The sections below cover how to do it cleanly.<\/p>\n\n<h2>What Data Migrates and What Does Not<\/h2>\n\n<p>Before starting any <a href=\"https:\/\/aaxonix.com\/resources\/data-migration-to-zoho-guide\/\" class=\"sp-content-link\">data migration to Zoho<\/a>, it is worth being precise about which objects Freshdesk exports and which Zoho Desk can import natively.<\/p>\n\n<table>\n  <thead>\n    <tr>\n      <th>Data Object<\/th>\n      <th>Freshdesk Export<\/th>\n      <th>Zoho Desk Import<\/th>\n      <th>Notes<\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td>Tickets (open, resolved, closed)<\/td>\n      <td>CSV \/ API<\/td>\n      <td>API only<\/td>\n      <td>Native CSV import is limited; API recommended<\/td>\n    <\/tr>\n    <tr>\n      <td>Contacts<\/td>\n      <td>CSV<\/td>\n      <td>CSV<\/td>\n      <td>Standard field mapping; custom fields need pre-creation<\/td>\n    <\/tr>\n    <tr>\n      <td>Companies \/ Accounts<\/td>\n      <td>CSV<\/td>\n      <td>CSV<\/td>\n      <td>Parent-child account hierarchies need manual mapping<\/td>\n    <\/tr>\n    <tr>\n      <td>Ticket comments and replies<\/td>\n      <td>API only<\/td>\n      <td>API only<\/td>\n      <td>Requires third-party migration tool or custom script<\/td>\n    <\/tr>\n    <tr>\n      <td>Attachments<\/td>\n      <td>API (per ticket)<\/td>\n      <td>API (per ticket)<\/td>\n      <td>Large volumes significantly increase migration time<\/td>\n    <\/tr>\n    <tr>\n      <td>Knowledge base articles<\/td>\n      <td>CSV \/ API<\/td>\n      <td>CSV \/ API<\/td>\n      <td>Category hierarchy needs to be recreated first<\/td>\n    <\/tr>\n    <tr>\n      <td>SLA policies<\/td>\n      <td>Not exportable<\/td>\n      <td>Manual recreation<\/td>\n      <td>Must be rebuilt in Zoho Desk before cutover<\/td>\n    <\/tr>\n    <tr>\n      <td>Automation rules<\/td>\n      <td>Not exportable<\/td>\n      <td>Manual recreation<\/td>\n      <td>Freshdesk rule logic maps to Zoho Desk workflow rules<\/td>\n    <\/tr>\n    <tr>\n      <td>CSAT scores and ratings<\/td>\n      <td>CSV<\/td>\n      <td>No native import<\/td>\n      <td>Historical CSAT data is typically archived, not migrated<\/td>\n    <\/tr>\n    <tr>\n      <td>Agent profiles and roles<\/td>\n      <td>Not exportable<\/td>\n      <td>Manual recreation<\/td>\n      <td>Invite agents to Zoho Desk; roles are reconfigured<\/td>\n    <\/tr>\n  <\/tbody>\n<\/table>\n\n<p>The practical takeaway: contacts, companies, and knowledge base articles migrate cleanly via CSV. Tickets with full conversation history require either a paid migration tool like Help Desk Migration or a custom Python\/Node script against both APIs. SLA policies, automation rules, and agent roles cannot be exported and must be rebuilt.<\/p>\n\n<h2>Step-by-Step Freshdesk to Zoho Desk Migration Process<\/h2>\n\n<h3>Phase 1: Audit and Preparation (1\u20132 weeks before cutover)<\/h3>\n\n<p>Start by pulling a full ticket report from Freshdesk. Go to Reports > Overview, filter by all statuses, and export to CSV. This gives you a baseline count: total tickets, open tickets by agent, tickets by channel (email, chat, phone, social). You need this number to verify completeness after migration.<\/p>\n\n<p>Next, document every active SLA policy in Freshdesk. Go to Admin > SLA Policies and screenshot or copy each rule: response time, resolution time, escalation targets, and business hours configuration. You will rebuild these in Zoho Desk before any tickets are moved.<\/p>\n\n<p>Export contacts and companies from Freshdesk (Admin > Import &#038; Export > Contacts). Open the CSV and identify any custom fields. Create matching custom fields in Zoho Desk (Setup > Customization > Fields) before importing \u2014 Zoho Desk will reject rows that reference fields that do not exist.<\/p>\n\n<h3>Phase 2: Configure Zoho Desk Before Moving Tickets<\/h3>\n\n<p>This phase is the most important one. Migrating tickets into an unconfigured Zoho Desk instance creates a mess that is harder to untangle than starting the migration late. Configure in this order:<\/p>\n\n<ol>\n  <li><strong>Departments:<\/strong> Create departments in Zoho Desk that mirror your Freshdesk groups. Tickets are assigned at the department level in Zoho Desk.<\/li>\n  <li><strong>Agent accounts:<\/strong> Invite all agents. Assign roles (Administrator, Agent, Light Agent) and associate each agent with the relevant department.<\/li>\n  <li><strong>SLA policies:<\/strong> Rebuild every SLA policy from your documentation. Set business hours first (Setup > Business Hours) because SLA timers reference them.<\/li>\n  <li><strong>Email channels:<\/strong> Connect your support email addresses (Setup > Channels > Email). Zoho Desk will send a verification. Do NOT disconnect Freshdesk email until you are ready to cut over.<\/li>\n  <li><strong>Ticket fields:<\/strong> Create all custom ticket fields before importing. Standard fields (priority, status, channel) map automatically.<\/li>\n  <li><strong>Workflow rules:<\/strong> Rebuild Freshdesk automation rules as Zoho Desk workflow rules (Setup > Automation > Workflows). Start with assignment and escalation rules.<\/li>\n<\/ol>\n\n<p>Run a smoke test: create 5\u201310 test tickets via your support email while Freshdesk is still active. Verify that Zoho Desk receives them (they will, because you have not pointed DNS to Zoho yet), SLA timers fire, and assignment rules apply correctly.<\/p>\n\n<h3>Phase 3: Migrate Contacts and Companies<\/h3>\n\n<p>Import contacts first (Setup > Import &#038; Export > Import Contacts). Map CSV columns to Zoho Desk fields. Fix any validation errors \u2014 typically phone number format or empty required fields. Import companies next. Confirm record counts match your Freshdesk export.<\/p>\n\n<h3>Phase 4: Migrate Tickets<\/h3>\n\n<p>For ticket migration, you have three options:<\/p>\n\n<ul>\n  <li><strong>Help Desk Migration (recommended for most teams):<\/strong> A paid SaaS tool that handles the Freshdesk API to Zoho Desk API translation, including comments and attachments. Pricing starts around $50 for small volumes. It preserves ticket IDs in a custom field so you can cross-reference old tickets.<\/li>\n  <li><strong>Custom API script:<\/strong> Use the Freshdesk REST API to pull tickets page by page, then POST each ticket to the Zoho Desk API. You maintain full control and pay only for compute time, but you need developer resources and testing time.<\/li>\n  <li><strong>Selective migration:<\/strong> Only migrate open tickets and last 90 days of resolved tickets. Archive older resolved tickets in Freshdesk (keep the account active in read-only mode) and close it down later. This option significantly reduces migration complexity.<\/li>\n<\/ul>\n\n<p>Whichever method you use, run a test migration first on a sample of 50\u2013100 tickets. Verify: ticket subject, description, creation date, contact association, and comment thread. Fix mapping issues before running the full migration.<\/p>\n\n<h3>Phase 5: Cutover<\/h3>\n\n<p>Schedule the cutover during your lowest-traffic window (typically a weekend night). The sequence:<\/p>\n\n<ol>\n  <li>Pause or disable new ticket creation in Freshdesk (put support email in vacation mode or remove the MX record temporarily).<\/li>\n  <li>Run a final delta migration of any tickets created after your last migration run.<\/li>\n  <li>Update your MX records or email forwarding to point to Zoho Desk&#8217;s mail server.<\/li>\n  <li>Notify agents: Zoho Desk is now live. All new tickets come here.<\/li>\n  <li>Keep Freshdesk active in read-only mode for 30 days for reference.<\/li>\n<\/ol>\n\n\n<figure style=\"margin:36px 0;text-align:center;line-height:0;\"><img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/04\/inline_freshdesk-to-zoho-desk-migration_2.jpg\" alt=\"Caucasian woman in gray sweater and glasses providing customer support using a headset in an office.\" style=\"width:100%;max-width:820px;height:auto;border-radius:10px;box-shadow:0 4px 20px rgba(10,22,40,.13);\" loading=\"lazy\" \/><\/figure>\n<h2>Post-Migration Configuration Checklist<\/h2>\n\n<p>Once tickets are in Zoho Desk and agents are working from the new system, work through this checklist within the first 48 hours:<\/p>\n\n<ul>\n  <li>Verify that the <a href=\"https:\/\/aaxonix.com\/products\/zoho-desk\/\" class=\"sp-content-link\">Zoho Desk helpdesk platform<\/a> is receiving emails from all channels (email, contact form, chat widget)<\/li>\n  <li>Confirm SLA timers are running on open tickets \u2014 check a ticket created after cutover and verify first response due time is correct<\/li>\n  <li>Test the customer reply flow: reply to a ticket from a customer email address and verify the reply appends to the correct ticket thread<\/li>\n  <li>Validate assignment rules: create a test ticket that should match each rule and confirm it routes correctly<\/li>\n  <li>Check that Zoho CRM integration is syncing contacts (if you are using Zoho CRM)<\/li>\n  <li>Review the CSAT survey configuration \u2014 Freshdesk&#8217;s survey links will no longer be valid<\/li>\n  <li>Set up Zoho Desk reports to mirror your baseline Freshdesk dashboards (Tickets by status, First response time, Resolution time)<\/li>\n<\/ul>\n\n<h2>Common Migration Mistakes and How to Avoid Them<\/h2>\n\n<p>Teams that struggle with a <a href=\"https:\/\/aaxonix.com\/resources\/zoho-desk-zendesk-migration-guide\/\" class=\"sp-content-link\">zoho desk migration from zendesk<\/a> or Freshdesk typically make one of the same four mistakes:<\/p>\n\n<h3>1. Migrating tickets before configuring SLAs<\/h3>\n<p>Tickets imported before SLA policies are active arrive with no SLA timer attached. You cannot retroactively start SLA timers on historical tickets. Always build SLA configuration before importing any live tickets.<\/p>\n\n<h3>2. Not pre-creating custom fields<\/h3>\n<p>Zoho Desk silently drops custom field data during CSV import if the target field does not exist. There is no error log \u2014 the data just vanishes. Create every custom field before importing contacts or tickets.<\/p>\n\n<h3>3. Cutting over email before agents are trained<\/h3>\n<p>Even a two-hour training session on Zoho Desk&#8217;s interface before cutover significantly reduces ticket handling errors and agent confusion on day one. Agents who have never seen the Zoho Desk ticket view will lose time finding basic functions under pressure.<\/p>\n\n<h3>4. Forgetting the knowledge base migration<\/h3>\n<p>Help center articles are often an afterthought. If your Freshdesk knowledge base is linked from customer-facing pages, migrating it and redirecting URLs is part of the migration scope, not an optional add-on. Update your customer-facing help links within the first week.<\/p>\n\n<h2>Migration Timeline: What to Expect<\/h2>\n\n<table>\n  <thead>\n    <tr>\n      <th>Phase<\/th>\n      <th>Duration<\/th>\n      <th>Key Activities<\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td>Audit and documentation<\/td>\n      <td>3\u20135 days<\/td>\n      <td>Export contacts, document SLAs, count tickets<\/td>\n    <\/tr>\n    <tr>\n      <td>Zoho Desk configuration<\/td>\n      <td>5\u201310 days<\/td>\n      <td>Departments, agents, SLAs, workflows, email channels<\/td>\n    <\/tr>\n    <tr>\n      <td>Test migration<\/td>\n      <td>1\u20132 days<\/td>\n      <td>50\u2013100 ticket sample, verify mapping<\/td>\n    <\/tr>\n    <tr>\n      <td>Full migration<\/td>\n      <td>1\u20133 days<\/td>\n      <td>Contacts, companies, tickets (volume-dependent)<\/td>\n    <\/tr>\n    <tr>\n      <td>Cutover and validation<\/td>\n      <td>1 day<\/td>\n      <td>Email switch, agent go-live, 48-hour checklist<\/td>\n    <\/tr>\n    <tr>\n      <td>Parallel running period<\/td>\n      <td>30 days<\/td>\n      <td>Freshdesk in read-only, close out after no new references<\/td>\n    <\/tr>\n  <\/tbody>\n<\/table>\n\n<p>Total elapsed time for a team of 10\u201320 agents with 5,000\u201315,000 historical tickets: typically 3\u20134 weeks from project kick-off to full cutover. Larger volumes or complex automation setups can extend this to 6\u20138 weeks.<\/p>\n\n<div class=\"faq-section\">\n  <h2>Frequently Asked Questions<\/h2>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">Can you migrate ticket history from Freshdesk to Zoho Desk without losing conversation threads?<\/p>\n    <p class=\"faq-answer\">Yes, but it requires using the APIs of both platforms rather than a CSV export. Tools like Help Desk Migration automate this process and preserve ticket conversations, internal notes, and attachments. A native CSV import from Freshdesk only transfers ticket metadata such as subject, status, and priority \u2014 conversation threads do not export via CSV.<\/p>\n  <\/div>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">How long does a Freshdesk to Zoho Desk migration take?<\/p>\n    <p class=\"faq-answer\">For a team of 10\u201320 agents with under 15,000 tickets, expect 3\u20134 weeks from start to full cutover. This includes configuration time in Zoho Desk, test migration, and the actual data move. The cutover itself (switching email channels) takes less than an hour; the preparation is where most time is spent.<\/p>\n  <\/div>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">Does Zoho Desk have a native Freshdesk import tool?<\/p>\n    <p class=\"faq-answer\">Zoho Desk does not have a dedicated Freshdesk import wizard. Contacts and companies can be imported via CSV. Tickets with full conversation history require the Zoho Desk API or a third-party migration tool. Zoho&#8217;s support team can provide API documentation and guidance, but the migration work itself requires planning and a tool or developer resource.<\/p>\n  <\/div>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">What happens to open tickets during the migration cutover?<\/p>\n    <p class=\"faq-answer\">If you run a delta migration correctly, open tickets are migrated in the final batch immediately before cutover. The cutover itself involves switching the email routing (MX records or forwarding rules), which takes effect within minutes. The recommended approach is to pause new ticket intake briefly during the final delta migration to avoid any tickets being split between systems.<\/p>\n  <\/div>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">Is Zoho Desk cheaper than Freshdesk for growing teams?<\/p>\n    <p class=\"faq-answer\">For most teams above 5 agents, Zoho Desk is priced lower than Freshdesk&#8217;s comparable plans. Zoho Desk Standard is $14 per agent per month; Professional is $23; Enterprise is $40. When bundled as part of Zoho One at $37 per user per month (billed annually), Zoho Desk is effectively included alongside 45+ other Zoho apps, making the per-app cost significantly lower than standalone Freshdesk licensing.<\/p>\n  <\/div>\n<\/div>\n\n<div class=\"aax-cta\">\n  <p>Aaxonix manages end-to-end Freshdesk to Zoho Desk migrations for support teams, covering data mapping, SLA rebuild, workflow configuration, and cutover planning. Book a free consultation and get a scoped migration plan with a realistic timeline for your team size and ticket volume.<\/p>\n  <a href=\"https:\/\/aaxonix.com\/contact\/\">Book a free consultation<\/a>\n<\/div>\n\n<p>A well-planned Freshdesk to Zoho Desk migration does not require downtime, and it does not require your agents to lose access to their ticket history. The critical work happens in the two weeks before cutover: documenting what you have, rebuilding it in Zoho Desk, and running a test migration before committing to the switch. Teams that treat the configuration phase as the migration and the data move as the final step tend to go live without incident.<\/p>\n\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Moving from Freshdesk to Zoho Desk? This step-by-step guide covers data export, ticket migration, SLA setup, and post-migration checks to keep support running.<\/p>\n","protected":false},"author":1,"featured_media":2368,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[645,641,642,644,643],"class_list":["post-2371","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-customer-support-migration","tag-freshdesk-to-zoho-desk","tag-helpdesk-migration","tag-ticket-migration","tag-zoho-desk-setup"],"_links":{"self":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/2371","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/comments?post=2371"}],"version-history":[{"count":2,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/2371\/revisions"}],"predecessor-version":[{"id":3652,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/2371\/revisions\/3652"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/media\/2368"}],"wp:attachment":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/media?parent=2371"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/categories?post=2371"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/tags?post=2371"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}