Migrate from APTANIA CRM to Freshsales

APTANIA Contact records map to Freshsales Contact. We extract all standard fields (name, email, phone, lifecycle stage) and the B2C/B2B flag, which we preserve as a custom property (aptania_b2c_b2b__c) in Freshsales since Freshsales uses its own lifecycle stage model. Email address is the dedupe key for contact import. Records that lack an email address are flagged in the scoping report and imported with a custom no_email__c flag for manual review.

APTANIA Company records map to Freshsales Account. The HubSpot-style company name becomes the Account Name field. Company-contact linkage is preserved during import by matching on company name before inserting contacts, then resolving the aptania_company_id to the Freshsales Account ID for the Contact.AccountId lookup. Accounts are imported before contacts to satisfy the foreign key dependency.

APTANIA Deal records map to Freshsales Deal. We extract monetary value, close date, stage name, and associated pipeline from the exported deal file. Stage names from APTANIA are mapped to Freshsales Deal stages during the transform step. Deals are imported after Accounts and Contacts so that AccountId and ContactIds are already resolved.

APTANIA pipeline and stage structure is inferred from the exported deal records since APTANIA's export schema does not expose pipeline metadata directly. We reconstruct pipeline names and stage order from the dealstage values present in the export and configure Freshsales Deal Pipelines with matching stage names before deal import. The customer reviews and approves the reconstructed pipeline structure during scoping.

APTANIA activity logs (emails, calls, notes) exist in the export but the schema is not publicly documented and field names vary across export runs. We extract what is available, map each activity to Freshsales Activity records, and flag any unstructurable fields in the data map for manual review. Activity timestamp is preserved on Freshsales Activity.Date.

APTANIA user records are exported and matched to Freshsales users by email address. Any APTANIA user without a corresponding Freshsales user is held in a reconciliation queue for the customer's admin to provision before import resumes. Role and permission differences are documented for manual review post-migration since APTANIA's permission model does not map directly to Freshsales roles.

APTANIA custom field values and names are extracted from the export and recreated in Freshsales as custom fields on the appropriate object. Field types are inferred from the data (text fields for string values, numeric for integers, date for timestamps). Any custom field that cannot be cleanly typed from the export data is flagged in the mapping document for the customer to review and resolve in Freshsales admin settings before import.

APTANIA email automation rules do not export. We do not migrate automation logic as code. During scoping, we request screenshot documentation of all active automation rules from the customer and deliver a written automation inventory with each rule's trigger, conditions, and actions described in Freshsales Workflow equivalent terminology. The customer's admin rebuilds the rules in Freshsales Workflows post-migration.