Migrate from Atendare to Freshsales

Atendare Contact records map to Freshsales Contact objects with name, email, phone, address, owner assignment, and custom properties preserved. We use email as the dedupe key during import. Any segmentation tags or lifecycle properties stored on the Atendare Contact migrate as custom fields or multi-select picklist values. Freshsales requires custom fields to be pre-created in Admin Settings before import; we handle this during the schema phase so that the CSV column headers match destination field API names exactly.

Atendare Company records map to Freshsales Account. The company-contact relationship is preserved by resolving the Atendare company_id foreign key to the Freshsales Account record before Contact import begins. Company-level custom fields migrate as Freshsales Account custom fields created in the same schema phase. Website, industry, annual revenue, and address fields map directly to Freshsales Account equivalents.

Atendare Deals map to Freshsales Deals with deal name, value, expected close date, stage, owner, and associated company preserved. The deal-to-company link resolves to the Freshsales Account record by email domain or company name match. Atendare stage names and probabilities map to a Freshsales Sales Process that we configure in Admin settings before migration. Custom deal properties migrate as Deal custom fields.

Atendare Pipelines define the stages a Deal moves through. We extract all pipeline configurations including stage names, stage order, and probability percentages during discovery. Each Atendare Pipeline becomes a Freshsales Sales Process (defining stage names and probabilities) and a corresponding Record Type (scoping page layouts and deal entry criteria). Pro tier or above is required for multiple Sales Processes; we confirm the destination tier during scoping.

Atendare tracks multiple activity types per contact including calls, meetings, and tasks with timestamps, descriptions, and owner assignments. We split Atendare's multi-activity structure into Freshsales Task (for calls and tasks) and Event (for meetings). The original Atendare activity type is preserved in a custom field for reconciliation. Activity dates migrate as ActivityDate on Task and StartDateTime/EndDateTime on Event. Owner resolution uses email-based matching against Freshsales Users.

Atendare Team Members assigned as Deal owners or Activity owners map to Freshsales User records by email. We extract all distinct owner references from Contacts, Companies, Deals, and Activities during discovery. Owners without a matching Freshsales User go to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Atendare users map to inactive Freshsales Users if historical assignment needs to be preserved.

Atendare custom fields on Contacts, Companies, and Deals vary by account configuration. We detect every custom property definition during discovery including field name, data type, and required status. Freshsales custom fields must be created in Admin Settings before any data import; we pre-create all mapped fields during the schema phase with matching field types (text, number, date, picklist, multi-select picklist, checkbox, currency). Custom field mapping is documented field-by-field in the migration spec.

Atendare Products (names, SKUs, pricing, descriptions) map to Freshsales Product records. Product-to-Deal associations migrate as Deal line items with quantity, unit price, and discount preserved. We create the Product2 records before Deal migration so that line item resolution is satisfied at import time. If Atendare's product catalog is empty or sparse, we note this during discovery and skip the Product phase.

Atendare contact segments defined by filter rules are extracted as saved filter criteria during discovery. Freshsales Lists are rebuilt as static lists or dynamic lists using Freshsales's filter builder, based on the original Atendare segment logic. Segment membership is re-evaluated at migration time by applying the original filter criteria against the migrated contact data. We document each segment's original rule and recommend a Freshsales list rebuild approach.