Migrate from Altcraft to Salesforce Sales Cloud

Altcraft Profiles map to Salesforce Contact as the primary record, with the behavioral history, channel subscriptions, device context, and location metadata stored as custom fields on Contact. The Altcraft Profile email address becomes the Contact Email field and is used as the dedupe key during import. We pre-create a default Account (using Account Name derived from the Profile's company field or a placeholder) so that AccountId is resolved at Contact insert time. Any loyalty tier or promo eligibility attributes transfer as custom fields on Contact.

Altcraft user-defined fields on the Profile object export as structured columns in the profile CSV. We map each field to a Salesforce custom field on Contact, handling type differences (string, date, number, boolean, picklist) and creating a custom field migration matrix during discovery. Behavioral attributes like last_channel_interaction or engagement_score become custom Number or Text fields on Contact for use in Salesforce reports and Flow criteria.

Altcraft Scenarios include conditional branching, loop constructs, time delays, and API webhook calls that have no standard export format. We cannot generate a drag-and-drop import package for Salesforce Flow. We export each Scenario as a structured description document listing the trigger, all branches, loop exits, referenced Profiles, and webhook endpoints, then deliver a Scenario Inventory to the customer's admin for manual Flow rebuild. This is documented configuration, not a code migration.

Static segments export as straightforward record lists tied to Profile IDs. We map them to Salesforce Campaign Members by resolving the Profile ID to the new Contact ID post-migration. Dynamic segments depend on real-time behavioral criteria that have no direct Salesforce equivalent; we export the segment definition as a structured description and recommend Salesforce Marketing Cloud Account Engagement (Pardot) Lists or a custom Salesforce List object with criteria-based population rules as the equivalent.

Altcraft message templates export in standard formats. A/B test variants transfer as separate EmailTemplate records. Subject lines, HTML bodies, and merge field names migrate directly; the merge field references update from Altcraft syntax to Salesforce merge field syntax (e.g., {{Profile.FirstName}} becomes {!Contact.FirstName}) during the template transformation step.

Altcraft Campaign records (including send history, open and click analytics, and channel assignment) map to Salesforce Campaign. Performance metrics like open rate and click rate migrate as custom fields on Campaign because Salesforce's native Campaign reporting tracks member counts and revenue rather than engagement ratios. We preserve the campaign-channel association as a custom field on Campaign for reporting purposes.

Altcraft Control Groups are assigned to specific Profile IDs. If Profiles receive new IDs during the Salesforce import, the Control Group association breaks. We preserve Control Group membership as an explicit attribute on each Profile record before export, then re-apply the assignment after Salesforce Contact IDs are established, ensuring that comparative analytics (treatment vs. holdout) remain valid in the destination Campaign reporting.

Altcraft supports Email, SMS, Web Push, Mobile Push, and Messenger channels with sender IDs, API credentials, and approved sending domain configurations. These credentials are platform-bound and do not transfer. We document the existing channel configuration (sending domain, SMS sender ID, messenger app credentials) and re-establish them in Salesforce or Salesforce Marketing Cloud as part of the migration configuration step. Salesforce Email relay or Marketing Cloud Email Studio replaces Altcraft's native email channel by default.

Altcraft Products transfer as Salesforce Product2 records with Standard Price Book entries created during import. ProductCode maps from the Altcraft SKU field. Order history is linked to the Contact at migration time via a custom Order__c object with a Contact lookup, preserving purchase history for segmentation and reporting in Salesforce. If the destination org uses Salesforce Order Management, we map directly to the native Order object.

Altcraft loyalty program tiers, point balances, and promo code pools transfer as a custom LoyaltyProgram__c object with a lookup to Contact. Promo code pools export as a custom PromoCode__c object linked to the LoyaltyProgram. We preserve the full loyalty structure and promo rules as structured data; recreation in Salesforce depends on whether the customer implements a native loyalty app from AppExchange or builds a custom solution with Apex triggers.

Altcraft Form definitions and NPS survey question structures export cleanly as structured data. Survey responses already embedded in Profile records migrate as standard Profile data. Standalone response logs transfer as a custom SurveyResponse__c object linked to Contact. The form definition itself (field layout, conditional logic) does not migrate; we document the structure for recreation in Salesforce Web-to-Lead, Experience Cloud, or a third-party survey tool.

Altcraft's Web Layer module (popups, tracking goals, tag manager) is client-side configuration independent of Profile data. We do not migrate these as they require re-implementation in the destination platform's tag management or equivalent module. We deliver a written inventory of all active popup triggers, goal definitions, and tag rules for the customer's web team to re-implement in Salesforce Experience Cloud or a tag manager like Google Tag Manager post-migration.