Migrate from Panacea to Zoho CRM

Panacea vendors with company-level data map to Zoho Accounts. Panacea vendor contacts map to Zoho Contacts linked to the parent Account via Account Name lookup. If a Panacea vendor has no company name, it creates a Zoho Account named from the vendor contact name and the Contact links to it.

Panacea job records map directly to Zoho Deals. Job name becomes Deal Name. Job status (Quote, In Progress, Completed, Invoiced) maps to Zoho Deal Stage via value-by-value mapping. Amount from the Panacea job price field maps to Deal Amount in Zoho.

Panacea's proof-upload and supplier communication logs map to Zoho Tasks (for actionable items) and Notes (for reference records). Task Subject carries the interaction type; Task Status and Due Date map from Panacea interaction timestamp and follow-up flag. This ensures all interactions are tracked and visible in Zoho.

Panacea quote line items merge into Zoho Products for pricing catalogue alignment. The parent quote with pricing, validity date, and terms maps to Zoho Quotes, linked to the Deal. If Panacea tracks multiple quotes per job, each quote becomes a separate Zoho Quote record under the same Deal. During migration, FlitStack AI also maps any custom pricing tiers to Zoho Product Attributes, preserving discount structures and volume pricing rules.

Panacea POs map to Zoho Purchase Orders module. PO number, supplier, line items, and total amount transfer directly. Zoho Purchase Orders are available from the Professional tier upward.

Panacea custom fields on vendor and job records — such as supplier tier, proof-format preference, or job-type classification — are recreated as Zoho custom fields. Field types are matched (text → varchar, number → integer, currency → currency, date → date). Custom fields are registered in Zoho before migration data loads.

Panacea proof PDFs, artwork files, and supplier documents attached to job records are re-uploaded to Zoho Files and attached to the corresponding Deal or Account record. Files over 25 MB are chunked or linked via URL reference where the source file is hosted externally.

Panacea workflow sequences for supplier proof approval, follow-up reminders, and quote-to-PO automation do not migrate. FlitStack AI exports Panacea workflow definitions as a structured reference document. Your Zoho admin uses that reference to rebuild equivalent logic in Zoho Blueprint, available from Zoho Professional tier.

Panacea report configurations — such as supplier cost variance, job profitability, and lead-to-close by channel — do not transfer. The underlying transactional data (Deals, Tasks, Products) migrates fully. Zoho Custom Reports are rebuilt from the migrated data; we deliver a report specification sheet listing each Panacea report and its Zoho equivalent.

Panacea user accounts are resolved by email match against Zoho Users. Active Panacea users with email addresses get matched to existing Zoho users. Users without Zoho accounts are flagged before migration; your team either creates Zoho user licenses or assigns records to a fallback owner.

Panacea's internal record ID is stored as Source_System_ID__c on each migrated Zoho record. This field enables delta-run de-duplication, rollback targeting, and traceability back to the Panacea source system. It also facilitates data validation after migration, allowing you to cross-check record counts and identify any mapping discrepancies in downstream reports and integrations.

Zoho's CreatedDate and ModifiedDate are set at migration time. Panacea's original create and last-modified timestamps are preserved in custom datetime fields (Original_Create_Date__c and Original_Modify_Date__c) on each record for reporting continuity. These custom fields enable historical trend analysis, support audit requirements, and allow you to rebuild time-based reports such as monthly create rates or change frequency after the migration.