Migrate from Pawa to Zoho CRM

Pawa Contact records (name, phone, email, custom fields) map to Zoho CRM Contacts. If the customer uses Zoho Leads as a separate pre-conversion stage, we split at scoping based on a lead qualification flag in Pawa. Custom fields on Contacts are discovered via live API at scoping time; we build an explicit field map before import and flag any Pawa field types with no direct Zoho equivalent for customer review.

Pawa Company records (name, address, linked contacts) map directly to Zoho CRM Accounts. The Company-to-Contact relationship is preserved by resolving the Pawa company ID against the Account record created during the import phase before Contact inserts begin. Account is created first so that Account lookup is satisfied at the moment of Contact write.

Pawa Deal records (value, stage, linked contacts) map to Zoho CRM Deals. The deal-to-contact association is preserved by cross-referencing IDs from the exported record set. If Pawa uses pipeline stages that differ from Zoho's default Deal stages, we create a stage mapping table during scoping and apply it at import. Stage probability percentages map to Zoho's probability field where supported.

Pawa custom fields on Contacts and Companies are discovered via live API at scoping time. We map each Pawa field to a typed Zoho CRM custom field (Text, Number, Date, Picklist, etc.) and create the destination fields in the customer's Zoho CRM account before importing any records. Custom fields are not available in Zoho CRM Free edition; we confirm the destination edition during scoping and flag any upgrade requirement before work begins.

Pawa stores tags as flat string arrays on records. Tags migrate as multi-select picklist fields or as standard label fields in Zoho CRM. Zoho handles tag inheritance differently depending on whether the customer uses Tags as a standalone feature or as part of a Zoho CRM Plus workflow. The customer chooses the tag strategy during scoping.

Pawa User records (name, email, role) map to Zoho CRM Users. We resolve owners by email match against the Zoho CRM User table. Any Pawa User without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Pawa users are flagged and excluded unless the customer requests otherwise.

Pawa's API does not expose file attachments in a documented endpoint. We do not migrate attachments as part of the migration scope. Before migration begins, we enumerate all attachment-bearing records in the source account and deliver a list so the customer can manually download and re-upload files to Zoho CRM post-migration. Attachment-bearing records are excluded from the record count used to scope migration timelines and pricing.

Where Pawa supports pipeline stages on Deals, we map each stage name and preserve the stage order. If Zoho's default stages do not match the customer's Pawa stage model, we configure a custom sales process in Zoho CRM with stage names, probabilities, and layout assignments before Deal import begins.

If the customer uses Pawa's field record capabilities beyond standard Contacts and Companies, we assess whether Zoho CRM's Custom Modules feature can accommodate the data model. We create the destination custom module in Zoho, define all fields and lookup relationships, then import records in dependency order. Custom module creation is scoped separately from standard object migration.

Pawa workflows and automations do not migrate to Zoho CRM. The automation models differ structurally and are not transferable as code. We deliver a written inventory of every active Pawa automation (trigger, conditions, actions) with a recommended Zoho Blueprint or workflow equivalent for the customer's admin to rebuild post-migration.