Migrate from RAMM to Pipedrive

RAMM People map directly to Pipedrive Person. The Person object holds name, email, phone, job title, and address. FlitStack resolves the primary Organization link by matching company_name against Pipedrive Organization records; unmatched organizations are created first to satisfy the foreign key.

RAMM Organizations map to Pipedrive Organizations 1:1. Name, domain, industry, address, employee count, and annual revenue transfer as standard fields. Parent-child organizational hierarchies use Pipedrive's parent_organization_id field; FlitStack migrates parent organizations first, validates domain uniqueness, and flags circular references before loading.

RAMM Deals map to Pipedrive Deals with direct field transfers for title, value (amount), close date, and owner. The pipeline and stage assignment uses Pipedrive's pipeline_id and stage_id fields; FlitStack maps each RAMM pipeline to a distinct Pipedrive pipeline and each stage to a corresponding Pipedrive stage by order.

RAMM logged calls become Pipedrive Activities with activity_type='call'. Subject, notes, due_date, and marked_done status transfer directly. Owner assignment uses email-match resolution against Pipedrive users. The person_id and org_id links are restored by matching contact email against migrated Pipedrive Person records.

RAMM logged emails migrate as Pipedrive Activities with activity_type='email'. Subject, body content, and sent timestamp transfer; inbound versus outbound distinction is stored in a custom flag field since Pipedrive's activity_type does not distinguish direction natively. Links to Person and Organization records are reconstructed from email address matching post-migration.

RAMM meeting records become Pipedrive Activities with activity_type='meeting'. Start time, end time, location, and subject transfer. Attendee data (if stored as a linked Person list) is preserved in the activity note body; Pipedrive does not have a native attendees field on Activities, so FlitStack appends the attendee list as formatted text.

RAMM to-do items and tasks map to Pipedrive Activities with activity_type='task'. Due date, priority flag, and marked_done status transfer. Open tasks from RAMM land as open Activities in Pipedrive; completed tasks land as marked=true Activities. Each task is linked to the originating Person, Organization, or Deal record via the respective ID field.

RAMM notes attached to People, Organizations, or Deals become Pipedrive Files uploaded to the corresponding record. Rich-text formatting in RAMM notes is flattened to plain text during transfer since Pipedrive Files do not preserve inline HTML. File name, content (as text), and creation timestamp are preserved; file size limits are checked before loading.

RAMM custom fields on People require Pipedrive custom fields to be created in the destination account first. Because Pipedrive assigns each account a unique 40-character hash key for custom fields, FlitStack generates the field definitions in Pipedrive during the migration run and maps the field key dynamically rather than copying hard-coded keys.

Organization-level custom fields follow the same pattern as Person custom fields: FlitStack creates the Pipedrive field definition using the correct field type (text, number, date, pick-list, or bool) as inferred from the RAMM schema, then populates values during the data load. Pick-list fields require a value-by-value map when the options differ between systems.

Deal-level custom fields (probability overrides, deal source tracking, custom priority tiers) migrate as Pipedrive Deal custom fields. Numeric and currency fields transfer directly; date fields use ISO 8601 formatting. If RAMM stores a custom probability value, FlitStack maps it to Pipedrive's stage-specific probability unless a custom probability field is requested.

RAMM workflow rules, automation triggers, and sequence definitions have no native export and cannot migrate automatically. FlitStack documents the active automation definitions (trigger conditions, actions, and filter logic) in a structured export file that your Pipedrive admin can use to rebuild equivalent Automations and Sequences in Pipedrive.

RAMM reports and dashboards are built against live queries and cannot be exported as reusable definitions. The underlying data migrates to Pipedrive, so reports can be rebuilt once records are in place. FlitStack provides a data dictionary showing what migrated fields are available in Pipedrive so report authors can map their metrics correctly.

RAMM owner IDs are resolved by matching the owner's email address against the Pipedrive users list. Unmatched owners are flagged before migration — your team can invite them to Pipedrive first or assign their records to a fallback user. No record lands in Pipedrive without a valid owner assignment.