Migrate from APTANIA CRM to HighLevel

APTANIA Contact records map directly to GoHighLevel Contact. Standard fields (name, email, phone, address) transfer as-is. The APTANIA B2C/B2B flag is preserved as a custom property (contact_type__c) in GoHighLevel Custom Fields. We create the custom field in GoHighLevel before migration and map the flag value to a picklist. Lifecycle stage data stored in APTANIA custom fields migrates to GoHighLevel Lifecycle Stage if present, or to a text custom field if the source schema does not use GoHighLevel-native values.

APTANIA Company records map to GoHighLevel Company with the domain, name, address, and industry fields preserved. The Company record is created before Contact import so that the contact-to-company relationship is resolved at insert time. We use company name as the dedupe key. If APTANIA stores multiple contacts per company, we resolve the primary contact flag and attach secondary contacts via the GoHighLevel Contact-Company relationship.

APTANIA Deal records map to GoHighLevel Opportunities. The monetary value, close date, stage name, and associated contact and company references transfer. We map APTANIA stage names to GoHighLevel pipeline stage values during the transform phase, creating any missing stages in GoHighLevel Pipelines before the Deal import batch runs. Deal-owner references resolve by email match to GoHighLevel User records.

APTANIA pipeline structures (stages and stage order) are inferred from exported Deal records during scoping. We recreate the pipeline in GoHighLevel with matching stage names and probabilities. If APTANIA supports multiple pipelines, we create corresponding GoHighLevel Pipelines and assign Deal records to the correct pipeline via GoHighLevel's pipeline assignment field. Stage status values (won, lost, open) map to GoHighLevel Opportunity status equivalents.

APTANIA Activity logs (calls, notes, manual tasks) map to GoHighLevel Tasks. Email activities stored in APTANIA's activity log migrate as Task records with the body preserved and the activity type flagged in a custom field. APTANIA's undocumented activity schema requires a pre-migration schema audit; we extract all available fields and map what is structurally consistent, flagging any unstructured activity data for manual review. Activity timestamps are preserved using GoHighLevel's due date and reminder fields.

APTANIA custom fields migrate to GoHighLevel Custom Fields, which we provision in the destination account before data import. Field types map by data type: text to text, number to number, date to date, and multi-select checkbox arrays to GoHighLevel multi-select fields. We document the complete custom field schema in a field map delivered with the migration package. Any custom field metadata not exposed in the APTANIA export (such as field descriptions or conditional display rules) is noted as lost and recommended for manual documentation.

APTANIA User records map to GoHighLevel Users by email address. Role and permission structures differ between platforms and do not migrate directly; we flag permission differences in the migration report for manual configuration in GoHighLevel Roles and Permissions settings. Inactive APTANIA users are flagged for optional GoHighLevel provisioning.

APTANIA email automation rules are stored server-side and are not accessible via any export mechanism. We do not migrate automation logic. As part of pre-migration preparation, we generate a written inventory of every active automation rule (trigger condition, delay, action) from in-platform screenshots provided by the customer, formatted as a GoHighLevel Workflow rebuild guide. The customer or a GoHighLevel specialist rebuilds these post-migration.