Migrate from Wise Agent to Microsoft Dynamics 365 Sales

Wise Agent Contact maps directly to Dynamics 365 Contact. FlitStack resolves the primary company by email lookup and populates AccountId on the Contact record. All standard fields (name, email, phone, address) carry over directly. Owner resolution runs by email match against Dynamics 365 users.

Wise Agent Company object — which holds property and listing data alongside company information — maps to Dynamics 365 Account. Property-specific fields (MLS ID, listing status, property type) migrate as custom fields on the Account record. Dynamics 365 Account.Address fields carry street/city/state/zip directly.

Wise Agent Transactions hold deal data, stage checklists, and checklist-item completion status. FlitStack maps the deal-level fields (transaction name, amount, stage, close date) to a Dynamics 365 Opportunity. Checklist items and transaction-specific custom fields create a related custom table (TransactionChecklist__c) linked by OpportunityId.

Wise Agent labels are arbitrary string tags on contacts with no cardinality limit. FlitStack extracts all unique label values from the source, creates a custom option-set field (WiseAgentLabel__c) on the Contact entity, and maps each contact's labels as pipe-delimited values or as individual option entries depending on how the team uses them.

Wise Agent task reminders and to-do items map to Dynamics 365 Task records. Standard fields including Subject, Description, DueDate, Priority, and Status map directly without transformation. ParentRecord references link each Task to the corresponding Contact, Account, or Opportunity record in Dynamics 365, preserving the original contextual relationship from Wise Agent.

Wise Agent logged emails migrate as Dynamics 365 Email records. FlitStack preserves the full email metadata including Subject, Description (body), From, To, SentDate, and regarding object link. Email integration with Exchange Online requires separate configuration within Dynamics 365 after the migration completes.

Wise Agent call logs migrate as Dynamics 365 PhoneCall activity records. All relevant call details including Subject, Description, PhoneNumber, Direction, StartDateTime, and Duration map directly. Owner resolution occurs by matching the email address of the Dynamics 365 user who logged the call.

Wise Agent calendar events and meetings map to Dynamics 365 Appointment records. Key appointment details including Subject, Location, StartDateTime, EndDateTime, RequiredAttendees, and OptionalAttendees carry over directly. The regarding object links each meeting to the Contact or Opportunity it was originally scheduled against.

Wise Agent notes attached to contacts, companies, or transactions migrate as Dynamics 365 Annotation records. The NoteText body, Subject, and ObjectId (regarding) link carry over. FlitStack downloads embedded file attachments and re-uploads them to the Dynamics 365 SharePoint or Dataverse file storage.

Wise Agent users and owners are resolved by email address against Dynamics 365 SystemUser records. Unmatched owners are flagged before migration runs — teams either provision the user in Dynamics 365 first or assign records to a fallback owner. User-specific settings (notification preferences) are not migrated.

Wise Agent drip campaigns and follow-up sequences do not have a direct equivalent in Dynamics 365 Sales. FlitStack exports the campaign definitions (step names, delays, content references) as a structured JSON document. Teams rebuild these sequences using Power Automate flows or Dynamics 365 Sales premium automation features post-migration.

Wise Agent MLS-synced property data (listing ID, status, MLS feed source, photos) does not map to any native Dynamics 365 entity. FlitStack creates a custom MLSListing__c table with the necessary fields and migrates the listing data as records linked to the corresponding Account.