Migrate from Pawa to Freshsales

Pawa Contact records (name, phone, email, custom fields) map to Freshsales Contact. We use email as the dedupe key during import. Custom fields are discovered via API at scoping time, and the corresponding Freshsales custom fields are created before import begins. Tags stored as flat string arrays on Pawa Contacts migrate to Freshsales Contact tags. If Pawa Contacts are linked to Companies, we create the Account record first so that AccountId is resolved at Contact insert time.

Pawa Company records (name, address, linked contacts) map to Freshsales Account. The Company-to-Contact relationship is preserved by matching on company ID from the exported record set. Address fields (street, city, state, postal code, country) map to Freshsales Account address fields. If Pawa stores a website on Company, it becomes the Account Website field.

Pawa Deal records (value, stage, linked contacts) map to Freshsales Deal. Deal-to-Contact associations are preserved by resolving the Pawa contact ID to the corresponding Freshsales Contact record before writing. Stage names from Pawa are mapped to Freshsales Deal stages using a stage mapping table created during scoping. If Pawa stores a deal owner, that owner is resolved via User mapping by email match.

Pawa custom fields on Contacts and Companies are discovered via API at scoping time. We create the corresponding Freshsales custom fields (Contact-level or Account-level) in the destination account before any records are written. Field type mapping follows Freshsales field type conventions: text fields map to Text, numeric fields to Number, date fields to Date, and picklist-like fields to Picklist. The customer reviews and approves the custom field map during the scoping phase.

Pawa User records (name, email, role) are exported and mapped to Freshsales User records. We resolve owners by email match. Inactive Pawa users are flagged and excluded unless the customer requests otherwise. Any Pawa Owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Pawa tags stored as flat string arrays on records map to Freshsales Contact tags and Account tags. We note that Freshsales handles tag inheritance (across Contact, Account, and Deal) differently from Pawa's tagging model. The customer chooses the tag migration strategy during scoping.

Where Pawa supports pipeline stages on Deals, we map stage names and preserve order using a stage mapping table applied at import. If Freshsales uses a different stage model, we create the corresponding stages in Freshsales before migration begins. Stage probability percentages are mapped from Pawa to Freshsales Deal stage probability fields.

Pawa's API does not expose file attachments in a publicly documented endpoint. We do not migrate attachments. Before migration, we list all attachment-bearing records so the customer can manually download and re-upload them post-migration to Freshsales. We document this in the migration plan and exclude attachments from the record count used to scope migration timelines and pricing.