{"id":2414,"date":"2026-05-16T10:00:00","date_gmt":"2026-05-16T10:00:00","guid":{"rendered":"https:\/\/aaxonix.com\/resources\/?p=2414"},"modified":"2026-04-11T08:21:35","modified_gmt":"2026-04-11T08:21:35","slug":"dynamics-365-to-zoho-crm-migration","status":"publish","type":"post","link":"https:\/\/aaxonix.com\/resources\/dynamics-365-to-zoho-crm-migration\/","title":{"rendered":"Microsoft Dynamics 365 to Zoho CRM Migration: A Practical Guide for Mid-Market Teams"},"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\"><h4><svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\"><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><ol class=\"sp-toc-list\" id=\"spTocList\"><\/ol><\/nav><\/div>\n<div class=\"aax-post\">\n\n<p>A Dynamics 365 to Zoho CRM migration is one of the more common platform switches mid-market sales teams undertake, yet it rarely goes smoothly without a clear plan. Dynamics 365 is a capable platform, but its licensing structure, complexity overhead, and tight Microsoft ecosystem dependency push many 50-to-500 person sales teams toward Zoho CRM \u2014 where the total cost is lower, the customisation is more accessible, and the full Zoho suite adds marketing, support, and finance under one umbrella. This guide walks through exactly what&#8217;s involved in the migration: what data moves cleanly, what needs manual reconstruction, what the typical timeline looks like, and the configuration decisions that determine whether your team actually adopts the new platform or reverts to spreadsheets within 90 days.<\/p>\n\n<h2>Why Mid-Market Teams Are Moving Off Dynamics 365<\/h2>\n\n<p>The case against Dynamics 365 for mid-market teams is rarely about features \u2014 it has plenty. The issue is the total cost and operational overhead relative to what you actually use. Here are the most common reasons teams initiate a migration:<\/p>\n\n<ul>\n  <li><strong>Licensing cost:<\/strong> Dynamics 365 Sales Professional runs $65\/user\/month and Enterprise is $95\/user\/month. A team of 40 reps on Enterprise pays $3,800\/month \u2014 before add-ons, Power BI, or any other Microsoft 365 integration licensing.<\/li>\n  <li><strong>IT dependency:<\/strong> Most customisations in Dynamics require Power Platform skills or a developer with D365 certifications. Marketing, support, and pipeline changes often go through IT backlogs rather than being handled by operations teams directly.<\/li>\n  <li><strong>Microsoft ecosystem lock-in:<\/strong> Dynamics works best inside a full Microsoft stack. Teams already using Google Workspace or non-Microsoft ERP find integration friction high.<\/li>\n  <li><strong>Feature bloat:<\/strong> Dynamics 365 was built for enterprise complexity. Mid-market teams often use 30% of its features and pay for the rest.<\/li>\n<\/ul>\n\n<p>Zoho CRM Professional starts at $23\/user\/month, Enterprise at $40\/user\/month. A 40-person team on Enterprise pays $1,600\/month. The annual saving of $26,400 typically funds the migration and then some. See our <a href=\"https:\/\/aaxonix.com\/resources\/zoho-vs-dynamics-365-india\/\" class=\"sp-content-link\">zoho vs dynamics 365 breakdown<\/a> for a detailed feature comparison across both platforms.<\/p>\n\n<figure style=\"margin:2rem 0;text-align:center\"><img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/04\/p8_inline_1.jpg\" alt=\"Team analyzing business reports and charts during a collaborative meeting.\" style=\"max-width:100%;border-radius:8px;height:auto\" loading=\"lazy\"><figcaption style=\"font-size:.82rem;color:#6b7a8d;margin-top:.4rem\">Photo by Pavel Danilyuk \u00b7 Pexels<\/figcaption><\/figure>\n<h2>What Transfers Cleanly and What Doesn&#8217;t<\/h2>\n\n<p>Before planning a Dynamics 365 to Zoho CRM migration, audit your data against what Zoho CRM&#8217;s import tools can handle natively and what will require manual reconstruction.<\/p>\n\n<h3>Clean transfers (via export\/import)<\/h3>\n<ul>\n  <li>Contacts, Accounts, and Leads \u2014 standard CSV or Excel export from Dynamics, import into Zoho CRM with field mapping<\/li>\n  <li>Opportunities\/Deals \u2014 pipeline stage names need remapping, but the records transfer well<\/li>\n  <li>Activities: meetings, calls, tasks \u2014 exportable as CSV; Zoho supports bulk import<\/li>\n  <li>Products and Price Books \u2014 export from Dynamics product catalogue; re-import to Zoho&#8217;s Products module<\/li>\n  <li>Custom fields with simple data types \u2014 text, number, date, picklist<\/li>\n<\/ul>\n\n<h3>What requires manual reconstruction<\/h3>\n<ul>\n  <li><strong>Workflows and automation:<\/strong> Dynamics uses Power Automate flows. These have no direct export format compatible with Zoho. You must rebuild each automation as a Zoho Workflow Rule, Blueprint, or Zia trigger.<\/li>\n  <li><strong>Dashboards and reports:<\/strong> Dynamics dashboards are built in the Power Platform. Zoho Analytics and CRM&#8217;s native reporting require rebuilding from scratch \u2014 though the data is there.<\/li>\n  <li><strong>Custom entities:<\/strong> Any custom entities in Dynamics (beyond standard CRM modules) must be recreated as Custom Modules in Zoho CRM before data import.<\/li>\n  <li><strong>Email templates:<\/strong> Dynamics email templates need to be recreated in Zoho CRM or Zoho Campaigns.<\/li>\n  <li><strong>Notes and attachments:<\/strong> These can be exported but require careful mapping. Attachments may need to be re-uploaded in batches.<\/li>\n  <li><strong>Relationship hierarchies:<\/strong> Account-to-Contact and Account-to-Opportunity relationships must be re-established via lookup field mapping in Zoho&#8217;s import wizard.<\/li>\n<\/ul>\n\n<h2>Step-by-Step Migration Process<\/h2>\n\n<p>A clean <a href=\"https:\/\/aaxonix.com\/resources\/data-migration-to-zoho-guide\/\" class=\"sp-content-link\">data migration to zoho<\/a> follows six phases. Rushing any of them produces bad data in the new system, which kills user adoption.<\/p>\n\n<h3>Phase 1 \u2014 Audit and data cleanup (1\u20132 weeks)<\/h3>\n<p>Export all Dynamics 365 entities and run a data quality check before touching Zoho. Remove duplicate contacts, stale deals older than 18 months (or archive them), and standardise picklist values like industry, lead source, and deal stage names. Data problems that exist in Dynamics will be imported into Zoho if you skip this step.<\/p>\n\n<h3>Phase 2 \u2014 Zoho CRM setup and schema design (1\u20132 weeks)<\/h3>\n<p>Set up Zoho CRM org settings, user roles, and permissions profiles first. Then create custom modules and custom fields to match your Dynamics schema. Map Dynamics entities to Zoho modules before importing any data. This is also the time to configure pipeline stages in Deals, set up the product catalogue, and build territory rules if your team uses them.<\/p>\n\n<h3>Phase 3 \u2014 Test migration (1 week)<\/h3>\n<p>Run a test import with a 10\u201315% sample of your data \u2014 pick records that cover all your data types. Verify that relationships are intact (Contacts linked to correct Accounts, Deals linked to correct Contacts), that all custom field values imported correctly, and that no records were duplicated or truncated. Fix mapping errors before the full import.<\/p>\n\n<h3>Phase 4 \u2014 Full data import (2\u20135 days)<\/h3>\n<p>Import in sequence: Accounts first, then Contacts (linked to Accounts), then Deals (linked to Contacts and Accounts), then Activities. Import Products and Price Books last. Use Zoho CRM&#8217;s import history to monitor success rates and error logs in real time.<\/p>\n\n<h3>Phase 5 \u2014 Automation and workflow rebuild (1\u20132 weeks)<\/h3>\n<p>Recreate Dynamics workflows in Zoho. Zoho Workflow Rules handle simple if-then triggers (e.g., assign a lead when it hits a specific score). Blueprints are used for structured sales processes with mandatory fields and stage transitions. Macros handle batch actions. Map each Dynamics Power Automate flow to the appropriate Zoho equivalent before cutover.<\/p>\n\n<h3>Phase 6 \u2014 Training and cutover (1 week)<\/h3>\n<p>Run parallel systems for no more than two weeks \u2014 longer than that and data sync becomes a problem. Set a hard cutover date. Train reps on Zoho before go-live. Disable Dynamics data entry access on cutover day (read-only is fine for reference). Export one final snapshot from Dynamics on cutover day to capture the last few days of activity.<\/p>\n\n<figure style=\"margin:2rem 0;text-align:center\"><img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/04\/p8_inline_2.jpg\" alt=\"Laptop displaying Google Analytics in a modern workspace, highlighting digital analytics and technology.\" style=\"max-width:100%;border-radius:8px;height:auto\" loading=\"lazy\"><figcaption style=\"font-size:.82rem;color:#6b7a8d;margin-top:.4rem\">Photo by Negative Space \u00b7 Pexels<\/figcaption><\/figure>\n<h2>Mapping Dynamics 365 to Zoho CRM: Module and Feature Equivalents<\/h2>\n\n<table>\n  <thead>\n    <tr><th>Dynamics 365<\/th><th>Zoho CRM Equivalent<\/th><th>Migration approach<\/th><\/tr>\n  <\/thead>\n  <tbody>\n    <tr><td>Accounts<\/td><td>Accounts<\/td><td>Direct CSV import with field mapping<\/td><\/tr>\n    <tr><td>Contacts<\/td><td>Contacts<\/td><td>Direct CSV import; map Account lookup<\/td><\/tr>\n    <tr><td>Leads<\/td><td>Leads<\/td><td>Direct CSV import<\/td><\/tr>\n    <tr><td>Opportunities<\/td><td>Deals<\/td><td>CSV import; remap stage names<\/td><\/tr>\n    <tr><td>Activities (calls, tasks, meetings)<\/td><td>Activities module<\/td><td>CSV import in bulk<\/td><\/tr>\n    <tr><td>Products \/ Product Catalogue<\/td><td>Products<\/td><td>CSV import; recreate price books<\/td><\/tr>\n    <tr><td>Power Automate flows<\/td><td>Workflow Rules \/ Blueprints<\/td><td>Manual rebuild<\/td><\/tr>\n    <tr><td>Dashboards (Power BI)<\/td><td>Zoho CRM Reports \/ Zoho Analytics<\/td><td>Manual rebuild<\/td><\/tr>\n    <tr><td>Custom Entities<\/td><td>Custom Modules<\/td><td>Create module first, then import<\/td><\/tr>\n    <tr><td>Cases \/ Customer Service<\/td><td>Zoho Desk (separate product)<\/td><td>Separate migration path<\/td><\/tr>\n    <tr><td>Marketing (Dynamics 365 Marketing)<\/td><td>Zoho Campaigns \/ Marketing Automation<\/td><td>Separate migration path<\/td><\/tr>\n    <tr><td>Quotes \/ Orders<\/td><td>Quotes in Zoho CRM<\/td><td>Manual or CSV + PDF re-attachment<\/td><\/tr>\n  <\/tbody>\n<\/table>\n\n<h2>Common Pitfalls in Dynamics 365 to Zoho CRM Migrations<\/h2>\n\n<p>Most migration failures are predictable. These are the patterns that cause projects to stall or require re-migration:<\/p>\n\n<h3>Not cleaning data before import<\/h3>\n<p>Dynamics installations that have been running for 3+ years typically have 20\u201340% duplicate or stale contacts. Importing bad data into Zoho doesn&#8217;t clean it \u2014 it just moves the problem. Deduplicate before migration, not after.<\/p>\n\n<h3>Skipping the test import<\/h3>\n<p>Teams that import 80,000 contacts without a test run discover field mapping errors only after the full import \u2014 which means a full re-import after fixing the mapping. The test import phase saves days of cleanup time.<\/p>\n\n<h3>Building automation too early<\/h3>\n<p>Setting up Zoho Workflow Rules and Blueprints before verifying your pipeline stage names, custom field values, and user roles creates automation that fires on incorrect conditions. Build automation after the data is confirmed clean and the schema is finalised.<\/p>\n\n<h3>Running parallel systems too long<\/h3>\n<p>Two systems of record create split attention and data drift. Two weeks of parallel operation is the maximum. Beyond that, reps enter data in whichever system is easier, and the migration goal collapses.<\/p>\n\n<h3>Ignoring integration dependencies<\/h3>\n<p>If Dynamics 365 is integrated with your ERP, marketing platform, or customer support system, those integrations don&#8217;t automatically move to Zoho. Map every integration before cutover and plan rebuild time for each. Zoho has native connectors via <a href=\"https:\/\/aaxonix.com\/resources\/zoho-crm-api-webhooks-india\/\" class=\"sp-content-link\">Zoho CRM API and webhooks<\/a> for custom integrations.<\/p>\n\n<figure style=\"margin:2rem 0;text-align:center\"><img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/04\/p8_inline_3.jpg\" alt=\"Software developer analyzing code on a tablet in a modern office workspace.\" style=\"max-width:100%;border-radius:8px;height:auto\" loading=\"lazy\"><figcaption style=\"font-size:.82rem;color:#6b7a8d;margin-top:.4rem\">Photo by Jakub Zerdzicki \u00b7 Pexels<\/figcaption><\/figure>\n<h2>Post-Migration: Configuring Zoho CRM for Your Sales Process<\/h2>\n\n<p>The migration gets data into Zoho. What happens next determines whether the platform actually improves your sales operation. Follow the <a href=\"https:\/\/aaxonix.com\/resources\/zoho-crm-complete-setup-guide\/\" class=\"sp-content-link\">complete zoho crm setup guide<\/a> for full configuration detail, but the highest-priority items post-migration are:<\/p>\n\n<h3>Sales pipeline configuration<\/h3>\n<p>Review your Deals stage names and probability percentages. Dynamics often has legacy stages that don&#8217;t reflect how your team actually sells. Post-migration is the right time to rationalise: aim for 6\u20138 stages maximum, with clear entry and exit criteria for each. Enable Blueprint on your primary pipeline to enforce mandatory fields at each transition.<\/p>\n\n<h3>Role hierarchy and territory setup<\/h3>\n<p>Zoho CRM&#8217;s role hierarchy is simpler to configure than Dynamics&#8217; security model, but it works differently. Map your Dynamics security roles to Zoho&#8217;s role + profile combination. Profiles control what a user can do (module-level permissions); roles control what data they can see (record-level access). Get this right before granting access to reps \u2014 incorrect role setup exposes deals across territories.<\/p>\n\n<h3>SalesSignals and activity tracking<\/h3>\n<p>Zoho CRM&#8217;s SalesSignals gives reps real-time alerts when prospects open emails, visit pricing pages, or submit forms. This requires connecting Zoho SalesIQ (for website tracking) and Zoho Campaigns (for email tracking). Set these up in the first week post-migration \u2014 reps who see the signals adopt the platform faster.<\/p>\n\n<h3>Zia AI configuration<\/h3>\n<p>Zia, Zoho CRM&#8217;s AI layer, starts building prediction models from your deal history once you have a sufficient data set. After import, enable Lead Scoring and Deal Prediction in the Zia configuration panel. These features need at least 3\u20136 months of historical data to generate reliable scores \u2014 but your imported Dynamics data accelerates that timeline.<\/p>\n\n<h2>Realistic Costs and Timeline<\/h2>\n\n<p>Migration cost depends on data volume, customisation complexity, and integration count. Here is a realistic planning benchmark for a 30\u2013100 person mid-market team:<\/p>\n\n<table>\n  <thead>\n    <tr><th>Cost component<\/th><th>DIY estimate<\/th><th>With implementation partner<\/th><\/tr>\n  <\/thead>\n  <tbody>\n    <tr><td>Zoho CRM licensing (40 users, Enterprise)<\/td><td>$1,600\/mo<\/td><td>$1,600\/mo<\/td><\/tr>\n    <tr><td>Data audit and cleanup<\/td><td>Internal time (2\u20133 weeks)<\/td><td>$2,000\u2013$5,000<\/td><\/tr>\n    <tr><td>Schema design and setup<\/td><td>Internal time (1\u20132 weeks)<\/td><td>$3,000\u2013$6,000<\/td><\/tr>\n    <tr><td>Data migration and testing<\/td><td>Internal time (1\u20132 weeks)<\/td><td>$2,000\u2013$4,000<\/td><\/tr>\n    <tr><td>Automation rebuild<\/td><td>Internal time (2\u20134 weeks)<\/td><td>$3,000\u2013$8,000<\/td><\/tr>\n    <tr><td>Training<\/td><td>Internal time (1 week)<\/td><td>$1,500\u2013$3,000<\/td><\/tr>\n    <tr><td>Total project cost (one-time)<\/td><td>Staff time only<\/td><td>$11,500\u2013$26,000<\/td><\/tr>\n    <tr><td>Annual licensing saving vs Dynamics Enterprise<\/td><td colspan=\"2\">$26,400 (40 users)<\/td><\/tr>\n  <\/tbody>\n<\/table>\n\n<p>Most professionally managed migrations for mid-market teams complete in 6\u201310 weeks from kick-off to cutover. DIY migrations typically run 12\u201316 weeks due to learning curve and competing priorities.<\/p>\n\n<div class=\"faq-section\">\n  <h2>Frequently Asked Questions<\/h2>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">How long does a Dynamics 365 to Zoho CRM migration take?<\/p>\n    <p class=\"faq-answer\">A professionally managed migration for a 30\u2013100 person team typically takes 6\u201310 weeks from kick-off to cutover. This includes data audit and cleanup (1\u20132 weeks), Zoho CRM setup and schema design (1\u20132 weeks), test migration and full import (1\u20132 weeks), automation rebuild (1\u20132 weeks), and training and cutover (1 week). DIY migrations take 12\u201316 weeks because of the learning curve and competing internal priorities.<\/p>\n  <\/div>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">Will my Dynamics 365 workflow automations transfer to Zoho CRM?<\/p>\n    <p class=\"faq-answer\">No. Dynamics 365 workflows run on Power Automate, which uses Microsoft&#8217;s proprietary flow format. There is no direct export or import path into Zoho. Each automation must be manually rebuilt in Zoho CRM using Workflow Rules (for simple triggers), Blueprints (for structured stage-based processes), or Macros (for batch actions). Before migration, document every active Power Automate flow with its trigger conditions and actions so nothing is missed in the rebuild.<\/p>\n  <\/div>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">Can I keep Dynamics 365 running while migrating to Zoho CRM?<\/p>\n    <p class=\"faq-answer\">Yes, and it is recommended to run both systems in parallel for a short period during testing. However, parallel operation should be capped at two weeks. Longer than that and reps begin entering data inconsistently across both systems, creating data drift that complicates the final cutover. Set a hard cutover date, export a final snapshot from Dynamics on that day, and restrict Dynamics to read-only access immediately after.<\/p>\n  <\/div>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">What happens to Dynamics 365 data that doesn&#8217;t have a matching Zoho CRM module?<\/p>\n    <p class=\"faq-answer\">Any Dynamics custom entities without a Zoho CRM equivalent must be recreated as Custom Modules before data import. Zoho CRM supports unlimited custom modules with custom fields, layouts, and relationships. Create the module schema first, test the import with a sample, and then run the full import. If the data represents functionality outside CRM scope (like Dynamics Field Service or Marketing), it may require a separate Zoho product such as Zoho Desk or Zoho Campaigns.<\/p>\n  <\/div>\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">Is it worth hiring an implementation partner for a Dynamics 365 to Zoho CRM migration?<\/p>\n    <p class=\"faq-answer\">For teams with more than 25 users or significant Dynamics customisation, yes. An implementation partner reduces migration time by 40\u201350% and eliminates the most common failure modes: bad field mapping, missed automation, and poor adoption. The project cost is typically recovered within the first year from licensing savings. For very simple Dynamics setups with fewer than 15 users and minimal customisation, a guided DIY approach with Zoho&#8217;s own migration resources is viable.<\/p>\n  <\/div>\n<\/div>\n\n<div class=\"aax-cta\">\n  <p>Aaxonix manages end-to-end Dynamics 365 to Zoho CRM migrations for mid-market sales teams, handling data audit, schema design, automation rebuild, and user training in a structured 6\u20138 week engagement. Book a free consultation and get a scoped migration plan with a fixed timeline and cost estimate for your team.<\/p>\n  <a href=\"https:\/\/aaxonix.com\/contact\/\">Book a free consultation<\/a>\n<\/div>\n\n<p>A Dynamics 365 to Zoho CRM migration is not simply a data export-import exercise. The teams that get it right spend equal time on data quality, schema design, and automation rebuild as they do on the actual import. Plan for 6\u201310 weeks, take the test migration seriously, and set a hard cutover date. The platform is only as good as the data and workflows you put into it \u2014 and both of those are decisions made before the first record is transferred.<\/p>\n\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Practical guide to migrating from Microsoft Dynamics 365 to Zoho CRM. Covers data mapping, module equivalents, common pitfalls, and go-live checklist for mid-market teams.<\/p>\n","protected":false},"author":1,"featured_media":2410,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[668,637,666,667,638],"class_list":["post-2414","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-crm-data-migration","tag-crm-migration","tag-dynamics-365-to-zoho-crm","tag-microsoft-dynamics-migration","tag-zoho-crm-setup"],"_links":{"self":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/2414","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=2414"}],"version-history":[{"count":1,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/2414\/revisions"}],"predecessor-version":[{"id":2415,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/2414\/revisions\/2415"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/media\/2410"}],"wp:attachment":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/media?parent=2414"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/categories?post=2414"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/tags?post=2414"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}