Migrate from Maple CRM to Pipedrive

Maple CRM Leads map directly to Pipedrive Leads. We map source, status, assigned executive, follow-up dates, and any custom intake data fields. Jurisdiction-specific intake fields (IRCC-relevant fields from Canada intake forms) map to Pipedrive custom fields that we pre-create in the destination account before migration. Pipedrive's Leads object (separate from People) is available on all paid tiers and handles unqualified prospects before they enter a Deal pipeline.

Maple CRM Client records split into Pipedrive Person (contact details, email, phone, address, nationality, passport data) and Organization (if the Client is a corporate applicant or employer sponsor). For individual applicants, only a Person record is created. For corporate clients with linked Cases, both an Organization and Person are created, and the Organization is used as the parent lookup on the subsequent Case-to-Deal migration. We run Clients before Cases to ensure Organization lookups are resolved at Deal insert time.

Maple CRM Cases map to Pipedrive Deals as the core immigration process object. We map the process stages (Application, Review, Submission, Approval, Denial/Appeal) to Pipedrive pipeline stage values in a custom immigration pipeline we create before migration. Visa type, jurisdiction, IRCC filing number, case officer, and denial/appeal reason migrate as custom fields on the Deal. The Deal's Organization link points to the Client Organization record resolved in the previous step. Active and recent Cases (typically last 24 months) are migrated; archived or fully resolved Cases older than 24 months are excluded unless the customer specifies otherwise.

Each Maple CRM Case pipeline (if multiple immigration service lines exist) becomes a Pipedrive Pipeline with corresponding stage values. We pre-create the pipeline and stage structure in Pipedrive before any Deal migration begins. Stage probabilities are set to reflect immigration process realities — approval rates by visa type are customer-provided during scoping and mapped to stage probability percentages.

Documents attached to Cases or Clients migrate as binary file blobs. We extract the file content from Maple CRM's document storage API, re-upload to Pipedrive's Activity attachments or Deal file section, and preserve document type metadata (passport, proof of funds, visa application, intake form), upload date, and related Case/Client link as Pipedrive custom fields on the attachment. Large documents (scanned PDFs over 10 MB) are chunked and re-assembled. If Maple CRM exposes document download URLs via API, we fetch and re-upload directly; if not, the customer provides a document export archive and we process from that.

Maple CRM Agreement records (rendered agreements with filled macro placeholders) migrate as Pipedrive Deal-linked Notes or Attachments. The underlying agreement data (service terms, fee schedule, renewal dates) migrates to custom fields on the Deal. The Agreement template definitions with macro placeholders are not API-exportable and are documented in the automation inventory for manual rebuild in Pipedrive Smart Docs or a third-party e-sign tool like DocuSign or PandaDoc post-migration.

Maple CRM Quotations map to Pipedrive Products linked to Deals. Quotation line items, pricing, and status migrate as Pipedrive Product entries with custom pricing. The PDF quotation itself is not migrated; only the underlying data record transfers. If Pipedrive Products are used, we create Price Book entries during migration. Quotations remain in open status until reconciled with corresponding Deal stage.

Maple CRM Invoices migrate to Pipedrive as Deal custom fields (invoice number, amount, payment status, outstanding balance) plus an Activity note recording the invoice history. Instalment schedules are modeled as multiple Activity entries with dates and amounts. Historical paid invoices preserve the paid status and payment date. Pipedrive's native invoicing is not used unless the customer opts in during scoping, as it requires separate setup.

Maple CRM Contracts and Annual Maintenance Contracts (AMCs) linked to Clients migrate to Pipedrive Deals with contract term custom fields (start date, end date, renewal date, service terms, pricing). Renewal date is stored as a custom date field on the Deal for use in Pipedrive's upcoming renewal alerting or automation rules post-migration. AMC status (active, lapsed, renewed) is a custom picklist field.

Maple CRM Support Requests migrate as Pipedrive Leads (for intake-level requests) or as Deal-linked Activities (for case-specific support). Support Request status, priority, assignee, and timestamps migrate to custom fields on the target object. SLA TAT and escalation rules are not API-exportable and are documented in the automation inventory for manual rebuild in Pipedrive's workflow tools post-migration. Open and recent Support Requests (typically last 12 months) are migrated; fully resolved and archived requests are excluded.

Maple CRM User accounts with role-based access control map to Pipedrive User records by email match. Role and team assignments are preserved as Pipedrive User custom fields during migration. Any Maple CRM user without a matching Pipedrive User email goes to a reconciliation queue for the customer's admin to provision before record import resumes. Staff records with HR data (compensation, PTO) are not stored in Maple CRM and therefore not in scope.