Migrate from Adobe Marketo Engage to Nutshell

Discovery and scoping audit

We audit the source Marketo instance for Person count, Company count, Opportunity count, Custom Object definitions, Static List memberships, Program count and channel assignments, and Activity record volume by type. We identify any SOAP API integrations requiring REST migration before the July 31, 2026 SOAP deprecation deadline. We pair this with a Nutshell tier assessment ($16-$52 per user per month) and confirm the custom field creation capacity against the customer's field inventory. The discovery output is a written migration scope document with record counts, dependency map, and Nutshell tier recommendation.

Custom field schema creation in Nutshell

We map every Marketo Person and Company custom field to a Nutshell custom field on Contact or Account, applying Nutshell's supported field types (text, number, date, picklist, checkbox, currency). Custom Object fields are flattened and assigned to the parent Contact or Account record. We configure the Nutshell custom field schema in the customer's live Nutshell account (or a sandbox if available) before any data import begins. Any fields that cannot be mapped due to Nutshell's type constraints are flagged with a transformation note.

Static List extraction and Contact deduplication

We export all Marketo Static Lists with their Person memberships and the full Person record set via Bulk Extract API (for large sets) or REST paging (for smaller sets). We deduplicate by email and marketoGUID combination, flagging duplicates for the customer to resolve before import. Static List membership is preserved as a mapping table (Contact email to List name) for Nutshell List creation.

Record import in dependency order

We import into Nutshell in dependency order: Accounts (from Marketo Companies), then Contacts (with AccountId resolved for linked Companies), then Leads (from Marketo Opportunities, linked to Account), then Custom Field data, then List memberships. Owner resolution uses email match against Nutshell User email. Each phase emits a row-count reconciliation report showing records attempted, imported, skipped (dupe), and errored.

Activity history extraction and Note migration

We extract Marketo standard Activities (email opens, form fills, page visits, score changes, link clicks) via the Bulk Activity API in type-batched chunks. Each activity type is processed separately to respect rate limits. Activities write as Nutshell Notes with a structured prefix capturing activity type, key attributes, and ISO timestamp. Bulk Extract is used for datasets over 50,000 activity records to minimize REST API call consumption. The output is a per-day reconciliation log showing activities extracted versus Notes written.

Program, Campaign, and Scoring inventory delivery

We deliver the written inventory of Marketo Smart Campaigns (name, Smart List filters, trigger conditions, flow steps), Programs (name, channel, tags, period costs, member count), and Scoring Models (field, operator, grade values, change increments) as a structured JSON and markdown document. This document is the handoff artifact for the customer's admin to use when rebuilding campaign logic in Nutshell. We do not rebuild these artifacts inside Nutshell as part of the migration scope.

Final reconciliation and cutover

We run a delta migration for any records created or modified in Marketo during the migration window, then enable Nutshell as the system of record. We deliver a final reconciliation report comparing source record counts against destination record counts for each object type. We support a 72-hour hypercare window for immediate data quality issues. Workflow rebuild, Sequence rebuild, and Nutshell admin training are outside migration scope and are handled as separate engagements.