Migrate from ELMA365 to HubSpot

ELMA365 contacts migrate as HubSpot contacts. We preserve original create and update timestamps as custom datetime properties since HubSpot's native createdate is set at migration time. Email address serves as the primary identifier for de-duplication and owner resolution across both systems. Each contact's email is matched against HubSpot's user list to resolve the owner assignment, ensuring proper assignment continuity after migration.

ELMA365 companies map directly to HubSpot companies without transformation. Company domain and name transfer as-is. HubSpot's company-to-contact association uses the contact's primary company property to establish the relationship; multi-contact companies resolve correctly in HubSpot's association graph, ensuring that all related contacts point to the same parent company record.

ELMA365 tasks migrate as HubSpot tasks with a direct field mapping. Subject, description, due date, priority, and status map to their HubSpot task property equivalents. Original assignees resolve by email match to HubSpot users; unassigned tasks attach to the contact or company record as standalone tasks without an owner assignment.

ELMA365 cases have a lifecycle state (Open, In Progress, Resolved, Closed) that does not map natively to HubSpot's deal pipeline. If the team uses HubSpot Service Hub, we map cases to Tickets. If Service Hub is not in scope, we map to a custom object (Case__c) with status and priority properties — your team decides the HubSpot-side configuration before migration.

ELMA365 projects represent structured work items that may contain tasks, documents, and milestones. We assess whether project-level data maps to HubSpot Deals (for sales-aligned projects) or a custom object (Project__c) for operational projects. Milestones and task counts within a project become custom properties on the target object.

Files attached to ELMA365 tasks, cases, or records re-upload to HubSpot Files attached to the corresponding contact, company, deal, or ticket record. HubSpot's 25MB per-file default limit applies; files exceeding this are flagged before migration so your team can split or rehost them externally.

ELMA365 users resolve to HubSpot users by matching their email address. Unmatched ELMA365 users are flagged in the migration plan before migration runs — your HubSpot admin either invites them to join HubSpot or assigns their records to a fallback HubSpot user account to prevent orphaned record ownership.

Every custom field in ELMA365 requires a corresponding HubSpot custom property created before migration begins. We deliver a custom property creation plan with field type mapping (text, number, date, picklist, checkbox) so HubSpot admins can pre-create the schema. HubSpot's naming convention applies — no spaces, use underscores or camelCase for property names.

ELMA365 workflows, business rules, and approval chains are process definitions that cannot transfer to HubSpot's automation engine. We export workflow definitions as structured documents your HubSpot admin uses as a rebuild reference. The exported definitions include trigger conditions, action sequences, and conditional branches.

ELMA365's low-code applications built with the BPM designer and custom widgets have no direct HubSpot equivalent. The data those apps manage migrates to HubSpot standard or custom objects; the app logic itself must be rebuilt or replaced with HubSpot's native tools or a third-party integration.

ELMA365's N:1 and 1:N associations between contacts, companies, and tasks map to HubSpot's association model using the associations API endpoint. Contact-to-company and contact-to-deal associations transfer via HubSpot's native association mechanisms, preserving the relational structure established in ELMA365.