Migrate from MaxCredible to Pipedrive

MaxCredible Debtors are the primary entity containing contact details, credit risk scores, and payment behavior history. If a Debtor represents a company, we split into a Pipedrive Organization with the company name as the Organization name and a Person record for the primary billing or contact person. If the Debtor is an individual, we create only a Person record. The split logic uses the Debtor's company registration or business type field if present; otherwise we create both and let the customer reconcile during the sandbox validation phase. We preserve the MaxCredible debtor_id as a custom field on both the Person and Organization for cross-system audit trails.

MaxCredible Invoices are linked to Debtors and include amount, due date, status, and payment behavior history. We map each Invoice to a Pipedrive Deal, using the invoice amount as the Deal value, the invoice due date as the close date, and the invoice status (Open, Overdue, Paid, Credit Note Applied) as a custom picklist field that maps to the Deal stage. Overdue invoices receive an Overdue deal stage; paid invoices receive Won. We resolve the parent Debtor to the Pipedrive Person or Organization created in the previous step and attach the invoice number as a custom text field for reconciliation.

MaxCredible Credit Notes are issued against invoices to adjust receivable amounts. We map each Credit Note to a Pipedrive Deal Note attached to the corresponding Deal (the one created from the original Invoice), with the note body containing the credit note amount, reason, and effective date. If the Credit Note fully cancels the invoice, we update the Deal value to zero and set stage to Won. Partial credit notes update the Deal value to the net amount and add a note with the adjustment details.

MaxCredible Reminders are time-based tasks triggered by invoice aging rules. Each Reminder has a debtor reference, an invoice reference, a due date, and a description of the action to take. We map Reminders to Pipedrive Activities of type Task, linked to the Person or Organization (Debtor) and the Deal (Invoice). The Task due date maps from the Reminder due date, and the Task subject and notes capture the Reminder description. Reminders that were completed in MaxCredible become completed Tasks in Pipedrive with the original completion date preserved.

MaxCredible tracks outbound communications across email, SMS, and WhatsApp channels, each with channel-specific metadata. We normalize these into Pipedrive's Activity model: email communications map to Pipedrive Email activities, phone-based outreach maps to Call activities, and meeting requests map to Meeting activities. WhatsApp and SMS messages without a meeting context map to Note activities with a custom channel_type__c field set to SMS or WhatsApp. The channel-specific metadata (WhatsApp thread context, SMS carrier metadata, email template references) is normalized into custom fields and notes for audit but the original rich context is simplified in the Pipedrive activity timeline. We flag which communications require rich context preservation during scoping.

MaxCredible's receivables ledger aggregates all open items per Debtor. We extract the ledger as a structured dataset and map it to Pipedrive Deals using custom fields: open_amount__c, payment_terms__c, last_payment_date__c, and total_outstanding__c. The custom fields are pre-created in Pipedrive before migration using the Pipedrive API field creation endpoint. Some Pipedrive plans limit custom field counts; we validate the target plan during scoping and recommend Advanced or above if the customer has complex receivables data.

MaxCredible stores tone-of-voice templates as platform configuration with custom-branded communication rules enforced across email, SMS, and WhatsApp. These are not machine-readable structured data. We export the template body copy, variable placeholders, and channel-specific formatting rules as a JSON documentation file during the discovery phase. The customer's marketing or operations team rebuilds the templates in Pipedrive's Email Templates editor. We provide the variable mapping between MaxCredible placeholders and Pipedrive's template variable syntax during the handoff call.

MaxCredible's AI generates a credit risk score per Debtor based on payment behavior analysis, but the underlying behavioral data (payment timing history, dispute frequency) is not separately exposed for export. We migrate the current score value and its effective date as custom fields (credit_risk_score__c and score_effective_date__c) on the Person and Organization records. The score is a snapshot value that will not recalculate in Pipedrive without access to the raw behavioral dataset. We document this limitation in the migration report and recommend the customer either accept the static score as a reference value or recalibrate a scoring model in Pipedrive using their own data warehouse post-migration.

MaxCredible user accounts define access and role assignment. We export user records including name, email, and role. In Pipedrive, these map to standard User records. We match by email address during migration. Any MaxCredible User without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Pipedrive's per-user pricing means the customer should decide which MaxCredible users need Pipedrive access before migration to avoid over-licensing.

Documents linked to Debtors or Invoices (contracts, proof of delivery, correspondence attachments) migrate as Pipedrive Files attached to the corresponding Person, Organization, or Deal. We extract binary attachments from MaxCredible and upload them to Pipedrive's file storage using the Pipedrive API. File format compatibility is validated before migration; MaxCredible-specific formats are converted to PDF where possible. Pipedrive's Essential plan includes 5 GB file storage per user; larger migrations may require a storage plan upgrade or file archival strategy.

MaxCredible supports user-defined fields on Debtors, Invoices, Credit Notes, and Reminders. We extract the full custom field schema during discovery, including field name, data type, and all values per record. In Pipedrive, we pre-create the equivalent custom fields before migration using the Pipedrive API field creation endpoint, matching field types: text fields to varchar, numeric fields to number, date fields to date, and picklist fields to Pipedrive's custom picklist type. Custom field definitions must be identical between source and destination; we validate the schema match during sandbox migration before production cutover.

MaxCredible connects to ERP systems via XML file uploads over SSL with Verisign certificate authentication, with custom-built links for Oracle and SAP. The integration configuration, mapping rules, and sync frequency are stored in MaxCredible-specific settings that cannot be exported as a working configuration. We document the current integration setup (ERP type, sync frequency, data flows) during discovery and deliver a written ERP integration requirements document. Pipedrive has no native ERP integration; the customer rebuilds the data flow using a middleware platform (Zapier, Make, Boomi) or custom API connector. We provide a data dictionary of the MaxCredible XML schema to assist their integration developer.