Migrate from SuperOffice CRM to Pipedrive

SuperOffice Company records map directly to Pipedrive Organization. The Company record name becomes the Organization name; address fields map to Pipedrive address fields. Organization is the first object imported in every migration because every Contact in SuperOffice carries a Company reference via the associate table, and Pipedrive requires the Organization to exist before a Person can be linked to it during import.

SuperOffice Contact records map to Pipedrive Person. Each Contact's associated Company reference is resolved to the Organization created in the first import phase. Email, phone, title, and address fields map directly. Custom fields on the Contact record are recreated as custom fields in Pipedrive before Person import begins. SuperOffice contact categories map to a multi-select picklist or tags in Pipedrive.

SuperOffice Sale records map to Pipedrive Deals. The SuperOffice Sale.SaleType links to a pipeline, and Sale.SaleStatus maps to a stage within that pipeline. We configure the Pipedrive pipeline stages during pre-migration setup to match the SuperOffice stage order and probability percentages. The linked Company and Contact associations migrate as Person and Organization links in Pipedrive.

SuperOffice pipeline stages are tied to the SaleType list table with associated stage probabilities. Each SuperOffice SaleType becomes a Pipedrive pipeline stage. We capture the stage order, probability percentage, and any stage-specific probability rules during discovery and apply them as stage configuration in Pipedrive before Deal import.

SuperOffice Activities linked to Contact or Company records migrate as Pipedrive Activity records. Appointments become Meetings; tasks become Tasks; calls become Calls. The activity completion status, duration, and timestamp migrate directly. Activity links to the related Person and Organization are preserved by resolving the SuperOffice associate table references during the transform phase.

SuperOffice email activities linked to Contact or Company records migrate as Pipedrive Email activities. Email subject, body content, sender, and recipient migrate. The link to the associated Person or Organization resolves via the SuperOffice associate table. Note that email body content is migrated as a text field; inline images and attachments are handled as file references in the post-migration documentation.

SuperOffice Project records do not have a native equivalent in Pipedrive's standard object set. We offer two approaches during scoping: map Projects as a custom field on the linked Deal or Organization, or create a Projects app from the Pipedrive Marketplace. The chosen approach is applied during pre-migration setup. Project type and status are preserved as custom field values in either case.

SuperOffice Quotes map to Pipedrive Deals with the quote body stored as a custom text property. SuperOffice QuoteAlternative versions (multiple proposal versions per sale) flatten to the primary QuoteAlternative as the Deal amount and description; secondary alternatives are serialized as a JSON structure in a custom field. The deal close date maps from the Quote's valid-to date.

SuperOffice Users (Associates) map to Pipedrive Users by email address match. We resolve each Associate's email against the Pipedrive User table. Any Associate without a matching Pipedrive User goes to a reconciliation queue for the customer to provision before record import resumes. Role-based access control in SuperOffice maps to Pipedrive permission sets, which are configured post-migration.

Custom fields on SuperOffice Contacts, Companies, Sales, and Projects are recreated as custom fields in Pipedrive before their parent object is imported. Dropdown list values in SuperOffice must be manually recreated in Pipedrive as picklist options. We provide a custom field creation checklist as part of the pre-migration documentation.

Tags applied across Contact, Company, Sale, and Project objects in SuperOffice export as comma-separated values and are applied as Pipedrive Tags on the corresponding Person, Organization, or Deal. Tag names are preserved exactly; no normalization is applied unless the customer requests it during scoping.