Migrate from Entera to Pipedrive

Entera contacts map directly to Pipedrive Persons using name, email, phone, and address fields. The primary company association from Entera becomes a link to a Pipedrive Organization, which may need to be created first if it does not yet exist in Pipedrive.

Entera stores company data inside the contact record rather than as a separate object. FlitStack AI extracts every unique company name from all Entera contacts, creates the corresponding Organization records in Pipedrive, then updates each Person record with the resolved organization_id lookup. This dependency order is critical because Pipedrive requires Organizations to exist before Persons can be linked via the foreign key relationship.

Entera deals map to Pipedrive Deals with deal name, value, expected close date, and owner resolved by email matching. The Pipeline and Stage fields in Pipedrive are populated based on the Entera deal's current stage label, using the value-mapping table confirmed during the planning phase. Each Entera deal also receives its custom investment fields (IRR, cap rate, property address) via pre-created Pipedrive custom fields on the Deal record.

Each distinct stage label in Entera (e.g., Under Review, Due Diligence, Closing) is mapped to a corresponding Pipedrive Stage name within the assigned Pipeline. Probability values are applied per Pipedrive's stage configuration. Unmapped stages default to a catch-all stage and are flagged for admin review.

Pipedrive has no native property-address field. The property address from Entera is migrated as a Pipedrive varchar custom field on either the Organization or Deal entity, depending on whether Entera associates the address with the company or the deal record. FlitStack AI determines the correct parent entity during the audit phase and creates the Property_Address__c field on the appropriate entity via the /organizationFields or /dealFields API endpoint before inserting records.

Entera investment_type values (e.g., Buy-and-Hold, Fix-and-Flip, BRRRR) are mapped to Pipedrive enum options on a custom Deal field. The exact option labels are matched value-by-value; any Entera values without a Pipedrive equivalent are flagged for admin selection before migration runs.

The IRR value from Entera is migrated as a Pipedrive double-type custom field on the Deal record. Pipedrive supports numeric custom fields up to 18 digits, which covers all realistic IRR percentage values. No transformation is required beyond type mapping from Entera's numeric format to Pipedrive's double field representation.

Cap rate values from Entera are migrated as a Pipedrive double-type custom field on the Deal record, stored as Cap_Rate__c. Because Pipedrive double fields preserve full decimal precision without rounding, cap rate values transfer with complete accuracy. FlitStack AI creates the Cap_Rate__c field via the /dealFields API endpoint before inserting any Deal records, ensuring the custom field exists and is properly keyed for the first migration run.

Entera activity logs are migrated as Pipedrive Activities of the corresponding type (call, meeting, task). Each activity is linked to its parent Person or Deal record using Pipedrive's activity API parameters. Original timestamps are preserved using the done_time and due_date fields.

Entera free-text notes attached to contacts or deals migrate as Pipedrive Notes, which support both plain text and HTML content. Notes are linked to the parent Person, Organization, or Deal via the entity_type and entity_id parameters in the Pipedrive Notes API.

Entera user IDs on records are resolved by matching the owner's email address against Pipedrive user accounts. Unmatched owners are flagged before migration — your team either invites the user to Pipedrive or reassigns records to a designated fallback owner. No record lands without a Pipedrive user owner.

Entera automations (e.g., stage-triggered emails, property listing alerts) do not have a Pipedrive equivalent and cannot be migrated automatically. FlitStack exports the Entera automation definitions as a structured JSON file so your Pipedrive admin can rebuild them in Pipedrive's automation builder.

Files attached to Entera contacts, companies, or deals are downloaded and re-uploaded to Pipedrive as attachments on the corresponding Activity or Note record. Pipedrive's per-file size limit is 50 MB; files exceeding this are flagged for manual handling.

Pipedrive's native CreatedDate and update_time fields reflect the migration run timestamp, not the original Entera creation or update date. FlitStack AI preserves the original Entera timestamps as custom datetime fields (Original_Create_Date__c, Original_Update_Date__c) on each record so historical reporting continuity is maintained and your team can sort and filter by when records were originally created in Entera.

The original Entera record ID is stored on each migrated Pipedrive record as Entera_Source_ID__c. This field enables delta-run de-duplication, ensuring that if a record is modified in Entera during the cutover window, FlitStack updates the existing Pipedrive record instead of creating a duplicate. The source ID also provides a permanent audit trail back to the original Entera system for compliance and reference purposes.