Migrate from SuiteDash to Zoho CRM

SuiteDash Contact records map directly to Zoho CRM Contacts. Standard properties (name, email, phone, address) use Zoho's corresponding field names. Contact-level custom fields migrate as Zoho CRM custom fields scoped to the Contacts module. Tags on SuiteDash Contacts migrate as a comma-separated Multi-Select Picklist in Zoho or as Zoho Tags linked via the Tagging API. We run GET /contact/list on SuiteDash and map each Contact-level custom field before inserting into Zoho via the Contacts API.

SuiteDash Company records with Public custom fields map to Zoho CRM Accounts. The company name becomes the Account Name, domain becomes the Website field, and Public custom fields migrate as Zoho custom fields on Accounts. Public visibility means the data is accessible to all users with Account-level read access in Zoho. We use the Company name as the dedupe key during Zoho insert to prevent duplicate Account creation.

SuiteDash Company Private custom fields are visible only to the Primary Contact and are not exposed via SuiteDash Dynamic Data Placeholders. We identify all Private-scoped Company fields during scoping, confirm with the customer which should map to restricted Zoho custom fields (with field-level security enforcing visibility), and flag any that have no equivalent Zoho field type for manual review. Private data that cannot be placed in an equivalent visibility bucket is migrated as encrypted or restricted custom fields or stored as a private Note attached to the Account.

SuiteDash Deals map to Zoho CRM Deals. Deal name, amount, closing date, probability, and stage migrate directly. The SuiteDash pipeline assignment determines the Zoho Deal Stage we configure before migration. We preserve Closed-Won and Closed-Lost reasons from SuiteDash custom properties in Zoho custom fields on Deals. Owner resolution is handled by matching SuiteDash Staff email to Zoho User email during the Owner reconciliation phase.

Each SuiteDash Deal pipeline maps to a Zoho Deal Stage or a set of stage values. We configure Zoho Deal stages before migration by creating stage names matching SuiteDash's pipeline stage labels, set probability percentages from SuiteDash (with Zoho's integer rounding), and assign stage order to match the SuiteDash pipeline sequence. If the customer uses multiple Deal pipelines in SuiteDash, we configure Zoho Deal subforms or separate Zoho modules per pipeline.

SuiteDash Support Tickets map to Zoho CRM Cases (or Zoho Desk if the customer licenses it). Ticket subject, description, status, priority, and assignee migrate. Thread conversations migrate as Zoho Case Thread entries or as Notes attached to the Case. Status values from SuiteDash are mapped to Zoho Case Status (Open, Pending, Closed, On Hold) with the nearest equivalent. Ticket-level custom fields migrate as Zoho custom fields on Cases.

SuiteDash Projects carry custom fields and task hierarchies that do not have a direct CRM-native equivalent in Zoho CRM. We export Projects with their associated task lists and custom field values. If the customer has Zoho Projects licensed, we map Projects to Zoho Projects tasks and milestones linked to the Account or Deal via a lookup. If Zoho Projects is not available, we create a custom module in Zoho CRM named Projects, migrate the project records as custom module entries with their custom fields, and attach task lists as related Notes or as a separate task module. The customer chooses the approach during scoping.

SuiteDash Invoice records (line items, payment status, Invoice Custom Fields) migrate to Zoho Invoice. Invoice Custom Fields are a distinct field type in SuiteDash separate from CRM Custom Fields and must be discovered via the Invoice API endpoints, not via GET /contact/meta. We run a separate Invoice-specific field discovery during scoping to capture Invoice Custom Fields before mapping. Historical paid invoices migrate as closed Invoice records. Active or pending invoices require additional configuration to preserve payment workflow status in Zoho Invoice.

SuiteDash Appointments (scheduling data, associated Contacts, status) map to Zoho CRM Events. The appointment subject, start time, end time, location, and attendee Contact references migrate. We resolve the SuiteDash Contact reference to the Zoho Contact ID at migration time and link the Event via the Related To field. Booking page configurations and bidirectional calendar sync settings do not port; we flag these for manual reconfiguration in Zoho Calendar or Zoho Bookings if licensed.

SuiteDash Staff records (name, email, role, staff-level custom fields) map to Zoho CRM Users. Owner and assignee relationships on Deals, Projects, and Tickets are migrated as references to the resolved Zoho User record. We match by email address during the Owner reconciliation phase. Any SuiteDash Staff member without a matching Zoho User is held in the reconciliation queue for the customer's admin to provision the Zoho User before record import resumes. Staff-level custom fields migrate as Zoho User custom fields where supported.

Organization-level custom fields and white-label settings in SuiteDash have no direct equivalent in Zoho CRM's migration API. We document the Organization Settings configuration (white-label domains, logo, color scheme, role definitions) in a setup audit report for the customer's admin to reconfigure manually in Zoho Setup. Role definitions map to Zoho Roles and Profiles, but white-label portal configurations require Zoho Creator or Zoho Sites rather than Zoho CRM native settings.

SuiteDash custom fields exist at six scopes: Contact, Company Public, Company Private, Organization, Staff, Work Request, Project, and Support. We run GET /contact/meta to capture the full CRM field schema, then run a separate Invoice-specific discovery to capture Invoice Custom Fields. Each scope maps to a Zoho module: Contact fields to Contacts, Company Public fields to Accounts (Public visibility), Company Private fields to Accounts (restricted visibility via field-level security), Staff fields to User custom fields, Project fields to the custom Projects module, and Support fields to Cases. Work Request fields map to a custom Zoho module if no equivalent Zoho object exists.