Migrate from Marketing Creatio to HubSpot

Creatio Contact maps directly to HubSpot Contact. The contact's name field in Creatio is split into firstname and lastname for HubSpot. Primary phone maps to HubSpot phone; any additional phone property becomes mobilephone. Contacts without a primary account link remain as standalone HubSpot contacts.

Creatio Account maps to HubSpot Company. Standard fields — name, domain, industry, number of employees, annual revenue — translate directly. Parent Account relationship uses HubSpot's Parent Company field. Multi-account contacts collapse to the primary account with secondary accounts noted in a custom property.

Creatio Opportunity maps to HubSpot Deal. Deal name, amount, and close date migrate directly. Deal stage maps to HubSpot pipeline and dealstage via value mapping — each Creatio stage name is matched to a named HubSpot stage within the target pipeline.

Creatio stage names map to HubSpot pipeline stage values value-by-value. Probability and forecast category are applied per stage based on HubSpot's stage settings. Original stage-entered timestamps are preserved as custom datetime properties for reporting continuity. Each stage mapping is validated against the target pipeline configuration to ensure the stage exists and accepts the expected values before migration begins.

Creatio Case maps to HubSpot Ticket. Subject, status, priority, and case origin transfer as HubSpot ticket properties. Case-specific custom fields require HubSpot custom properties to be created first. SLA timer fields have no native HubSpot equivalent and migrate as custom date fields.

Creatio Lead maps to HubSpot Lead. Name, email, phone, company, and job title transfer directly. Lead status uses value mapping to match Creatio's pick-list values to HubSpot's lead status options. Owner resolves by email match to HubSpot users. If a HubSpot user with the matching email does not exist, the lead is flagged for manual owner assignment before the migration run completes.

Creatio Activities with type column values Call, Email, Meeting, and Task map to their HubSpot equivalents. Original engagement dates and activity owners are preserved. Parent-record links are rebuilt via HubSpot's association API after records land. Each activity type is validated to ensure the correct HubSpot engagement schema is applied, and any attachments or notes associated with the activity are migrated alongside the parent record.

Creatio Note body maps directly to HubSpot Note. Rich-text formatting is preserved. File attachments on notes are extracted, uploaded to HubSpot Files, and linked back to the note record. Inline images are downloaded and rehosted in HubSpot's file storage. All note associations to contacts, accounts, or deals are maintained through HubSpot's association API to preserve the full context of each note after migration.

Creatio custom objects map 1:1 to HubSpot custom objects (Enterprise tier). Custom object relationships that use Creatio's N:N model require HubSpot junction objects when the relationship is many-to-many. We surface the required junction object schema in the migration plan before records move.

File attachments on any Creatio record (contact, account, opportunity, case) are downloaded, re-uploaded to HubSpot Files, and linked to the corresponding HubSpot record. File size limits per destination apply. Inline images embedded in notes are handled separately from the note body.

Creatio marketing campaigns and campaign activities have no direct HubSpot equivalent. We export campaign definitions, audience rules, and enrollment logic as a structured reference document so your HubSpot team can rebuild campaigns using HubSpot's workflow and list tools. The export includes campaign names, descriptions, target audience criteria, associated tracks or nurture sequences, and performance metrics from Creatio to guide the rebuild process in HubSpot.

Creatio business units and territories are organizational constructs with no HubSpot Teams equivalent. We preserve business unit names and hierarchies in a custom property so admin teams can configure HubSpot Teams and sharing rules after migration. The exported business unit data includes the full organizational hierarchy, reporting relationships, and territory assignments from Creatio to support accurate team configuration in HubSpot.