Migrate from Atendare to HubSpot

Atendare contacts map directly to HubSpot contacts. The Atendare primary-company link becomes a HubSpot company association. For contacts without a primary company, we create an 'Unassigned' placeholder company in HubSpot before linking. This ensures that every contact has a valid company association in HubSpot after migration.

Atendare companies map to HubSpot companies. Atendare's company hierarchy (parent/child) translates to HubSpot's parent company field. Multi-contact accounts map with all associated contacts linked via HubSpot's N:N association model. We also ensure that parent-child relationships are preserved to maintain reporting accuracy across your organization.

Atendare deals map to HubSpot deals. Each Atendare pipeline becomes a separate HubSpot deal pipeline. Deal stage names map value-by-value to corresponding HubSpot pipeline stages, with probability and forecast category re-applied from HubSpot's stage settings. This mapping ensures that deal forecasting reflects the original pipeline performance metrics.

Atendare proposals contain line-item data — product, quantity, price, discount — that maps to HubSpot line items attached to the corresponding deal. The proposal header (title, status, total) becomes deal custom properties for reference since HubSpot has no native proposal object.

Atendare logged calls, emails, and meetings migrate as HubSpot engagements (calls, emails, meetings). Original timestamps, body content, and owner assignments are preserved. Attachments to activities are downloaded and re-uploaded as HubSpot file associations.

Atendare contact lists are not migrated as HubSpot lists because HubSpot lists rely on different rule syntax. We export the contact IDs in each Atendare list and deliver them as a CSV that your HubSpot admin can import as a static list. Dynamic list rules must be rebuilt using HubSpot's list criteria builder.

Atendare products migrate to HubSpot products. Product name, description, price, and unit map directly. Products are migrated before line items so the line-item-to-product lookup resolves correctly during import. This ordering prevents orphaned line items and ensures that each product reference is valid in HubSpot after migration.

Atendare custom fields on contacts map to HubSpot custom contact properties. We create the property in HubSpot with the matching field type (text, number, date, picklist) during schema setup. Picklist values require value-by-value mapping if the options differ between systems.

Atendare lead status values map to HubSpot lifecycle_stage values based on a mapping table agreed upon before migration. For Atendare statuses that don't correspond to a standard HubSpot lifecycle stage, we create a custom property to preserve the original value.

Atendare tasks and notes migrate to HubSpot as either engagement notes or tasks depending on their type. Notes with rich-text content map to HubSpot engagement notes. Action items and to-dos map to HubSpot tasks with due dates and owners preserved.

Atendare owners resolve to HubSpot users by email match. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts for them or assigns records to a fallback owner. Atendare role and permission structures do not migrate; those are configured in HubSpot separately.

Each Atendare pipeline becomes a HubSpot deal pipeline. We create the pipeline in HubSpot with the same name and configure stages matching the Atendare stage count and order. Stage probability defaults are set per HubSpot's pipeline settings. This maintains consistent deal tracking across both platforms.