Migrate from AllClients to HubSpot

AllClients contact records map 1:1 to HubSpot contacts. Standard fields (name, email, phone, address) map to HubSpot's corresponding contact properties. Owner is resolved by email match to HubSpot user accounts; unmatched owners assign to a designated fallback owner. The contact's original create date is preserved as a custom property to maintain reporting continuity from the source system.

AllClients company records map directly to HubSpot companies. The company-to-contact association in AllClients translates to a HubSpot company-contact association. HubSpot's company properties (domain, industry, phone) receive AllClients company field values. Companies load into HubSpot before contacts to ensure association lookups resolve correctly during the contact migration phase.

AllClients custom fields on contacts require pre-created HubSpot contact properties with matching types (text, number, date, enumeration). We map each field by name, infer the HubSpot property type from the source data format, and create the property before the import runs.

Company-level custom fields in AllClients migrate to pre-created HubSpot company properties. HubSpot company properties are created with the same type and options as the source custom fields before the migration loads company records. If an AllClients company custom field uses a pick-list, all unique source values are extracted and created as enumeration options in HubSpot.

AllClients contact notes map to HubSpot contact engagement timeline entries (type: note). Original timestamps, note authors, and content are preserved in HubSpot's timeline. Notes attached to company records in AllClients migrate to the corresponding HubSpot company timeline, maintaining the full context of each note entry across the CRM transition.

AllClients Workgroups (used for segmented exports and campaign targeting) map to HubSpot static Lists. We export each Workgroup membership and associate the contact records to the corresponding HubSpot list after the main contact load completes. If a Workgroup uses dynamic filter criteria, we document those rules for the admin to recreate as HubSpot Smart Lists.

AllClients does not have a native deal or opportunity tracking object. If a customer has deal-like data stored in custom fields or as tagged contact records, we surface those fields for a HubSpot admin to create Deals or custom deal properties during the migration planning phase.

AllClients owner fields store a user name or ID per contact. FlitStack resolves each owner by email lookup against HubSpot user accounts. Contacts whose owner email has no HubSpot user match are flagged and assigned to a designated fallback owner before import.

AllClients tags on contacts (e.g., 'vip', 'referral', 'churned') migrate to a HubSpot contact property — typically a multi-checkbox or text-list property depending on how many unique tags exist. Tags with fewer than 100 unique values use a HubSpot enumeration property; higher-cardinality tags use a text field.

AllClients email communications logged against contact records (stored as note entries with timestamps) migrate to HubSpot engagement timeline entries. Each logged email receives a timestamp, owner, and subject line derived from the note content. This preserves the full communication history within HubSpot's engagement timeline for each contact record.

AllClients tasks and follow-up reminders attached to contacts migrate as HubSpot tasks with the same due date, owner, and description text. Completed vs. open status is preserved from the source record. Task ownership is resolved via the same email-matching logic used for contact owner resolution during the migration.

AllClients workflow definitions cannot be exported in a portable format. We export workflow step descriptions and trigger conditions as a reference document for a HubSpot admin to rebuild. No workflow logic moves automatically; the automation layer requires a separate rebuild project.