Migrate from Constructor to Salesforce Sales Cloud

Direct map for Constructor contacts that are active customers. Salesforce requires AccountId on Contact — Constructor contacts without a primary company link get attached to a default 'Unassigned Account' record or routed to the Lead object based on lifecycle status. This ensures every contact has a valid AccountId reference and maintains referential integrity in Salesforce reports and list views.

Constructor contacts flagged as prospects or without deal history route to Salesforce Lead. The Lead object uses the Status pick-list field, and Constructor contact status values map value-by-value to Salesforce Lead Status pick-list options. This routing ensures prospects enter the Salesforce lead-to-contact conversion flow rather than landing as inactive orphaned contact records.

Direct map for Constructor company records to Salesforce Account. The Account requires Name and optional ParentId for hierarchical company structures. Constructor's multi-company contact associations (N:1 contact-to-company model) are collapsed to a primary AccountId with additional company associations surfaced as Account Contact Relations for reporting clarity.

Direct map for Constructor deal records to Salesforce Opportunity. Opportunity requires AccountId, StageName, and CloseDate as mandatory fields. Constructor deal amount maps to Opportunity Amount field, and RecordTypeId assignment happens at this stage based on Constructor pipeline mapping configuration established during the pre-migration schema setup phase.

Constructor pipeline becomes a Salesforce Record Type. Each pipeline requires its own Record Type so stage pick-list values are scoped correctly per business unit. The Sales Process in Salesforce is tied to the Record Type, governing which stages appear for each deal category and controlling the lead-to-close workflow progression.

Stage names map value-by-value per RecordType. Constructor stage-entered timestamps are preserved as custom datetime fields (Stage_Entered__c) since Salesforce's native stage-history model tracks only current stage. Forecast category re-applied per Salesforce stage configuration to maintain accurate pipeline forecasting after migration.

Constructor call and email logs map to Salesforce Task with Type='Call' or Type='Email'. Constructor meetings map to Salesforce Event with original start/end times preserved. Owner assignment and original timestamps maintained. WhoId links to Contact or Lead; WhatId links to Account or Opportunity for complete activity tracking continuity.

Constructor notes migrate as Salesforce Notes (modern Note object, not legacy Note). Rich-text formatting preserved where feasible. ParentId links back to the original record (Contact, Account, or Opportunity). Inline images embedded in Constructor notes are downloaded and rehosted per Salesforce file handling rules to ensure attachments display correctly post-migration.

Constructor custom objects map 1:1 to Salesforce custom objects. Custom object fields in Constructor gain the __c suffix in Salesforce. Custom object associations that use Constructor's N:N relationship model require Salesforce junction objects — we flag these in the migration plan for admin decision and provide junction object schema templates.

Constructor owner records resolve by email match against Salesforce User records. Unmatched owners are flagged before migration — your team either provisions Salesforce User accounts for them or assigns their records to a designated fallback owner. No record lands without a valid Salesforce OwnerId, ensuring all migrated records appear in standard Salesforce queue and ownership-based reports.

Constructor file attachments re-upload to Salesforce Files (ContentDocument/ContentVersion model). File size limits apply — Salesforce default 25MB per file with higher limits available via Salesforce Shield. Files are linked to parent records via ContentDocumentLink with ShareType and Visibility settings matching your Salesforce sharing model configuration.

Constructor custom fields (any field not in the standard schema) migrate to Salesforce custom fields with __c suffix appended per Salesforce naming conventions. Data type mapping: text fields to Text, number fields to Number, pick-list fields to Picklist with values mapped per Salesforce pick-list value set conventions. All custom fields must be created in Salesforce sandbox before the data load phase to avoid validation errors.