Migrate from MaxCredible to Nutshell

MaxCredible debtors are the primary entity containing contact details, credit risk scores, payment behavior history, and payment terms. We map MaxCredible debtors 1:1 to Nutshell People, with company-level information (if the debtor represents a business entity) mapped to Nutshell Companies. The debtor's name, email, phone, and address fields map directly to Person fields. Payment terms and segment assignments become custom fields on the Person record. We use email as the dedupe key during import.

MaxCredible invoices have no native equivalent in Nutshell because Nutshell is a sales CRM without an invoice object. Invoice amount, due date, aging status, and invoice-to-debtor linkage migrate as a collection of custom fields on the related Person record or as a custom Deal record with AR-specific field names. We recommend a Deal-based approach when invoice tracking is frequent, using a dedicated 'AR Tracking' pipeline in Nutshell. The customer chooses the approach during scoping based on their invoice volume and reporting needs.

MaxCredible credit notes adjust invoice amounts and are linked to a parent invoice. We map credit notes as negative line items on a Deal record (if using the Deal-based invoice approach) or as a dedicated custom field tracking net balance adjustments on the Person record. The net receivable balance across all invoices and credit notes per debtor is recalculated and stored as a custom field during migration.

MaxCredible reminders are time-based tasks triggered by invoice aging rules and assigned to credit management handlers. We map reminders to Nutshell Tasks with the due date, subject, and assignee preserved. The debtor and invoice references are stored as custom fields on the Task so that the handler can navigate to the linked Person record in Nutshell. Reminder escalation levels (first reminder, second reminder, escalation) map to Nutshell Task Priority or a custom priority field.

MaxCredible tracks outbound communications across email, SMS, and WhatsApp as separate channel-specific logs. We normalize all three channels into Nutshell Activity records (Notes or Tasks depending on the channel type). Email logs map to Nutshell Note records with the template name and channel flag preserved. SMS and WhatsApp logs map to Task records with a custom channel_type field. Channel-specific metadata (WhatsApp thread context, SMS carrier data) is simplified during normalization and stored as a JSON or text blob in a custom field. Customers requiring rich channel context preservation should flag this during scoping.

MaxCredible tone-of-voice templates are stored as platform configuration with brand-style enforcement across email, SMS, and WhatsApp channels. Nutshell has an email template editor but no cross-channel brand voice enforcement feature. We export the full template body copy, variable placeholders, and segment-to-template assignments as a structured CSV and PDF documentation package. The customer's operations or marketing team uses this documentation to rebuild templates in Nutshell's editor post-migration. This is not an automated migration step.

MaxCredible generates an AI-driven credit risk score per debtor based on payment behavior analysis. We export the current score value and the effective date as a custom field on the Nutshell Person record (e.g., credit_risk_score__c and score_effective_date__c). The underlying behavioral data (payment timing history, dispute frequency) is not exposed by MaxCredible's API and cannot be migrated. The destination system cannot reproduce the same score without raw behavioral data, so we recommend recalibrating credit risk models in Nutshell using post-migration payment data.

The MaxCredible receivables ledger aggregates all open invoice items per debtor into a running balance view. Nutshell does not have a ledger or accounting object. We do not migrate the ledger as a data structure. Instead, we extract the per-debtor open balance as a custom field on the Nutshell Person record (open_receivable_balance__c). The customer's accounting team maintains the authoritative ledger in their ERP post-migration.

MaxCredible user accounts (name, email, role, and permission level) map to Nutshell User records. We match users by email address. Any MaxCredible user without a matching Nutshell User account goes to a reconciliation queue for the customer's admin to provision before the migration continues.

MaxCredible supports user-defined fields on core objects. We extract the full custom field schema during discovery, including field name, type, and all values per record. Custom field definitions must be recreated in Nutshell before data import. Nutshell custom fields support text (225 character limit), long text, currency, date, number, checkbox, and dropdown types. Long-text or high-character-count fields from MaxCredible may need to be split into multiple Nutshell text fields or truncated if they exceed Nutshell's limits.