Migrate from ServeManager to Zoho CRM

ServeManager Job maps directly to Zoho Deal as the primary work record. Both represent a discrete unit of work with a due date, assigned owner, and status. Zoho Deal Stage maps from ServeManager Job status. Zoho requires custom fields (Service_Type__c, Client_Reference__c, Case_Number__c, Stripe_Fee__c) to capture ServeManager's full job schema since Zoho has no native Service Type or Client Reference property.

ServeManager Attempt maps directly to Zoho Task — each record represents a discrete field action tied to a parent Job. Attempt date and time map to Zoho Task Due Date and a custom Time field. GPS latitude and longitude are stored as Zoho custom number fields (Attempt_Latitude__c, Attempt_Longitude__c) since Zoho Tasks have no native GPS coordinate field. Attempt type (personal service, substituted service, certified mail) maps to Zoho Task Stage, and attempt outcome (served, not served, refused) maps to Zoho Task Status.

ServeManager Company (law firms and clients) maps directly to Zoho Account. Both are organization-level records containing business name, address, phone, domain, and industry. Parent-child company hierarchies in ServeManager map to Zoho Account Parent Account relationships. Companies are migrated before Jobs so that Account lookups resolve correctly on Deal creation.

ServeManager Contact records split based on role: law-firm billing contacts and service recipients map to Zoho Contact under the associated Account; individual process servers or ad-hoc contacts without a firm association route to Zoho Lead. Contact name, email, phone, and address map directly. The full address string is stored in a custom field (SM_Full_Address__c) to preserve formatting since Zoho Contact address fields structure differently than ServeManager's combined address property.

ServeManager Invoice maps to a Zoho Custom Module (SM_Invoices__c) rather than Zoho's native Invoices module, because Zoho's native module requires Products module setup and line-item product records. The custom module captures Invoice Number, Invoice Date, Due Date, Amount, Balance Due, and Stripe Fee as custom fields. Line item descriptions and fees are stored as a text subform (Line_Items__c) in the custom module to preserve item-level detail.

ServeManager Payment maps to a Zoho Custom Module (SM_Payments__c) to preserve the payment record independently of Zoho's native accounting objects. The module includes Amount, Payment Date, Payment Method, Reference Number, and Payment Status as custom fields. A lookup field links each Payment to its parent SM_Invoices__c record, preserving the invoice-to-payment relationship.

ServeManager Server Payables (amounts owed to process servers) map to a Zoho Custom Module (SM_Server_Payables__c). This object has no native equivalent in Zoho CRM — Zoho Books handles payables, but Books is a separate product. The custom module stores Server Name, Amount Owed, Payable Date, Payment Status, and a link to the original Job (Deal) so teams can reconcile payables against served jobs.

ServeManager process servers are stored as name strings on Job records, not as user objects. Zoho CRM Deal_Owner is a lookup to a Zoho User record. FlitStack AI resolves ServeManager's process-server name strings by email match against Zoho Users — if a matching Zoho User exists, the Deal_Owner field populates automatically. Process servers without a Zoho User account are flagged before migration for your team to create accounts or assign a fallback owner.

ServeManager job notes and uploaded attachments (affidavits, proof of service documents) map to Zoho Notes and Attachments on the Deal record. Document file types and original filenames are preserved. Zoho's 25MB per-file attachment limit applies — files exceeding this are flagged for manual delivery. Affidavit PDFs attached to Jobs in ServeManager re-upload to Zoho Files attached to the corresponding Deal.

ServeManager's user-defined custom fields (jurisdiction codes, court identifiers, affidavit type, client-specific flags) require explicit Zoho custom field creation before migration. FlitStack inventories all ServeManager custom fields during the discovery phase, creates matching Zoho custom fields in the appropriate modules, and applies the same data type (picklist, text, number, date, checkbox) before any records load. Fields not pre-created in Zoho are silently skipped by the import wizard.