Migrate from APTANIA CRM to Microsoft Dynamics 365 Sales

APTANIA Contact records map directly to Dynamics 365 Contact. We extract all standard fields (fullname, emailaddress1, telephone1, mobilephone) and custom properties that appear in the exported file. The B2C/B2B flag from APTANIA is preserved as a custom field aptania_contact_type__c on the Contact record. APTANIA Contact records are imported after Account records so that the parentcustomerid_account lookup is satisfied at insert time.

APTANIA Company records map to Dynamics 365 Account. The company name becomes the Account Name (name) field, and domain data from APTANIA maps to the Website field for reference. Account is imported first in the sequence because Contact and Deal records depend on the parent AccountId lookup. We use the APTANIA company ID as a staging key and match it against the Account record created during import to resolve parent references on child records.

APTANIA Deals map to Dynamics 365 Opportunity. We extract deal value (amount), stage name, close date, and any linked contact reference. The pipeline-stage relationship in APTANIA is not publicly documented, so we infer the stage list from the distinct values present in the exported deal records and configure corresponding Sales Process stage values in Dynamics 365 before import.

APTANIA pipeline structure (stages, stage names, probabilities) is inferred from exported deal records since the pipeline schema is not publicly documented. We reconstruct this as a Microsoft Dynamics 365 Sales Process linked to a Record Type on Opportunity, with stage probabilities rounded to the nearest integer values allowed by Dynamics 365.

APTANIA Activity logs (emails, calls, notes) map to Dynamics 365 Activity records. The exact APTANIA activity schema is not publicly documented, so we export all available fields and map them to the corresponding Dynamics 365 activity type (Task for generic activities, Email for email logs, PhoneCall for call logs). Any fields that do not map to a standard Dynamics 365 field are stored as custom fields on the activity record.

APTANIA user records are exported and matched to Dynamics 365 Users by email address. Role and permission structures are not directly portable because APTANIA's security model differs from Dynamics 365's role-based security. We flag permission differences for manual review and provide a role-mapping guide so the customer's admin can assign the appropriate Security Role in Dynamics 365 post-migration.

APTANIA custom fields are exported with their field names and values. We create corresponding custom fields on the relevant Dynamics 365 entity (Contact, Account, Opportunity) using the Dataverse API before data import. APTANIA custom property metadata is not fully exposed in export files, so we document any fields that cannot be reconstructed from the exported values and flag them for the customer to validate in Dynamics 365 post-import.

APTANIA email automation rules are not exportable and do not migrate. We capture a screenshot-based inventory of all active automation rules during scoping and deliver it as a written document with trigger conditions, target audiences, and action sequences, so the customer's admin has a reference guide to rebuild using Dynamics 365 Workflow or Power Automate post-migration.

APTANIA channel attribution data (referrer, UTM parameters, landing page history) is stored inside APTANIA's tracking system and is not exportable to standard file formats. Historical web engagement data is lost at migration. We flag this gap in the data map and recommend that the customer configure fresh web tracking in Microsoft Dynamics 365 Sales AI or through Azure Application Insights before go-live to preserve future attribution data.