Migrate from APTANIA CRM to Zoho CRM

APTANIA Contact records map to Zoho CRM Lead for unqualified prospects and Contact for qualified buyers. We use APTANIA's lifecycle stage or B2C-B2B flag to determine the split: B2C contacts and contacts without a linked Company record migrate to Zoho Lead; B2B contacts with a linked Company record migrate to Zoho Contact and are associated with the corresponding Zoho Account. The original APTANIA contact ID is preserved in a custom field aptania_contact_id__c for audit and cross-reference. Email, phone, address, and custom property fields transfer as typed fields or custom fields in Zoho.

APTANIA Company records map directly to Zoho CRM Account. Company name becomes the Account Name; website URL, industry, and employee count map to corresponding Zoho fields. We extract the Company record first, then resolve the Account ID before importing linked Contact records to satisfy the Contact-to-Account lookup relationship. APTANIA does not expose all custom property metadata in export, so any custom fields on Company are created in Zoho as custom fields before import.

APTANIA Deals map to Zoho CRM Deals. Deal name, monetary value, stage, close date, and associated Contact and Company references transfer. We resolve the Contact or Account lookup ID from the earlier import phases before inserting Deals. APTANIA's pipeline and stage structure is inferred from the exported deal records since the exact stage-object relationship is undocumented; we create Zoho pipeline stages that match the distinct stage values present in the exported data.

APTANIA deal stages map to Zoho CRM Deal Stage values within a Zoho pipeline. We extract all distinct stage names from the exported deal records, create corresponding stages in Zoho with matching or closest-fit labels, and set stage probabilities. Stage ordering in Zoho matches the sequence from APTANIA. If APTANIA used a single pipeline model, we create one Zoho pipeline; if multi-pipeline structure is inferred from the data, we create multiple Zoho pipelines.

APTANIA activity logs (emails, calls, notes) export as available and map to Zoho CRM Task or Event records. Emails map to Task with TaskSubtype=Email and activity body preserved; call logs map to Task with TaskSubtype=Call and duration field; notes map to Event or Task depending on date presence. APTANIA's undocumented activity schema means we export what is available and flag any fields that cannot be mapped to standard Zoho fields. Parent record resolution (Contact or Account) is performed by email or name matching against the already-imported records.

APTANIA user records export and map to Zoho CRM User by email address. User full name, email, and role flag transfer. APTANIA role and permission structures differ from Zoho's role hierarchy, so we flag permission differences for the customer's admin to configure in Zoho post-migration. Any APTANIA user without a matching Zoho User is placed in a reconciliation queue for manual provisioning.

APTANIA custom properties on Contact records are exported as available field-value pairs. We create matching custom fields in Zoho CRM before import, using the closest Zoho field type: text fields for string values, picklist fields for enumerated values, date fields for date values. APTANIA does not expose all custom property metadata in export, so field labels are inferred from exported column headers and values. Any custom properties without a clear type are created as text fields and flagged for the customer to review.

APTANIA custom properties on Company records map to custom fields on Zoho CRM Account. Same field-type mapping logic applies: text for strings, picklist for enumerated, date for dates. The Account custom fields are created in Zoho before the Account import phase begins. We document all created custom fields in the field mapping deliverable so the customer has a complete reference.

APTANIA email automation rules (trigger-based email sends tied to customer activity or inactivity) cannot be exported. The rules engine is not accessible via APTANIA's export tools. We do not migrate automation logic as code. We request that the customer provides screenshots of all active automation rules before the migration data-pull phase, and we deliver a written inventory of every rule with its trigger, conditions, actions, and recommended Zoho Workflow equivalent. The customer's admin rebuilds the rules in Zoho Workflows post-migration.

APTANIA's web traffic monitoring and channel attribution data (referrer, UTM parameters, landing page history) does not export to standard file formats. We do not migrate web tracking events. We flag the gap in the data map and recommend that the customer configures Zoho Web豪Analytics or a third-party tracking integration (Google Analytics, Zoho Analytics) before go-live to preserve future attribution data. Historical attribution data in APTANIA is lost at migration cutover.