Migrate from tab32 to Zoho CRM

tab32's Open Data Warehousing export is not a standard CRM API — schema discovery takes time before mapping

tab32 exposes data through its Open Data Warehousing API and CSV export, not through a conventional CRM REST or SOAP API. The export schema is dental-domain-specific with object names like Patient, Provider, ToothChart, and PerioChart that have no direct equivalents in Zoho CRM. FlitStack AI performs schema discovery on the tab32 warehouse before generating the Zoho mapping plan. Teams migrating without this step risk mis-mapping clinical modules to Zoho standard objects that cannot store the data correctly (for example, mapping periodontal probing depths to a text field that truncates at 255 characters). The schema audit typically adds one to two weeks to the discovery phase and must be completed before any data moves.

Zoho CRM's credit-based API rate limits vary by edition and can throttle bulk imports mid-run

Zoho CRM's V2 API uses a credit deduction model: Professional tier allows approximately 10,000 credits/day (base) plus 500 per user license, while Enterprise reaches 1,000,000 credits/day at scale. A bulk patient migration with 50,000 records consuming one credit per record can exhaust daily allocations if not batched and spaced. Additionally, the Lead Convert operation deducts 5 credits per call — significant if automated conversion is part of the migration plan. FlitStack AI calculates credit consumption during planning, paces imports within Zoho's rolling 24-hour window, and uses Zoho's Bulk Read API (which requires 50 credits per initialize) strategically to avoid mid-run throttling that would leave records in an incomplete state.

Multi-location provider assignments require a custom field strategy since Zoho Users have a single Owner field

tab32 supports one provider record being assigned to multiple office locations simultaneously — a hygienist working at three practice locations is one provider record with three location links. Zoho CRM User records represent providers, but each CRM record (Contact, Event, Quote) has a single Owner field. A provider assigned to four offices cannot populate four Owner fields on a single record. FlitStack AI maps the primary office provider to the Zoho Owner field and stores secondary office assignments in a custom Provider_Office_List__c multiselect picklist on the Contact. This preserves the full multi-location provider context without data loss, but it requires Zoho custom field setup before the migration runs and means secondary-location queries require filtered list views rather than native owner-based filtering.

tab32 workflows and automation rules have no Zoho equivalent and must be rebuilt as Blueprint or workflow rules

tab32 automations include appointment reminder sequences, recare workflows triggered by last-visit dates, e-prescription routing rules, and custom clinical alerts. These are built within the dental PMS and do not export as portable configuration files. Zoho CRM's equivalent automation engine consists of Blueprint (for process enforcement) and workflow rules (for field updates and email alerts) — the underlying logic must be recreated. FlitStack AI exports tab32 workflow definitions as structured rebuild reference documents that your Zoho admin can use to configure equivalent Blueprint stages and workflow rules in Zoho. Recare workflows are particularly complex to rebuild because Zoho lacks a native 'days since last appointment' trigger, requiring a combination of scheduled workflow checks and custom date fields.

Zoho CRM CSV import file size limits vary by edition — large imaging data and attachments may require chunking

Zoho CRM's import file size limits are edition-dependent: Standard caps CSV imports at 10 MB, Professional at 10 MB, Enterprise at 25 MB, and Ultimate at 25 MB. tab32 practices with large attachment volumes (panoramic X-rays, intraoral photos per patient) face a direct constraint: files exceeding the Zoho edition limit cannot be imported via the standard CSV mechanism and must be chunked by patient batch or uploaded separately as Zoho Attachments. FlitStack AI pre-assesses total attachment volume during the audit phase and sequences large file uploads separately from the record migration to avoid import failures that could corrupt the patient record linkage.