Migrate from Actito to Microsoft Dynamics 365 Sales

Actito Custom Tables lack direct Microsoft Dynamics 365 Sales equivalent

Actito's Custom tables with user-defined schemas and Profile-linked relationships do not have a native Microsoft Dynamics 365 Sales standard object. We map them to custom Dataverse entities, but this requires pre-designing the Dataverse schema (custom tables, columns, lookups, option sets) before any data loads. Migrations that skip schema design result in custom table data landing as text blobs with no relational integrity. We address this by inspecting the Actito custom table definitions during scoping, creating the Dataverse custom table schema in a Sandbox first, validating the relationship resolution, and only then loading production data.

Scenario automation does not migrate to Microsoft Dynamics 365 Sales

Actito Scenarios are event-triggered automation workflows with branching logic and multi-step action sequences. Microsoft Dynamics 365 Sales does not have a native scenario equivalent; equivalent logic requires Power Automate flows or Microsoft Dynamics 365 Sales Processes, which are separate products requiring separate configuration. We do not migrate Scenarios as executable code. We deliver a written scenario inventory document for each active Actito Scenario, documenting the trigger conditions, branching rules, action steps, and recommended Power Automate or Microsoft Dynamics 365 Sales Process equivalent. The customer's admin rebuilds these post-migration.

Actito API rate limit of 100 calls/min constrains bulk export

Actito's API enforces a hard limit of 100 calls per minute and a maximum of 5 concurrent requests per licence. For large profile sets or multi-table exports, we use Actito's ETL export jobs with CSV and GZIP compression rather than looping API calls. ETL jobs retrieve archives via Actito's file transfer API and decompress before loading. We schedule large exports during off-peak hours and chunk the work into manageable batches. We recommend requesting a temporary rate-limit increase through Actito support before migration begins if the dataset exceeds 50,000 records.

Push notification migration excludes campaign interaction history

When migrating push subscribers from Actito, device information and opt-in status transfer but no historical push campaign performance data (opens, deliveries, clicks) is available via the Actito API. We migrate only the device token table and subscription metadata, and flag that push campaign analytics will reference Microsoft Dynamics 365 Sales or the replacement push channel data only from the go-live date forward. We advise exporting and archiving all push campaign reports from Actito before the cutover date.

Microsoft Dynamics 365 Sales entity security model requires upfront Business Unit design

Microsoft Dynamics 365 Sales uses Business Units and Teams to enforce data security and segregation. Actito's entity partitioning (B2C/B2B co-existence) maps to this model but requires designing the Business Unit hierarchy before record import. If the destination org uses a flat Business Unit structure, records from Actito entities without a corresponding Business Unit land in the default Business Unit, potentially causing data visibility issues for teams that expect segmented access. We map Actito entities to Business Units or Teams during scoping and validate security role assignments in the Sandbox before production migration.