CRM migration
Field-level mapping, validation, and rollback between Altcraft and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Altcraft
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
8 of 12
objects map 1:1 between Altcraft and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Altcraft to Microsoft Microsoft Dynamics 365 Sales is a platform-category migration: Altcraft is a customer data platform and marketing automation suite; Microsoft Dynamics 365 Sales is a sales-focused CRM. The structural mismatch means we must resolve Altcraft's unified Profile object into Dynamics' Lead, Contact, Account, and Opportunity entities, decide which profiles are sales prospects versus marketing-only contacts, and route the split before any data enters Dynamics. Engagement history (email, SMS, call, and meeting records stored against Altcraft Profiles) migrates via the Dynamics Web API with parent-record resolution so that timelines attach to the correct Contact or Opportunity. We do not migrate Automation Scenarios, Web Layer configurations, or Control Group logic as code; we deliver written inventories for admin rebuild. The migration scope is bounded by Altcraft's broken API documentation, which forces us to export through CSV where possible or through Albato integrations where the customer has them configured.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Altcraft platform overview
Scorecard, SWOT, gotchas, and pricing for Altcraft.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Altcraft object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Altcraft
Profile
Microsoft Dynamics 365 Sales
Contact or Lead (split required)
1:manyAltcraft Profiles with behavioral history and subscription data require a routing decision before migration. Profiles that represent individual buyers with purchase history map to Salesforce Contact attached to an Account. Profiles that represent early-stage prospects with no purchase record may route to Lead. We preserve the original Altcraft Profile ID in a custom field for audit and cross-reference. The routing rule is defined during scoping based on whether the Profile has an associated order, deal stage, or sales-owner assignment.
Altcraft
Company
Microsoft Dynamics 365 Sales
Account
1:1Altcraft Companies map to Dynamics 365 Account. The Company domain maps to Account.Website, and Company name maps to Account.Name. Account is created before any Contact import to satisfy the AccountId lookup relationship.
Altcraft
Deal
Microsoft Dynamics 365 Sales
Opportunity
1:1Altcraft Deals map to Dynamics 365 Opportunity. Deal stage maps to Opportunity.StageName via a customer-approved stage matrix configured before migration. Deal amount, close date, owner, and associated Products all migrate to the Opportunity record.
Altcraft
Segment (Static)
Microsoft Dynamics 365 Sales
Contact/Lead List or Custom Field
1:1Altcraft static segments are list-based membership records that map to Dynamics Contact or Lead list membership. We export segment names and member Profile IDs, then create corresponding list records or populate a multi-select picklist custom field on Contact that encodes segment membership.
Altcraft
Segment (Dynamic)
Microsoft Dynamics 365 Sales
Custom View or Filter
lossyAltcraft dynamic segments depend on real-time behavioral criteria that do not have a direct Dynamics equivalent. We export the segment definition logic (rule structure, criteria fields, operators) as a written specification, and the Dynamics admin recreates equivalent advanced find views or uses Power Automate to replicate the dynamic criteria.
Altcraft
Message Template
Microsoft Dynamics 365 Sales
Email Template
1:1Altcraft message templates migrate to Dynamics Email Template records. HTML body migrates to TemplateBody, subject to Template.Subject. A/B test variants are preserved as separate template records with naming convention indicating the variant. Dynamics supports both HTML and plain text templates.
Altcraft
Campaign
Microsoft Dynamics 365 Sales
Campaign
1:1Altcraft Campaign records (send history, open and click analytics, channel assignment) map to Dynamics Campaign. Campaign response data migrates to CampaignMember records. Engagement metrics (opens, clicks) are stored as custom fields because Dynamics Campaign tracks response rates rather than individual engagement events.
Altcraft
Engagement (Email, SMS, Call, Meeting)
Microsoft Dynamics 365 Sales
EmailMessage, Task (Call), Event (Meeting)
1:1Altcraft engagement records attach to Profiles. We resolve each engagement's parent Profile to the corresponding Dynamics Contact or Lead ID, then create the appropriate Dynamics record: EmailMessage for email, Task with TaskSubtype=Call for calls, Event for meetings. SMS engagements map to Task records with a custom sms_body__c field if no native SMS entity is available in the destination Dynamics configuration.
Altcraft
Product
Microsoft Dynamics 365 Sales
Product
1:1Altcraft Products map to Dynamics Product2 records with Standard Pricebook entries. ProductCode, Description, and BasePrice migrate directly. We resolve the Pricebook2 reference during import.
Altcraft
Order
Microsoft Dynamics 365 Sales
Custom Order Object or Opportunity Line Item
lossyAltcraft Order records linked to Profiles migrate to a custom Order entity with an Account lookup if Dynamics Sales does not include the Commerce or Supply Chain Management module. Order status, total amount, and line items transfer as structured data. The customer confirms during scoping whether a custom Order entity or OpportunityLineItem approach applies.
Altcraft
Custom Profile Field
Microsoft Dynamics 365 Sales
Custom Field on Contact/Lead/Account
lossyAltcraft user-defined fields on Profile export as structured CSV columns. We map each to a corresponding custom field on the appropriate Dynamics entity (Contact, Account, or Lead), handling type differences (string, date, number, boolean). Picklist-style custom fields map to Dynamics picklist or multi-select picklist fields where applicable.
Altcraft
Control Group
Microsoft Dynamics 365 Sales
Campaign Holdout Group (manual rebuild)
1:1Altcraft Control Groups assign specific Profiles to campaign holdouts for comparative analytics. Microsoft Dynamics 365 Sales does not have a native Control Group equivalent. We preserve Control Group membership as a custom Contact field (e.g., control_group_name__c), and the customer's marketing team implements comparable holdout logic in Dynamics Campaign or in an integrated marketing tool. The written inventory we deliver includes the Control Group membership list for manual re-entry.
| Altcraft | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Profile | Contact or Lead (split required)1:many | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Segment (Static) | Contact/Lead List or Custom Field1:1 | Fully supported | |
| Segment (Dynamic) | Custom View or Filterlossy | Fully supported | |
| Message Template | Email Template1:1 | Fully supported | |
| Campaign | Campaign1:1 | Fully supported | |
| Engagement (Email, SMS, Call, Meeting) | EmailMessage, Task (Call), Event (Meeting)1:1 | Fully supported | |
| Product | Product1:1 | Fully supported | |
| Order | Custom Order Object or Opportunity Line Itemlossy | Fully supported | |
| Custom Profile Field | Custom Field on Contact/Lead/Accountlossy | Fully supported | |
| Control Group | Campaign Holdout Group (manual rebuild)1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Altcraft gotchas
Profile-count pricing means database size drives the bill
Automation Scenarios do not export as portable logic
API developer guide returns HTTP 301, blocking programmatic discovery
Private Cloud and on-premise use separate support contracts
Control Group assignment is Profile-ID dependent
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
Discovery and routing rule definition
We audit the source Altcraft instance across cloud tier, profile count, custom fields, segments, campaigns, engagement volume, and order history. We pair this with an assessment of the destination Microsoft Dynamics 365 Sales environment: edition (Professional $65/user, Enterprise $105/user, Premium $150/user), existing schema, active workflows, and any AppSource integrations in use. The discovery output is a written migration scope that includes the Profile-to-Lead-Contact routing rule, a complete field mapping draft, and a list of Altcraft objects that require rebuild rather than migration.
Schema design and custom field provisioning
We design the destination schema in Microsoft Dynamics 365 Sales . This includes creating any missing custom fields on Contact, Account, Lead, and Opportunity that correspond to Altcraft custom Profile fields, provisioning the Dynamics Account and Contact entities for the Company-to-Account mapping, and configuring the Opportunity stage matrix to match the Altcraft deal stage values approved by the customer. We deploy schema changes to a Dynamics Sandbox first for validation before any data loads.
Data export and cleansing
Because Altcraft's API documentation returns 301, we export via CSV from the Altcraft UI where supported. We extract Profiles, Companies, Deals, Products, Campaigns, and Message Templates as separate CSV files. We run a data quality pass: deduplication by email, required-field validation against the Dynamics schema, date format normalization (ISO 8601), and identification of records that require routing decisions. Any records with missing primary identifiers are quarantined for customer resolution before import.
Sandbox migration and reconciliation
We run a full migration into a Microsoft Dynamics 365 Sales Sandbox using production-like data volume. The customer's Dynamics admin reconciles record counts (Accounts in, Contacts in, Leads in, Opportunities in, Products in), spot-checks 25-50 records against the Altcraft source for field accuracy, and validates the Profile-to-Contact routing rule. Any mapping corrections happen in the sandbox before production migration begins. This step also surfaces any Dynamics validation rules or field-level security that would block the production import.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Altcraft Companies), Contacts (with AccountId resolved), Leads (with the routing rule applied), Opportunities (with AccountId, OwnerId, and stage resolved), Products and Pricebook entries, Engagement history (EmailMessage, Tasks, Events via Dynamics Web API with batch handling), and Custom Profile Fields. Each phase emits a row-count reconciliation report before the next phase begins. We use exponential backoff and batch chunking on the Dynamics Web API to respect rate limits.
Cutover, validation, and rebuild handoff
We freeze Altcraft writes during cutover, run a final delta migration of any records modified during the migration window, then mark Microsoft Dynamics 365 Sales as the system of record. We deliver the Scenario inventory, Control Group membership lists, and Segment definitions to the customer's Dynamics admin. We support a one-week hypercare window for reconciliation issues raised by the sales team. We do not rebuild Altcraft Scenarios as Dynamics Workflows inside the migration scope; that is a separate engagement or an internal admin task.
Platform deep dives
Altcraft
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Altcraft and Microsoft Dynamics 365 Sales .
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Altcraft and Microsoft Dynamics 365 Sales .
Object compatibility
All 8 core objects map 1:1 between Altcraft and Microsoft Dynamics 365 Sales .
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Altcraft: Configurable via API_MAX_REQUESTS_COUNT — exceeding returns HTTP 429. Specific numeric limits are not published in the developer guide and must be confirmed per deployment..
Data volume sensitivity
Altcraft exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Altcraft to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Altcraft to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Altcraft
Other ways to arrive at Microsoft Dynamics 365 Sales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.