Migrate from CallPro CRM to Microsoft Dynamics 365 Sales

CallPro Contact records map directly to Microsoft Dynamics 365 Sales Contact. Standard fields (FullName, Email, Phone, MobilePhone, Address) map to their Dynamics 365 equivalents. We preserve custom contact fields as Dynamics 365 custom attributes on the Contact table. Email history associations stored in CallPro migrate as related activity records. Contact is imported before Lead and before Account to satisfy parent-record lookups.

CallPro Company records map to Microsoft Dynamics 365 Sales Account. Company name becomes Account Name; domain becomes Website. Where a CallPro Contact has an explicit Company association, we resolve AccountId on the Contact record during import. Multi-database configurations in CallPro (segmentation by team or campaign) are preserved as a custom database_name__c attribute on Account.

CallPro Lead records map directly to Microsoft Dynamics 365 Sales Lead. Lead status, source attribution, and campaign association migrate to Lead Status, LeadSource, and CampaignId respectively. Dialer log entries attached to CallPro Leads carry forward as Tasks with TaskSubtype=Call on the migrated Lead record. Inactive leads are preserved with their original status; active leads requiring conversion are flagged in the reconciliation report.

CallPro Campaigns map to Microsoft Dynamics 365 Sales Campaign. Campaign member associations (Contacts and Leads enrolled in a campaign) migrate as CampaignMember records linked to the corresponding Dynamics Campaign. Email and SMS message history tied to a campaign is preserved as EmailMessage and Task records with the CampaignId reference. Note that CallPro campaign questionnaire logic and visual appointment routing rules do not have a portable schema and are documented separately for rebuild.

CallPro call activity logs (call duration, disposition code, notes, timestamp, and agent assignment) map to Microsoft Dynamics 365 Sales Task with TaskSubtype set to Call. Call duration transfers to CallDurationInSeconds; disposition code transfers to a custom disposition__c picklist field with a value map provided during scoping. The original CallPro timestamp sets ActivityDate to preserve timeline ordering. Recording URL links are stored as a custom call_recording_url__c field on the Task.

CallPro Sales Orders and Quotes map to Microsoft Dynamics 365 Sales Opportunity. Order header fields (order total, status, date) map to Amount, StageName, and EstimatedCloseDate. Line items from CallPro Sales Orders migrate as OpportunityProduct records with ProductCode, Quantity, and UnitPrice preserved. Quote status and approval flags map to a custom quote_status__c field and Opportunity StageName progression.

CallPro custom fields on Contacts, Companies, and Leads are extracted during the audit phase. We pre-create equivalent custom columns in Microsoft Dynamics 365 Sales Dataverse with matching data types (string, integer, decimal, date, picklist, boolean) before any data import. Lookup relationships defined in CallPro are reproduced as Dataverse lookup columns where the referenced object also migrates; cross-object lookups that reference non-migrated objects are stored as text fields and flagged for manual resolution.

CallPro tag taxonomy is exported and applied as either a Dynamics 365 multi-select picklist field on Contact and Lead, or as a text field with comma-separated values if the destination schema does not support multi-select. The customer chooses the strategy during scoping. We provide a tag-to-value mapping reference in the migration deliverable so that the admin can validate coverage post-import.

CallPro user records and record ownership assignments map to Microsoft Dynamics 365 Sales User by email address match. Inactive CallPro users are preserved as historical OwnerId assignments on migrated records. Active users must have a corresponding Dynamics 365 User provisioned before record import begins; we generate a user reconciliation list during scoping listing every CallPro owner without a Dynamics match, and the customer provisions missing accounts before the migration window.