Migrate from crmConnect to Salesforce Sales Cloud

crmConnect Contact records with no clear lifecycle stage (crmConnect does not expose a lifecycle model) default to Salesforce Lead if the contact is unqualifed or to Salesforce Contact if it is attached to a pipeline or has deal history. We use pipeline attachment as the split heuristic: contacts with no associated Opportunities map to Lead; contacts with at least one Opportunity map to Contact tied to the resolved Account. Tags and segments migrate as a custom field Tags__c (multi-select picklist) or as Campaign records with CampaignMember entries at the customer's choice.

crmConnect's single pipeline (Professional tier) maps to a Salesforce Opportunity Record Type with a corresponding Sales Process. Stage names from crmConnect migrate to StageName values, and probability percentages map to StageProbability. We configure the Record Type and Sales Process in the destination org before Opportunity import begins so that the RecordTypeId lookup is satisfied at insert time.

crmConnect Opportunities map to Salesforce Opportunity with Amount, StageName (resolved via the Sales Process mapping), CloseDate, and OwnerId carried over. The crmConnect opportunity-to-contact association maps to the OpportunityContactRole object in Salesforce. We resolve AccountId on Opportunity at migration time by matching the associated crmConnect Company name to the Salesforce Account name.

crmConnect calendar events migrate to Salesforce Event with Subject, StartDateTime, EndDateTime, Location, and Description preserved. Attendee records migrate to EventRelation entries linked to the resolved Contact or Lead. crmConnect Standard tier limits to 1 calendar; Professional tier allows unlimited, and we map each calendar separately against the Salesforce User's calendar.

crmConnect automations use a drag-and-drop builder with no documented JSON export format. We capture automation screenshots and metadata where accessible and deliver a written automation inventory document listing every active automation's trigger, conditions, actions, and a recommended Salesforce Flow equivalent. The customer's admin rebuilds automations in Flow post-migration. This is not a limitation of FlitStack AI specifically; it is a platform constraint of crmConnect.

crmConnect funnels and landing pages are visual content objects that have no transferable export format. We export funnel structure and page content as HTML snapshots and template documentation, noting that reassembly in Salesforce Experience Cloud or an external CMS requires manual rebuild. This is scoped as a written handoff, not a data migration.

crmConnect membership records (Professional tier) migrate to a Salesforce custom object Membership__c with fields for membership_status, enrollment_date, expiry_date, and a lookup to the parent Contact. We pre-create the Membership__c custom object and its fields in the destination org before import. Tier and status values map to custom picklist fields on the custom object.

crmConnect course records (Professional tier) migrate to Salesforce as Course__c custom objects with fields for course_name, description, and course_status. Student enrollment records map to a related Course_Enrollment__c custom object with a lookup to Course__c and to the Contact representing the student. We pre-create both custom objects and their lookup relationship before import.

crmConnect custom form field definitions and response data export separately. We map field types (text, number, date, dropdown) to Salesforce custom field types and pre-create the schema in a custom object before importing response records. Form response data that represents a lead capture maps to Salesforce Lead with the custom field values preserved. Form definitions themselves (layout, styling) do not transfer.

crmConnect email campaign templates and contact association lists migrate to Salesforce Campaign records. We preserve campaign name, send date, send count, and open rate as custom fields on the Campaign. Subscriber lists migrate as CampaignMember entries linked to the resolved Contact or Lead. Campaign content (HTML templates) is exported as a file attachment and noted for manual reassembly in Salesforce email tools or Marketing Cloud. Automation sequences tied to sends are documented but not migrated.

crmConnect SMS blast sequences (Professional tier, limit of 3) migrate to a Salesforce custom object SMS_Blast__c with fields for sequence_name, message_body, send_date, and subscriber_count. Subscriber lists map to CampaignMember records under a campaign record dedicated to the SMS blast. SMS sending capability in Salesforce requires integration with an SMS gateway (Twilio, SMS Magic, or a native Salesforce SMS product); the migration deliverable includes the contact list and message content, not the SMS sending configuration.

crmConnect Professional tier e-commerce products (up to 6) migrate to Salesforce Product2 records with Name, ProductCode (from SKU), and Description. We create Standard Pricebook entries during import so that the products are available in Opportunity Line Items. Product associations to contacts (as order records) map to Opportunity records with the Product2 as the line item if the customer uses Salesforce's quoting flow.

crmConnect invoicing and text-to-pay records (Professional tier) migrate to a Salesforce custom object Invoice__c with fields for invoice_number, invoice_date, amount, status, and line_items as a text summary. Payment records migrate to a related Payment__c custom object with amount, payment_date, payment_method, and status. The Invoice__c and Payment__c objects link to the Account and Opportunity representing the customer and deal.

crmConnect custom contact and opportunity properties have no documented API schema endpoint, so we discover available fields during the export phase by examining the CSV column headers and sampling values for type inference. We pre-create Salesforce custom fields with the matching API names (sanitized to remove spaces and special characters) and type-mapped data types (text to Text, numbers to Number, dates to Date). Custom field creation happens before the data import phase so that the fields are available as targets during field mapping.

crmConnect contact tags export as tag-to-contact mappings. We migrate tags as a custom multi-select picklist field on Contact or Lead (preferred for small tag sets under 200 unique tags) or as Salesforce Campaign records with CampaignMember entries (preferred for large or dynamic segment lists). The customer chooses the strategy during scoping. Tag membership is preserved as a field value on each migrated contact record.

crmConnect owner references on Contact, Company, Opportunity, and Calendar records resolve by email match against the Salesforce User table in the destination org. We extract every distinct owner email, match it against Salesforce Users, and flag any owner without a match in a reconciliation queue. The customer's Salesforce admin provisions missing Users (active for current employees, inactive for departed) before record import resumes. OwnerId on Opportunity and Event is required at insert time.