Migrate from Maple CRM to Zoho CRM

Maple CRM Leads map directly to Zoho CRM Leads. Source, status, assigned executive, follow-up dates, and custom intake data transfer to corresponding Zoho custom fields. We preserve any immigration-specific intake properties (visa category, source country, inquiry date) as custom fields in Zoho that the customer's admin maps to picklists or date fields during schema setup. Lead conversion in Zoho creates a Contact and optionally an Account at the same time.

Maple CRM Clients hold contact details, address, nationality, passport data, and links to multiple open Cases. We treat Clients as the parent entity and migrate them before Cases to preserve foreign-key resolution. Depending on the customer's Zoho data model preference, Clients map either to Zoho Contact (for a contact-centric model) or to Account with the primary Contact linked (for an account-centric model). The customer chooses during scoping. Passport number, nationality, and visa eligibility flags migrate as custom fields on the target object.

Maple CRM Cases are the core immigration vertical object linking to a Client and tracking process stages (Application, Review, Submission, Approval, Denial/Appeal). We pre-create a custom Zoho module named 'Immigration Case' with custom picklist values matching the exact Maple CRM stage names. Each Case record migrates with its linked Client as a lookup, stage as the picklist, related documents as attachments, and historical timestamps (created date, last modified, case open date) preserved as custom date fields.

Maple CRM Documents attach to Cases or Clients and include intake forms, passports, proof of funds, and visa applications. File attachments migrate as binary blobs via Zoho's file upload API. Document type, upload date, and related entity metadata migrate as custom fields on a Document custom module in Zoho that links back to the parent Case or Contact. We batch file uploads in chunks of 20 to respect Zoho's attachment API rate limits.

Maple CRM Quotations (created via the Quotation Builder linked to Deals or Orders) map to Zoho CRM Quotes. Quotation line items, pricing, tax, and status migrate to Zoho QuoteLineItems. The Quote PDF itself is not migrated; only the underlying data record transfers. We resolve the Contact or Account lookup on Quote using the Client-to-Contact mapping from the scoping phase.

Maple CRM Invoice records (including line items, amounts, payment terms, and outstanding balance) migrate to Zoho Invoice. Historical paid invoices transfer with status preserved. If the customer uses Zoho Books alongside Zoho CRM, we configure the CRM-to-Books sync for invoice data continuity. If not, Invoices remain in Zoho CRM's Quotes or Invoices module (available on Standard and above). Payment status and instalment schedule migrate as custom fields if the Zoho edition lacks instalment tracking.

Maple CRM Contracts and Annual Maintenance Contracts (AMCs) link to Clients and track service terms, renewal dates, and pricing. We map these to Zoho CRM's native Contracts module (available on Standard and above) or to a custom Contracts module if the customer needs additional fields. Renewal date migrates as Contract End Date; pricing migrates to Total Contract Value custom field.

Maple CRM Support Request records (with status, priority, assignee, and timestamps) migrate to Zoho CRM Cases. SLA TAT tracking and escalation rules are platform configurations not accessible via API and do not migrate. We document the existing SLA rules in a written inventory for the customer's admin to rebuild as Zoho Workflow Rules with time-based triggers or as Zoho Desk SLA policies if Service Cloud is in scope.

Maple CRM User accounts with role-based access control export as records with role and team assignments. We resolve users by email match against the Zoho destination's User table. Any Maple CRM user without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision. Migration cannot proceed past User resolution because OwnerId references are required on most standard objects.

Maple CRM Agreement template definitions with macro placeholders are not fully exposed via API and do not migrate. Generated agreement records (the filled-out documents) migrate as Zoho Notes linked to the associated Client or Case record, with the agreement body stored as Note content. The customer's admin rebuilds the template definitions using Zoho Writer with merge fields post-migration.

Maple CRM Service Schedules track appointment slots and staff assignments for field service visits. We map Service Schedules to Zoho Events with custom fields for service type, location, and assigned staff. Event date and time migrate to Zoho Event Start DateTime and End DateTime; attendee maps to the related Client Contact.

Maple CRM Workflow Automations (email triggers, stage-change notifications, follow-up reminders) are stored as platform configuration and are not accessible via any documented API endpoint. We do not migrate automation definitions. We deliver a written inventory of every active Maple CRM automation with its trigger, conditions, actions, and recommended Zoho Workflow Rule equivalent. The customer's admin rebuilds each one in Zoho under Settings > Workflows. Complex rule sets may require one to two hours per workflow to rebuild.