Migrate from MaxCredible to Microsoft Dynamics 365 Sales

MaxCredible Debtors are the primary entity containing contact details, credit risk scores, payment behavior history, and communication preferences. We map Debtors 1:1 to Dynamics 365 Contact (for individual debtors) or Account (for company-level debtors) based on the debtor_type field in MaxCredible. The debtor's email, phone, address, and credit risk score migrate to typed fields; credit risk score becomes a custom decimal field on Contact or Account. We request sample XML exports during scoping to confirm the debtor schema before transformation.

MaxCredible Invoices are linked to Debtors via a foreign key and include amount, due date, status, and aging bucket. Dynamics 365 Sales does not include a native invoice entity at the base tier; we create a custom Invoice table in Dataverse with a Lookup to Contact or Account, Invoice Number, Amount, Due Date, Status, and Aging Bucket fields. Invoice status maps to a Dataverse choice field (Open, Overdue, Paid, Written Off). If the customer uses Dynamics 365 Business Central alongside Sales, we map to the Business Central Sales Invoice table instead.

MaxCredible Credit Notes are issued against Invoices to adjust receivable amounts. We create a custom CreditNote Dataverse table linked to the parent Invoice record, with fields for Credit Note Number, Original Invoice reference, Adjustment Amount, Reason, and Issue Date. The net receivable balance is recalculated during migration to reflect the credit note offset against the original invoice balance.

MaxCredible Reminders are time-based tasks triggered by invoice aging rules, linked to both the Debtor and the associated Invoice. We map these to Dynamics 365 Task records with Subject, Description, Due Date, Status, and Priority preserved. The Task gets a Regarding lookup pointing to the migrated Contact or Account record and, where the Dataverse schema supports it, a secondary Regarding pointing to the custom Invoice record.

MaxCredible email communications store sender, recipient, subject, body, timestamp, template reference, and delivery status. We map these to Dynamics 365 Email (activity) records linked via Regarding to the Contact or Account. The MaxCredible template reference migrates to a custom text field for documentation; the full email body migrates to Description. Delivery status is preserved in a custom choice field.

MaxCredible SMS logs include carrier metadata, phone numbers, message content, and timestamp. Dynamics 365 Sales does not have a native SMS activity type at base tier. We create a custom activity type (msdyn_smsmessage) in Dataverse or map SMS logs to generic Activity records with channel metadata preserved in custom fields. The customer's admin can extend this with an SMS connector (Twilio, TeleSign) post-migration if needed.

MaxCredible WhatsApp logs include thread context, message content, read receipts, and media references. Dynamics 365 has no native WhatsApp integration. We map WhatsApp thread history to Activity records with thread metadata in custom fields, or to Notes attached to the Contact record. Rich context (media attachments, read status) migrates as Note attachments with a link back to the originating Activity record.

MaxCredible's AI-driven credit risk score per debtor is a snapshot value with an effective date. We migrate the current score and score_effective_date to custom fields on the Contact or Account entity (credit_score__c and credit_score_date__c). The underlying behavioral data (payment timing history, dispute frequency) is not separately exposed in MaxCredible's export and cannot be migrated. We document this limitation and recommend recalibrating credit risk models in Dynamics 365 using Power Automate or a dedicated credit scoring integration post-migration.

MaxCredible user accounts define platform access and role (Collector, Manager, Admin). We export User records with name, email, and role. In Dynamics 365, we match by email against the existing Azure Active Directory-synced User table. Any MaxCredible user without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

MaxCredible supports documents linked to Debtors or Invoices (contracts, proof of delivery, correspondence). We extract binary attachments and store them alongside migrated records. If the Dynamics 365 org is configured with SharePoint integration, we upload files to the associated SharePoint document library linked via Regarding. Otherwise, we attach files as Notes to the Contact or Account record.