CRM migration
Field-level mapping, validation, and rollback between AscendixRE and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
AscendixRE
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between AscendixRE and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
AscendixRE is a commercial real estate CRM built on the Salesforce platform, storing contacts and companies as Salesforce standard objects alongside CRE-specific custom objects for Properties, Listings, Leases, Commissions, and Inquiries. Nutshell uses a flat data model with People (analogous to Contacts), Companies, Leads, Deals, and Activities — it supports custom fields on People, Companies, and Leads but has no custom object capability. The structural gap between these models is the central challenge of the migration: CRE-specific objects that exist as separate Salesforce custom objects in AscendixRE must be collapsed into Nutshell custom fields or Notes attached to the nearest standard object. We map AscendixRE Contacts to Nutshell People, AscendixRE Companies to Nutshell Companies, and AscendixRE Deals to Nutshell Deals with pipeline stage mapping. Activity history (calls, emails, meetings, notes) migrates as Nutshell Activities. We preserve original create and modification timestamps by storing them in custom fields. Owner resolution runs via email match against Nutshell users. Workflows, automation rules, Salesforce sharing rules, page layouts, and permission sets do not migrate — we export these definitions as JSON for your Nutshell admin to rebuild using Nutshell's automation tools. The migration mechanism uses AscendixRE's Salesforce Data Export (up to 50,000 records per operation) and Nutshell's JSON-RPC API for import, with a 24–48 hour delta-pickup window capturing any in-flight changes during cutover.
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.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a AscendixRE object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
AscendixRE
Contact
Nutshell
Person
1:1AscendixRE stores contacts as Salesforce standard Contacts. Nutshell People object holds the equivalent data. Direct field mapping covers name, email, phone, title, mailing and shipping addresses, and any custom contact fields. Owner resolution maps the Salesforce OwnerId to a Nutshell user by matching the owner’s email address, and original create and modification timestamps are preserved in dedicated custom fields.
AscendixRE
Account
Nutshell
Company
1:1AscendixRE Company records map to Nutshell Companies. Website, industry, employee count, and annual revenue migrate as direct fields or value‑mapped picks where Nutshell’s pick‑list differs from Salesforce’s. Billing address components (street, city, state, zip, country) are mapped to the Nutshell address field, and any multi‑location hierarchy is collapsed to a single parent‑company reference, with the top‑level company retained as the parent.
AscendixRE
Opportunity / Deal
Nutshell
Deal
1:1AscendixRE deals backed by Salesforce Opportunities map directly to Nutshell Deals. Deal name, amount, close date, stage, owner, and description carry over. Stage mapping runs value-by-value from Salesforce stage names to Nutshell pipeline stage names configured in your Nutshell account.
AscendixRE
Task / Event
Nutshell
Activity
1:1AscendixRE logged calls, emails, meetings, and tasks migrate as Nutshell Activities. Original timestamps, owners, and the parent record link (Person or Deal) are preserved, along with any file attachments or meeting notes. The Activity type (Call, Email, Meeting, Note) maps to Nutshell’s activity type field, and for multi‑participant events, each attendee is recorded in the activity’s description or a linked Person reference.
AscendixRE
Lead
Nutshell
Lead
1:1AscendixRE may contain Salesforce Leads for uncompleted prospects. These map directly to Nutshell Leads, preserving lead status, source, rating, and any custom fields such as lead score or referral channel. If a lead is unqualified, it can either be imported as a Person record for immediate follow‑up or remain as a Nutshell Lead for further nurturing, and any duplicate detection based on email is applied during import.
AscendixRE
Property__c (custom object)
Nutshell
Company + Custom Fields
1:1AscendixRE's Property__c object has no direct Nutshell equivalent, so property address, type, square footage, zoning, and status fields are migrated as custom fields on the linked Nutshell Company record. If a company owns multiple properties, each property’s data is stored in a separate set of custom fields and identified by a property‑ID suffix, preserving the relationship to the relevant contacts and listings while maintaining a clear separation of property details.
AscendixRE
Listing__c (custom object)
Nutshell
Deal + Custom Fields
1:1Listing__c records with availability details map to Nutshell Deals using a 'Listing' type tag and custom fields for listing price, status, available square footage, and a property reference. When a property has multiple listings, each appears as a separate Deal, and status transitions such as Active to Under Contract are recorded in the custom status field, preserving the link to the parent Company record.
AscendixRE
Lease__c (custom object)
Nutshell
Deal + Custom Fields
1:1Lease__c records migrate as Nutshell Deals with a 'Lease' type tag and custom fields for lease term, rent amount, expiration date, and tenant reference. The Deal's linked Company represents the landlord; tenant information is stored in a custom Company field.
AscendixRE
Commission__c (custom object)
Nutshell
Custom Fields on Deal + Note
1:1Commission amounts, rates, and calculation logic from AscendixRE’s Commission__c object migrate as custom fields on the associated Nutshell Deal, such as commission_rate__c and commission_amount__c. If multiple commissions exist for a single deal, each commission is stored in a separate set of custom fields and identified by a commission‑ID suffix. Detailed calculation history, including step‑by‑step breakdowns, is preserved as a Note attachment on the Deal, ensuring full audit trail.
AscendixRE
Inquiry__c (custom object)
Nutshell
Lead + Custom Fields
1:1AscendixRE inquiry records representing prospective tenant or buyer inquiries migrate as Nutshell Leads, with custom fields capturing inquiry type, property interest, budget range, and desired timeline. Source tracking fields—such as referral channel, campaign ID, or website form identifier—are preserved as Lead custom fields, and any duplicate detection based on email or phone is applied during import to prevent redundant records.
AscendixRE
Attachment / Salesforce Files
Nutshell
Files attached to Person / Company / Deal
1:1Files attached to AscendixRE records—such as PDFs, images, and lease documents—are downloaded from Salesforce Files and re‑uploaded to the corresponding Nutshell Person, Company, or Deal record, preserving original file names. Nutshell’s 25 MB per‑file limit applies; any file exceeding this size is flagged in the pre‑migration audit and can be stored in a linked Google Drive or SharePoint location with the URL recorded in the Nutshell record.
AscendixRE
Salesforce Campaign
Nutshell
No equivalent
1:1AscendixRE may use Salesforce Campaigns for marketing tracking. Nutshell has no Campaign object. Campaign membership data is preserved as a custom field on the relevant Person records for reference, but the campaign structure must be rebuilt in Nutshell's email marketing module.
| AscendixRE | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Account | Company1:1 | Fully supported | |
| Opportunity / Deal | Deal1:1 | Fully supported | |
| Task / Event | Activity1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Property__c (custom object) | Company + Custom Fields1:1 | Fully supported | |
| Listing__c (custom object) | Deal + Custom Fields1:1 | Fully supported | |
| Lease__c (custom object) | Deal + Custom Fields1:1 | Fully supported | |
| Commission__c (custom object) | Custom Fields on Deal + Note1:1 | Fully supported | |
| Inquiry__c (custom object) | Lead + Custom Fields1:1 | Fully supported | |
| Attachment / Salesforce Files | Files attached to Person / Company / Deal1:1 | Fully supported | |
| Salesforce Campaign | No equivalent1: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.
AscendixRE gotchas
Annual billing with no published monthly option
Stacking plan visual data does not migrate as a rendered layout
Mailchimp list membership lives outside Salesforce
Custom object schema varies by org and requires pre-migration audit
Bulk export cap of 50,000 records per admin-defined action
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Audit AscendixRE schema and configure Nutshell custom fields
We connect to your AscendixRE Salesforce instance and extract the full object and field inventory — including all custom objects (Property__c, Listing__c, Lease__c, Commission__c, Inquiry__c), custom fields, and pick-list values. We then create the equivalent custom fields in your Nutshell account for each AscendixRE field that has no direct Nutshell equivalent. We configure pipeline stages in Nutshell to match your AscendixRE deal pipeline stage names, and we map pick-list values (property type, listing status, lease status) to Nutshell custom field options. This step also includes email-matching your AscendixRE Salesforce users to existing or new Nutshell users so owner resolution is ready before data moves.
Export data from AscendixRE in dependency order
We extract AscendixRE data via Salesforce Data Export (up to 50,000 records per operation, admin-configurable per-user export limits noted in the AscendixRE admin guide). We export in dependency order: Companies first (to resolve AccountId), then People/Contacts (to resolve relationships), then Deals/Opportunities (with stage and owner mapping applied), then Activity history, then custom object records (Properties, Listings, Leases, Commissions, Inquiries) mapped into the appropriate standard Nutshell objects. The Salesforce Owner Alias columns (updated in AscendixRE 1.29) are validated against the actual export schema to ensure owner data exports correctly.
Run sample migration and field-level diff
A representative slice of records — typically 100–500 across People, Companies, Deals, and a sample of each custom object type — migrates into Nutshell first. We generate a field-level diff report comparing source values against destination values for every mapped field, including custom fields on CRE objects. You review the diff to confirm stage mapping, custom field data integrity, property-deal associations, and owner resolution. We iterate on any mapping changes before the full migration commits. This step also surfaces any files exceeding Nutshell's 25MB per-file limit for separate handling.
Execute full migration with delta-pickup cutover
The full record set migrates into Nutshell via the Nutshell JSON-RPC API. During the migration window, your team continues working in AscendixRE — FlitStack AI uses scoped read access only, causing zero disruption. A delta-pickup window of 24–48 hours after the initial load captures any records created or modified in AscendixRE during cutover, ensuring Nutshell reflects the final state of your CRM at go-live. Our audit log records every operation. If reconciliation fails, one-click rollback reverts the Nutshell instance to its pre-migration state.
Platform deep dives
AscendixRE
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across AscendixRE and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
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
AscendixRE: Salesforce API limits apply — varies by Salesforce edition (Enterprise: 1,000 API calls/min per org; Unlimited: 2,000; Performance: 5,000).
Data volume sensitivity
AscendixRE 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 AscendixRE to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your AscendixRE to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave AscendixRE
Other ways to arrive at Nutshell
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.