Migrate from Empire SUITE to Pipedrive

Empire SUITE contacts map directly to Pipedrive People. Every standard field—first name, last name, email, phone, address, and job title—transfers to the corresponding Pipedrive Person fields. Original create timestamps are preserved in the create_time attribute. If a source contact has no associated company, it lands as a standalone Person in Pipedrive with no Organization link, and FlitStack logs a note for admin review.

Empire SUITE company records map to Pipedrive Organizations. The company name becomes the Organization name, industry values are mapped value‑by‑value to Pipedrive's industry picklist, and employee count and annual revenue transfer as numeric fields. Parent‑child hierarchies in Empire SUITE map to the Organization's parent field, preserving the hierarchy depth. Original create timestamps are retained on the Organization record for audit purposes.

Empire SUITE allows a contact to belong to multiple companies. Pipedrive People have a single primary Organization link. We migrate the most recently modified company association as the primary link and surface remaining associations in a custom multi-company reference field for admin review.

Empire SUITE deals map to Pipedrive Deals. Each deal transfers its pipeline reference, stage name, monetary value, close date, and owner assignment. FlitStack preserves the original create_time of the deal and maps the probability from the source stage to Pipedrive's stage‑level probability field. Deals that have no linked contact or organization are migrated as unlinked Deals, with owner assignments retained and a flag set for manual review.

Each Empire SUITE pipeline creates a corresponding Pipedrive Pipeline. The active or archived status of each pipeline is preserved, and the stage order from Empire SUITE is transferred to maintain the same workflow sequence in Pipedrive. Pipedrive supports multiple pipelines that can be displayed simultaneously in different dashboard views, matching Empire SUITE's multi‑pipeline model and allowing sales managers to switch between pipelines without losing context.

Empire SUITE stage names map value‑by‑value to Pipedrive Stage names within each corresponding Pipeline. The probability percentage from Empire SUITE stages is transferred to the Pipedrive Stage probability field, and the open/closed status of each stage is reflected in Pipedrive's stage‑level status indicator. Stage ordering is preserved to keep the pipeline flow consistent with the original Empire SUITE configuration.

Empire SUITE call, email, and meeting records map to Pipedrive Activities with the activity type set accordingly. Each Activity retains its original timestamp, due date, assigned owner, and the linked Person or Deal ID from the source. Note content migrates to Pipedrive Notes with the original create date preserved.

Empire SUITE custom contact fields are migrated as Pipedrive custom Person fields. Field type mapping follows the 16-type Pipedrive schema: text to varchar, numbers to int or double, pick-lists to settype, and date fields to date or datetime depending on precision.

Deal-level custom fields in Empire SUITE map to Pipedrive custom Deal fields. Pipedrive requires pre-creation of these fields in the UI or via API so the hash-key identifier is available for the import mapping. FlitStack registers each custom field before the migration run.

Company‑level custom fields in Empire SUITE transfer as Pipedrive custom Organization fields. Field labels and data types are preserved, with type‑aware mapping that converts Empire SUITE text, number, date, and pick‑list fields to their Pipedrive equivalents (varchar, int, double, date, settype). Multi‑select pick‑lists map to Pipedrive's listMD type, and FlitStack registers each custom field via the Pipedrive API before the migration run to obtain the required hash‑key identifier.

Empire SUITE user records are resolved by email address against Pipedrive User accounts. Unmatched owners are flagged before migration so your team can invite them to Pipedrive or assign a fallback owner. System-level or deactivated users map to the initiating admin account.

Empire SUITE workflows and automation rules do not have a direct equivalent in Pipedrive. FlitStack exports the workflow definitions as a structured JSON document that captures trigger events, conditions, and actions. Your Pipedrive admin can use this document as a reference to rebuild equivalent automations using Pipedrive's Automation rules and Sequences, ensuring that key business processes are not lost during the transition.