Migrate your MaxCredible data

Debtors are the primary entity in MaxCredible's data model, containing contact details, credit risk scores, and payment behavior history. We map Debtors 1:1 to the destination CRM's Contact or Account object, preserving the credit risk score and payment profile fields.

Invoices are linked to Debtors via a foreign relationship and include amount, due date, and status. We extract invoice records and map them to the destination's equivalent object (e.g., Opportunities in Salesforce or Deals in HubSpot), preserving the debtor link and payment status.

Credit notes are issued against invoices to adjust amounts. We migrate credit notes as line-item adjustments linked to the parent invoice, ensuring the net receivable balance is correctly reflected in the destination system.

Reminders are time-based tasks triggered by invoice aging rules. We migrate reminder definitions and their associated debtor and invoice references, preserving the workflow logic that drives MaxCredible's collections automation.

The receivables ledger aggregates all open items per debtor. We extract the ledger as a structured dataset and map it to the destination's accounting or CRM receivables view, noting that some destinations require this to be split into individual invoice and payment records.

MaxCredible tracks all outbound communications (email, SMS, WhatsApp) sent to debtors as part of the collections workflow. These are stored as structured log entries linked to the debtor record. We migrate these as activity or engagement records, but channel-specific formatting varies across destination CRMs.

Customizable communication templates define brand style across channels. These are stored as MaxCredible-specific configuration objects. We export the template content and link it to the debtor communication logs in the destination, though the template editor itself is not portable.

AI-driven credit risk scores are computed per debtor based on payment behavior. We export the current score value and the scoring model version used. Scores may need to be recomputed in the destination if the target CRM has its own credit risk engine.

MaxCredible connects to ERP systems via XML file uploads and custom-built links for Oracle and SAP. Integration configuration (mapping rules, sync frequency) is stored in MaxCredible-specific settings. We document the ERP link configuration during discovery but cannot directly migrate it to a non-MaxCredible system.

Some customers use Tableau for advanced MaxCredible reporting. The report definitions (stored in Tableau, not MaxCredible) need to be rebuilt or reconnected to the new data source after migration. We export the underlying data for reconstruction.

MaxCredible supports user-defined fields on core objects. We extract the full field schema and values during the migration scope call. Custom field definitions must be recreated in the destination, and values are mapped field-by-field.

Automated workflows trigger actions (reminders, escalations, communications) based on invoice aging and debtor segments. We document the workflow rules during discovery. Since automations are MaxCredible-native, they must be rebuilt in the destination CRM's automation engine.

MaxCredible user accounts define who can access the platform and their role. We export user records including name, email, and role assignment. In the destination, these map to the standard user or team member object.

Documents linked to debtors or invoices (e.g., contracts, proof of delivery) are supported. We extract binary attachments and store them alongside the migrated records. File format compatibility and storage limits in the destination should be confirmed during scoping.