Migrate from Apptivo to Microsoft Dynamics 365 Sales

Apptivo Contacts with no associated Customer record or with a lifecycle stage property set to Prospect map to Salesforce-style Lead in Microsoft Dynamics 365 Sales . Apptivo Contacts attached to a Customer record map to Dynamics 365 Contact linked to the corresponding Account. We determine the split using the Apptivo Customer link on the Contact record and preserve any lifecycle or stage property in a custom field apptivo_stage__c on both Lead and Contact.

Apptivo Customers (B2B account records with associated contacts and addresses) map to Dynamics 365 Account. The Customer's primary address maps to the Account's Address fields, and any billing or shipping distinctions in Apptivo map to the corresponding Dynamics 365 address roles. Account is created first so that the AccountId lookup is satisfied at Contact insert time.

Apptivo Leads with scoring and source tracking migrate directly to Dynamics 365 Lead. Lead score migrates to a custom integer field apptivo_lead_score__c; source tracking migrates to LeadSource. We resolve the Apptivo Owner to a Dynamics 365 User by email match and set OwnerId at insert.

Apptivo Opportunities map to Dynamics 365 Opportunity. Deal amount maps to Amount, expected close date to CloseDate, and the Apptivo pipeline stage to a Microsoft Dynamics 365 Sales Process stage. Stage probabilities migrate from Apptivo's stage configuration to the StageProbability field on Opportunity. The Customer link resolves to AccountId on the Opportunity record.

Each Apptivo deal pipeline becomes a Microsoft Dynamics 365 Sales Process with stage values mapped from the source pipeline. We configure the Sales Process in the destination org before migration so that stage picklist values match the Apptivo terminology the sales team is familiar with. Stage probability percentages round to the nearest integer allowed by Dynamics 365.

Apptivo Cases migrate to Dynamics 365 Cases. Ticket status from Apptivo maps to Case Status, priority maps to Priority, and owner maps to OwnerId via the User email reconciliation. Conversation history (customer portal threads) migrates as EmailMessage records linked to the Case. Case limits are enforced by Dynamics 365 plan tier; we verify the destination org's Service licensing before migration.

Apptivo custom attributes in each app's Master Layout map to Dynamics 365 custom fields on the corresponding entity. A critical nuance: Apptivo's 'Region' field in the Contacts app is a different field from 'Region' in the Cases app. We enumerate all custom attributes per app during discovery, assign each a unique Dynamics 365 field name (e.g., cust_region_contacts__c, cust_region_cases__c), and build a per-app field mapping table to prevent silent field collisions.

Apptivo Items (product and service catalog) map to Dynamics 365 Product2 records. SKU from Apptivo maps to ProductCode, name maps to Name, and price migrates to the Standard Price Book. Custom attributes on Items (text, number, date, dropdown) map to custom fields on Product2.

Apptivo file attachments on records migrate as Dynamics 365 Note (Annotation) records with DocumentBody and Filename populated from the Apptivo file blob. We download attachments from Apptivo in batches to avoid export timeouts, then upload to Dynamics 365 via the Web API. The parent record lookup (object type and ID) is preserved during the transfer.

Apptivo Projects with task hierarchies, milestones, and assignees migrate as Dynamics 365 Project Service records if the destination org licenses Project Operations. If Project Operations is not in scope, we migrate Projects as a custom entity with custom fields for milestones and assignees, and flag the custom-project-to-standard-Project mapping for the customer's admin to configure post-migration.

Apptivo Invoices with line items, tax codes, and payment status migrate to Microsoft Dynamics 365 Sales Invoice if the destination has Sales Cloud, or to Business Central Invoice if the customer licenses both. Invoice headers map directly; line items map to InvoiceProduct records. We recommend reviewing partial payment records post-migration because Apptivo's partial payment tracking may not map cleanly to Dynamics 365's invoicing state machine.