Migrate your Altcraft data
Omnichannel CDP and marketing automation platform from Russia, available as cloud, private cloud, or on-premise. Targets mid-to-enterprise teams that need unified customer profiles and multi-channel orchestration under one roof.
In its favor
Why people choose Altcraft
The signal that keeps Altcraft on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Unified customer profiles that merge behavioral data with CRM and SQL sources into a single 360° view that most standalone marketing tools cannot replicate without custom integration work.
Omnichannel orchestration from one interface—Email, SMS, Web Push, and Messengers all managed under shared segmentation and scenario logic rather than separate tools.
Flexible deployment model spanning managed cloud, dedicated private cloud, and on-premise options, which matters for regulated industries and enterprises with data-residency requirements.
Dedicated migration assistance bundled into Cloud Pro and Private Cloud tiers, giving teams a supported path onto the platform without requiring external implementation partners.
Starting price of $520/month for Cloud tier represents mid-market entry without the per-feature gating common at that price point among Western competitors.
Profile-based pricing scales with database size, creating unpredictable monthly bills as the contact list grows and pushing teams toward flat-rate alternatives.
On-premise and private cloud installations require custom integration work per environment, making the total cost of ownership higher than the headline subscription price suggests.
Limited public review presence and sparse independent user community make peer validation and competitive comparison difficult before committing.
Documentation and developer guides return errors or redirect loops, raising concerns about the platform's long-term maintenance and support responsiveness for enterprise accounts.
Reasons to switch
Why people leave Altcraft
The recurring reasons buyers give for replacing Altcraft. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Altcraft fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Altcraft pricing overview
Altcraft charges on a per-profile basis across all cloud tiers, with subscription costs scaling as the customer database grows. The Private Cloud and On-premises tiers use individual contracts with custom pricing based on infrastructure requirements and feature scope. No free tier or public trial is available.
Cloud
Tier 1 of 4
from $520/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Altcraft's schedule — see our quote-based pricing →
What gets migrated
Altcraft object support
Object-by-object support for Altcraft migrations. Per-pair details surface during scoping.
Profiles (Customer Profiles)
Fully supportedThe central object in Altcraft's data model. Holds the full action history, channel subscriptions, location and device metadata, and all custom fields. We export Profile records via CSV including behavioral history and import them with custom field mappings preserved. Dynamic segments are mapped to the destination's segment logic separately.
Automation Scenarios
Mapping requiredSequences of trigger-action rules that govern marketing workflows. Scenarios can include conditional branches, time delays, API webhooks, and loop constructs. Migration requires us to translate these into the destination platform's workflow format; complex branching logic may need manual reconstruction depending on the target system's expressiveness.
Segments (Static & Dynamic)
Mapping requiredStatic segments are straightforward list transfers. Dynamic segments depend on real-time behavioral criteria that may not map 1:1 to the destination's segment engine. We export the segment definition and rebuild equivalent dynamic audiences in the target system using the closest available operator set.
Message Templates
Fully supportedAltcraft supports template import from Unisender, Mailchimp, and Sendsay at the source level, and we export Altcraft templates in standard formats. A/B test variants are preserved as separate template versions. We map merge tags to destination field placeholders during the import phase.
Campaigns
Fully supportedCampaign records including send history, open and click analytics, and channel assignment. We transfer campaign metadata and performance metrics; engagement events are re-attributed in the destination system as new activity once sends resume.
Communication Channels
Mapping requiredEmail, SMS, Web Push, Mobile Push, and Messenger integrations. Channel configuration (sender IDs, API credentials, approved sender addresses) must be re-established in the destination platform. Altcraft's custom channel support in Private Cloud requires environment-specific handling.
Products & Orders
Mapping requiredE-commerce data linked to customer profiles. Products transfer as catalog records; order history is linked to the Profile at migration time. If the destination is not e-commerce-native, order records are migrated as custom Profile attributes or a separate Orders object.
Forms & NPS Surveys
Fully supportedForm definitions and survey question structures export cleanly. Responses already embedded in Profile records migrate as standard Profile data; standalone response logs transfer as a related data object.
Control Groups
Mapping requiredCampaign holdout groups used for comparative analytics. We preserve Control Group membership assignments linked to Profile IDs. The destination platform must support Control Group logic natively for statistical comparison to remain valid post-migration.
Loyalty & Promo Codes
Mapping requiredLoyalty program tiers and promo code pools are tied to Profile records. We export the full loyalty structure and promo rules as structured data; recreation in the destination depends on whether the target system has native loyalty management.
Custom Profile Fields
Fully supportedUser-defined fields on the Profile object export as structured columns in the profile CSV. We map each field to the destination's equivalent custom field, handling type differences (string, date, number, multi-select) during import.
Web Layer (Popups, Goals, Tag Manager)
Mapping requiredClient-side tracking and popup configurations live in Altcraft's Web Layer module. These are independent of Profile data and must be re-implemented in the destination platform's tag management or equivalent module.
| Object | Support | Notes |
|---|---|---|
| Profiles (Customer Profiles) | Fully supported | The central object in Altcraft's data model. Holds the full action history, channel subscriptions, location and device metadata, and all custom fields. We export Profile records via CSV including behavioral history and import them with custom field mappings preserved. Dynamic segments are mapped to the destination's segment logic separately. |
| Automation Scenarios | Mapping required | Sequences of trigger-action rules that govern marketing workflows. Scenarios can include conditional branches, time delays, API webhooks, and loop constructs. Migration requires us to translate these into the destination platform's workflow format; complex branching logic may need manual reconstruction depending on the target system's expressiveness. |
| Segments (Static & Dynamic) | Mapping required | Static segments are straightforward list transfers. Dynamic segments depend on real-time behavioral criteria that may not map 1:1 to the destination's segment engine. We export the segment definition and rebuild equivalent dynamic audiences in the target system using the closest available operator set. |
| Message Templates | Fully supported | Altcraft supports template import from Unisender, Mailchimp, and Sendsay at the source level, and we export Altcraft templates in standard formats. A/B test variants are preserved as separate template versions. We map merge tags to destination field placeholders during the import phase. |
| Campaigns | Fully supported | Campaign records including send history, open and click analytics, and channel assignment. We transfer campaign metadata and performance metrics; engagement events are re-attributed in the destination system as new activity once sends resume. |
| Communication Channels | Mapping required | Email, SMS, Web Push, Mobile Push, and Messenger integrations. Channel configuration (sender IDs, API credentials, approved sender addresses) must be re-established in the destination platform. Altcraft's custom channel support in Private Cloud requires environment-specific handling. |
| Products & Orders | Mapping required | E-commerce data linked to customer profiles. Products transfer as catalog records; order history is linked to the Profile at migration time. If the destination is not e-commerce-native, order records are migrated as custom Profile attributes or a separate Orders object. |
| Forms & NPS Surveys | Fully supported | Form definitions and survey question structures export cleanly. Responses already embedded in Profile records migrate as standard Profile data; standalone response logs transfer as a related data object. |
| Control Groups | Mapping required | Campaign holdout groups used for comparative analytics. We preserve Control Group membership assignments linked to Profile IDs. The destination platform must support Control Group logic natively for statistical comparison to remain valid post-migration. |
| Loyalty & Promo Codes | Mapping required | Loyalty program tiers and promo code pools are tied to Profile records. We export the full loyalty structure and promo rules as structured data; recreation in the destination depends on whether the target system has native loyalty management. |
| Custom Profile Fields | Fully supported | User-defined fields on the Profile object export as structured columns in the profile CSV. We map each field to the destination's equivalent custom field, handling type differences (string, date, number, multi-select) during import. |
| Web Layer (Popups, Goals, Tag Manager) | Mapping required | Client-side tracking and popup configurations live in Altcraft's Web Layer module. These are independent of Profile data and must be re-implemented in the destination platform's tag management or equivalent module. |
Gotchas
What to watch for in Altcraft migrations
Issues we've hit on past Altcraft migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| High | Profile-count pricing means database size drives the bill |
| High | Automation Scenarios do not export as portable logic |
| Medium | API developer guide returns HTTP 301, blocking programmatic discovery |
| Medium | Private Cloud and on-premise use separate support contracts |
| Medium | Control Group assignment is Profile-ID dependent |
Leaving Altcraft?
Where Altcraft customers move next
12 destinations Altcraft can migrate to.
How a Altcraft migration works
Four steps, Altcraft-specific
Connect
Token-based — API token passed in request body or via Authorization: Bearer header. Tokens are generated in Settings → Tokens by master users with configurable role and object-group scopes. into Altcraft. Scopes limited to read-only on the data we move.
Map
We translate Altcraft-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Altcraft quirks before production.
Migrate
Full migration with Altcraft rate-limit handling. Rollback available throughout.
FAQ
Altcraft migration FAQ
Answers to the questions buyers ask most during Altcraft migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Altcraft migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Altcraft.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Altcraft setup and destination — written quote back within a business day.