Migrate from MaxCredible to HighLevel

MaxCredible Debtors map directly to GoHighLevel Contacts. The debtor's contact name, email, phone, address, and payment behavior fields map to the corresponding GoHighLevel Contact standard fields. We use the debtor's email address as the dedupe key during import to prevent duplicate Contact creation. Any custom fields on the Debtor record are flagged during scoping and recreated as GoHighLevel custom Contact fields before migration.

MaxCredible Invoices map to GoHighLevel Opportunities. The invoice amount maps to the Opportunity amount, the due date maps to Close Date, and the invoice status (Open, Overdue, Paid, Written Off) maps to a GoHighLevel pipeline stage that we configure during schema design. We preserve the invoice number as a custom Opportunity field for audit traceability. The parent Debtor reference resolves to the Contact during migration.

MaxCredible Credit Notes represent invoice adjustments. We map them to the related GoHighLevel Opportunity as a negative line item or as a separate Opportunity with a 'Credit Note' type and reduced amount. The net receivable balance is recalculated at migration time against the parent invoice to ensure the Opportunity reflects the correct outstanding amount in GoHighLevel.

MaxCredible Reminders are time-based tasks triggered by invoice aging rules. We migrate Reminder definitions as GoHighLevel Tasks linked to the corresponding Contact and Opportunity. The due date, priority, and description migrate. Reminder trigger logic (aging thresholds, debtor segments) is documented in the automation inventory we deliver; it does not migrate as code and must be rebuilt in GoHighLevel's workflow builder.

MaxCredible's receivables ledger aggregates all open items per debtor. We extract the ledger as a structured dataset and configure a GoHighLevel pipeline view that reflects open invoices and their aging status. This is a configuration reconstruction rather than a direct data migration, as GoHighLevel's pipeline stage model approximates the ledger view without a dedicated AR ledger object.

MaxCredible email communications migrate to GoHighLevel Activity records of type Email. The email body, recipient, sender, and timestamp migrate to the Activity. Template references from MaxCredible are preserved as a custom field for documentation. GoHighLevel's two-way email sync keeps the inbox consistent post-migration.

MaxCredible SMS logs migrate to GoHighLevel Activity records with type SMS. Carrier metadata (delivery status, segment count) is stored as custom Activity fields. GoHighLevel's native SMS capability requires its own SMS plan; we migrate the log data regardless of the destination SMS configuration.

MaxCredible WhatsApp messages include thread context that does not map directly to a standard GoHighLevel object. We migrate WhatsApp communication content as GoHighLevel Activity records with a WhatsApp channel tag and the thread reference stored as a custom field. The rich thread hierarchy is simplified into a flat activity log in GoHighLevel.

MaxCredible's AI credit risk score per debtor migrates as a GoHighLevel custom number field on the Contact object. The score value and its effective date migrate. Because the underlying behavioral data (payment timing, dispute frequency) is not exposed by MaxCredible, the destination score is a static value; it cannot reproduce the AI model's output. We document this and recommend recalibrating a scoring model in GoHighLevel post-migration using the historical payment data migrated as invoice records.

MaxCredible tone-of-voice templates are stored as platform configuration. We export the template body copy and variable placeholders as a structured documentation package. GoHighLevel's email template editor does not accept MaxCredible's template format; the customer's marketing or operations team rebuilds them manually in GoHighLevel using the exported copy. We provide a template mapping spreadsheet to accelerate the rebuild.