Migrate from Notifi to Zoho CRM

Notifi Customers map directly to Zoho CRM Accounts. Company name, billing address, and phone carry over as Account fields. If the Notifi Customer has no company name (sole-proprietor), the Account name defaults to the customer's full name and a flag field is set to identify it as an individual.

Notifi Contact records map 1:1 to Zoho CRM Contacts. The primary contact on a Customer becomes the Account's primary Contact. Multiple contacts under one Customer are imported as separate Contact records linked to the same Account via Account Name lookup.

Notifi Contacts that have never been converted to a Customer (no active job or estimate) can optionally be routed to Zoho Leads instead of Contacts. FlitStack applies a configurable rule — contacts with zero associated Jobs or Estimates route to Lead; all others route to Contact.

Notifi Estimates map to Zoho Quotes at Professional tier or above. Line items become Quote Items with product lookup. If Zoho Quotes are unavailable in the account's plan, Estimates are stored as custom multi-line fields on the associated Deal and exported as a PDF attachment. Estimate status (Draft, Sent, Accepted, Declined) maps to a custom pick-list field.

Notifi Jobs have no native Zoho equivalent. FlitStack creates a Zoho CRM Custom Module named 'Job' with fields for job name, service type, scheduled date, technician assigned, job status, and GPS coordinates. The custom module is linked to the parent Account via a lookup relationship. Blueprint and workflow rules can then drive stage progression in the custom module.

Job statuses (Scheduled, In Progress, On Hold, Completed, Cancelled) map to a custom pick-list field on the Job module. Values are translated 1:1. Completed jobs include the completion timestamp stored as a custom datetime field for reporting continuity. This mapping preserves job lifecycle history and allows Zoho workflows to trigger based on status changes once Blueprint is configured.

Zoho CRM has no native invoice object at Standard/Professional tiers. Notifi Invoices are exported as PDFs and attached to the corresponding Account record (for customer-level invoices) or to the Deal representing the job. This preserves the financial record for reference without requiring Zoho Books integration.

Notifi user records are matched to Zoho CRM users by email address. A pre-migration report flags any Notifi user with no matching Zoho user — your team either invites that user to Zoho before migration or assigns their records to a designated fallback owner.

Notifi file attachments (photos, signed documents, job images) are downloaded and re-uploaded to the corresponding Zoho record. Zoho's 25 MB per-file limit applies; attachments exceeding this are flagged and linked via URL to a cloud storage reference field. This approach maintains document context within Zoho while handling size constraints gracefully. All attachment associations are preserved during migration, linking each file to its parent Customer, Contact, or Job record.

Notifi communication activities (calls logged, SMS sent, emails) are imported as Zoho Tasks with Type = Call, Email, or Other. The original timestamp and duration (for calls) are preserved in task description fields. Communication subject lines map to Task Subject.

Notifi GPS coordinates attached to jobs (from dispatch and routing) are stored as two custom decimal fields — Job_Latitude__c and Job_Longitude__c — on the Job module. This data is for reference only; Zoho CRM does not have native map visualization for custom coordinates.

Notifi custom properties on Customers, Contacts, Jobs, or Estimates that have no Zoho standard-field equivalent are migrated as custom fields. Data type is inferred from source — text, number, date, or pick-list — and recreated in the matching Zoho module before records are inserted.