Migrate from Infor CloudSuite Customer Relationship Management (CRM) to Pipedrive

Infor CRM Accounts map directly to Pipedrive Organizations. The CRM tab on Infor's Customers form holds SIC code, revenue, employee count, and territory assignments; we map these to Organization custom fields in Pipedrive. Account is loaded before Persons so the Organization-Person linkage is satisfied at insert time.

Infor Sales Contacts map to Pipedrive Persons with name, email, phone, and role preserved. Infor's Outlook export behavior creates duplicates rather than syncing, so we deduplicate on email address plus name match before landing Person records. Any Sales Contact without an email is matched on name and company only. Custom field types (picklists, dates, lookups) on the Contact form map to equivalent Pipedrive custom field types.

Infor CRM Opportunities map to Pipedrive Deals with stage, value, probability, and close date preserved. The Opportunity-Account linkage maps to Deal-Organization. Stage names from Infor map to Pipedrive pipeline stage names, which we configure before migration. Probability maps to a numeric custom field if the customer relies on it for reporting.

Infor CRM separates Prospects (pre-conversion) from Leads (post-qualification, pre-conversion). Pipedrive has a single Lead object for unqualified prospects and a separate Deal model for qualified opportunities. We merge Infor Prospects and Leads into Pipedrive Leads, preserving the source record type (Prospect vs Lead) in a custom field for audit. If the customer runs a dual-track qualification process, we configure Pipedrive's Lead status picklist to match Infor's status values.

Infor Activities (calls, meetings, tasks, notes) linked to Contacts or Opportunities map to Pipedrive Activities with type, description, date, and owner preserved. Infor stores Interaction records (Sales Contact Interactions, Prospect Interactions, Customer Interactions) against contacts; we map these to Pipedrive Activity records with the Person as the activity owner. Activity date ordering is preserved by setting the Pipedrive Activity timestamp to the original Infor timestamp.

Infor Sales Forecasts aggregate Opportunities into forecast periods defined by Sales Periods (named date ranges). Pipedrive has no native Sales Period equivalent. We decompose each Infor Sales Period into start and end dates and map forecast totals to Deal-level custom fields (forecast_amount, forecast_period_start, forecast_period_end). The territory or rep associated with the forecast maps to a custom field on the Deal for segmentation in Pipedrive's reporting.

Infor Territories assign reps to geographic or account-based regions, and Quotas set targets per rep per territory per period. Pipedrive has no native territory or quota object. We reconstruct territories as Organization custom fields (territory_name, territory_region) and quotas as numeric custom fields on Deals or as Pipedrive Goals. The customer chooses the reconstruction approach during scoping based on how they use territory data in reporting.

Infor Campaigns store type, status, start/end dates, and budget, with Campaign Items linking products or contacts to the campaign. Pipedrive does not have a native campaign management object. We map Campaigns to Pipedrive Activities with campaign name, type, status, and dates as custom fields, and attach Campaign Items as Activity participants or as Person custom field values. If campaign ROI tracking is critical, we recommend Pipedrive's reporting with custom filters rather than a native campaign model.

Infor CRM ticketing stores support cases with status, priority, assigned agent, and conversation history linked to Accounts and Contacts. Pipedrive does not have a native ticketing object. We map Tickets to a dedicated Pipedrive service pipeline (a separate Deal pipeline with stages matching Infor ticket status), or to Activities if the customer prefers not to use Deals for support. Multi-line ticket conversations migrate as Activity notes.

Infor Products and Price Lists used for quoting map to Pipedrive Products. The Price List form stores pricing tiers per product; we create Pipedrive Price List entries linked to each Product. Complex tiered pricing requires validation in Pipedrive's price configuration since Pipedrive Products support unit price and cost but not multi-tier price list entries natively without a custom field or app extension.

Infor Quotes hold products, prices, and discounts linked to Opportunities and Accounts. Pipedrive does not have a native quote object. We map Quote headers and line items to Deal custom fields (quote_number, quote_amount, quote_status) and attach the Quote PDF as a Pipedrive file linked to the Deal. If the customer requires formal quoting, we recommend Pipedrive's Smart Docs app or a separate CPQ integration post-migration.

Infor CRM Users serve as record Owners and are linked to Territories. We map Users to Pipedrive Users by email match. Any Infor User without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes.