Migrate from RAYNET CRM to Pipedrive

RAYNET Contact records map to Pipedrive Person. Standard fields (first name, last name, email, phone, address) migrate directly. RAYNET lifecycle stage property migrates as a custom picklist field on Person for audit continuity. If the RAYNET Contact has an associated Account, we link the Person to the corresponding Organization at migration time using the account_id cross-reference stored in RAYNET.

RAYNET Account records map to Pipedrive Organization. The account name, address fields, and shipping/billing addresses migrate directly. Organization is imported before Person records so that the Organization ID lookup is satisfied at the moment of Person insert, preventing orphaned Person records without an Organization link.

RAYNET Deal records map to Pipedrive Deal. Deal name, value, probability, estimated close date, and owner migrate directly. Pipeline stage from RAYNET maps to Pipedrive Pipeline stage via the stage name. We check whether RAYNET is on a tier with single or multiple pipelines; multiple RAYNET pipelines require multiple Pipedrive Pipeline configurations, which we set up before Deal import.

Each RAYNET pipeline stage (name, order, probability percentage) is extracted from the pipeline configuration and mapped to a Pipedrive Pipeline Stage with matching probability. Pipedrive allows unlimited stages per pipeline; if RAYNET had fewer stages, we pad with Pipeline Stages configured as inactive placeholders for historical alignment.

Multiple RAYNET pipelines (ENTERPRISE tier only) map to multiple Pipedrive Pipelines. Each Pipedrive Pipeline is created before Deal import and assigned a name matching the RAYNET pipeline label. If the customer is on RAYNET START or PROFESSIONAL (single pipeline only), we create one Pipedrive Pipeline and map all Deals into it.

RAYNET Activity records (calls, emails, meetings) map to Pipedrive Activity. Call duration, email subject and body, and meeting timestamps migrate directly. We link Activities to the migrated Person and Organization records by resolving the RAYNET contact_id and account_id references at migration time. Custom activity types require value mapping against Pipedrive's allowed activity types.

RAYNET Sales Order records (Subject, Final Price, Status, Estimated Costs, Delivery Date, Shipping/Billing address) do not have a direct Pipedrive equivalent object. We map these to a combination of Deal custom fields and notes. Sales Order subject becomes a Deal title prefix; price, status, and delivery date migrate as custom fields on the linked Deal record.

RAYNET Quote records with line items, validity dates, and pricing do not have a native Pipedrive equivalent. We map Quote header fields (validity dates, total price) to Deal custom fields, and line items to a structured Note attached to the Deal. If the customer uses Pipedrive's Smart Docs add-on for contracts post-migration, we flag Quote records as candidates for Smart Doc recreation.

RAYNET's Map Analysis feature auto-derives GPS latitude and longitude from contact addresses. Pipedrive does not have native geolocation. We preserve these coordinates as two custom fields (latitude and longitude as decimal number fields) on the Organization record. Customers can use these fields for map visualization via Pipedrive marketplace apps or external BI tools.

RAYNET Tags on Contacts and Deals migrate as Pipedrive Person Labels or Organization Labels (depending on object association). Labels in Pipedrive are a flat tagging system without hierarchy; if RAYNET tags had hierarchical parent-child relationships, we flatten them to a label array or prefix the tag name with the parent.

RAYNET User accounts with role assignments and deal ownership map to Pipedrive User records. We resolve owners by email match against the Pipedrive destination. Owners without a matching Pipedrive User go to a reconciliation queue for the customer admin to provision before record import resumes.

Files attached to RAYNET Contacts, Accounts, Deals, and Activities are exported via RAYNET's XLSX export and re-associated to the correct records in Pipedrive using record ID cross-references. Large attachments (over 10 MB) are flagged for alternative transfer (S3 bucket handoff) since Pipedrive's file attachment API has size constraints.