CRM migration

Migrate from VaultRE to Nutshell

Field-level mapping, validation, and rollback between VaultRE and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

VaultRE logo

VaultRE

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between VaultRE and Nutshell.

Complexity

BStandard

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

VaultRE is a real estate-specific CRM built for Australian and New Zealand agencies, combining contact management with property listings, multi-office support, and event-driven automation. VaultRE models buyers, sellers, tenants, and landlords as contact_types attached to People records, with properties stored as separate first-class objects linked to contacts via associations. Custom database fields are organized into field groups and support date, checkbox, text, and drop-down types. Nutshell uses a standard SMB CRM model: People, Companies (Accounts), and Deals with customizable pipelines and stages, plus integrated email marketing, calling, web chat, and SMS. Nutshell has no native property object—property data must live in custom fields on People or Company records. FlitStack AI migrates contacts, companies, deals, custom fields, activities, and property data into Nutshell via the Nutshell REST API or CSV import. Workflows, automations, and third-party integrations (Pricefinder, CoreLogic) do not migrate and must be rebuilt. We run a sample migration with field-level diff before the full cutover, preserve original create dates as custom fields, and match owners by email.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

VaultRE logo

VaultRE

What's pushing teams away

  • PitchBook reports VaultRE's status as Out of Business, and customers have reported outages with no clear resolution timeline on the official Facebook page.
  • The platform is Australia and New Zealand specific, limiting its usefulness for agencies expanding into other markets that require multi-currency or international property management.
  • Customers cite frustration with automation triggers being rigid in certain workflows, particularly around conditional logic for property status changes.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How VaultRE objects map to Nutshell

Each row shows how a VaultRE 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.

VaultRE

Contact (Person)

maps to

Nutshell

Person

1:1
Fully supported

VaultRE contacts migrate as Nutshell People. The primary contact fields (name, email, phone, address) map directly. VaultRE contact_type values (Buyer, Seller, Tenant, Landlord) migrate as a custom Selection field on the Person record. Nutshell People have no native role-type field.

VaultRE

Company

maps to

Nutshell

Company

1:1
Fully supported

VaultRE companies map to Nutshell Companies. Standard fields (name, website, address, industry) migrate directly. VaultRE parent-company hierarchy is preserved using a parent_company custom lookup field in Nutshell since Companies do not have a native parent-link field. If a company has no parent in VaultRE, we leave the custom lookup empty, preserving the top‑level structure as is.

VaultRE

Property

maps to

Nutshell

Custom fields on Person / Company

1:1
Fully supported

VaultRE property records have no direct Nutshell equivalent. We split property data: address fields migrate to Company records or Person address fields; listing-specific fields (price, bedrooms, status) become custom fields on the associated Person or Company. One property can appear against multiple contacts.

VaultRE

Deal

maps to

Nutshell

Deal

1:1
Fully supported

VaultRE deals map to Nutshell Deals. Deal name, amount, stage, and close date migrate directly. VaultRE pipeline names become Nutshell pipeline names. Stage values are mapped one-to-one. Owner resolves by email match to Nutshell users. If a deal has no owner in VaultRE, it is assigned to a default Nutshell user that you designate during setup.

VaultRE

Activity (Call / Email / Meeting / Note)

maps to

Nutshell

Activity

1:1
Fully supported

VaultRE call, email, meeting, and note activities migrate as Nutshell Activities with original timestamps and owners preserved. Activity type is stored in a custom activity_type field in Nutshell. Parent record links (contact or company) are preserved via Nutshell's activity association model.

VaultRE

Custom database field (Contact Field Group)

maps to

Nutshell

Custom field on Person

1:1
Fully supported

VaultRE contact field groups (e.g., Source Details, Buyer Preferences) map to individual custom fields on Nutshell Person. Each VaultRE field within a group becomes a separate Nutshell custom field. Drop-down fields with up to 30 options map to Nutshell Selection fields.

VaultRE

Custom database field (Property Field Group)

maps to

Nutshell

Custom field on Person / Company

1:1
Fully supported

VaultRE property field groups map to custom fields on the related Person or Company record. A VaultRE field group named Property Details with fields like listing_status and bedrooms_per_property becomes individual custom fields in Nutshell. Fields are placed on the record type that holds the property reference.

VaultRE

Attachment / File

maps to

Nutshell

File

1:1
Fully supported

VaultRE file attachments on contacts, companies, or properties are downloaded and re-uploaded to Nutshell's file storage. File size limits (25 MB per file in Nutshell) are enforced. Inline images in notes are extracted and rehosted as Nutshell Files. Files exceeding the 25 MB limit are flagged for manual upload after migration.

VaultRE

Owner / Staff

maps to

Nutshell

User (via email match)

1:1
Fully supported

VaultRE staff records map to Nutshell users by email address. Nutshell requires each user to have a unique email. Staff without a matching Nutshell account are flagged before migration and assigned to a fallback user or held for review. You can also choose to create new Nutshell accounts for any unmatched staff before the migration runs, ensuring continuity of ownership.

VaultRE

Integration (Pricefinder, CoreLogic)

maps to

Nutshell

No equivalent

1:1
Fully supported

VaultRE integrations with Pricefinder and CoreLogic for property data enrichment have no Nutshell equivalent. They must be disconnected in VaultRE and re-established as new integrations or manual workflows after cutover. We document the active integrations during audit. If you plan to continue using these services, you will need to configure them again in their respective platforms post‑migration.

VaultRE

Automation / Workflow trigger

maps to

Nutshell

No equivalent

1:1
Fully supported

VaultRE event-driven automation triggers do not transfer to Nutshell. Nutshell uses stage-based sequences, not event-condition-action triggers. We export VaultRE workflow definitions as a rebuild reference. The rebuild is a separate service not included in data migration pricing. You can rebuild the logic using Nutshell’s workflow builder or integrate with Zapier, Make, or other automation platforms after migration.

VaultRE

Trust Account / Ledger

maps to

Nutshell

No equivalent

1:1
Fully supported

VaultRE trust account and financial ledger entries are outside Nutshell's CRM scope. These records are excluded from the migration. Teams requiring trust accounting in Nutshell must use a dedicated property management or accounting integration. FlitStack AI can provide a CSV export of the trust ledger data for import into your chosen accounting platform.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

VaultRE logo

VaultRE gotchas

High

VaultRE is listed as Out of Business

High

CSV export is the only documented migration path

Medium

Trust accounting varies by Australian state

Medium

Custom field type constraints may limit destination mapping

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • VaultRE multi-office accounts require Nutshell restructuring

    VaultRE's unlimited-offices-per-account model has no native equivalent in Nutshell. When migrating from a multi-office VaultRE setup, each office's contacts, companies, and deals must be assigned to a specific Nutshell account or structured using a custom office identifier field. Teams that need consolidated reporting across offices will need a Nutshell Power-up or a post-migration reporting integration. FlitStack AI documents the office structure during audit and delivers an office-mapping plan before data lands in Nutshell.

  • VaultRE contact_types map as a custom field with manual rebuild needed for role-based workflows

    VaultRE assigns contact_types (Buyer, Seller, Tenant, Landlord) to each contact, and these types can coexist on a single record. Nutshell has no native role-type field on People. We migrate the contact_type as a custom Selection field, but VaultRE workflows that fired based on contact_type changes (e.g., when a Tenant is assigned, create a rental checklist) have no Nutshell equivalent and must be rebuilt as stage-based sequences or tasks. The contact_type field values are preserved for filtering and reporting but do not trigger automation in Nutshell.

  • VaultRE property records must be decomposed into custom fields

    VaultRE properties are first-class objects with address, status, price, bedrooms, bathrooms, parking, and available date. Nutshell has no Property object. Each property attribute must be mapped to a custom field on the related Person or Company record. For agencies with hundreds of active listings, this means dozens of custom fields per record type. We audit the property field groups during discovery and create the custom field structure in Nutshell before migration so property data lands cleanly in the correct locations.

  • VaultRE automation triggers do not transfer and must be rebuilt manually

    VaultRE's event-driven automation engine (triggers that fire when conditions are met, not just on stage entry) has no Nutshell equivalent. Nutshell sequences are stage-based—they start when a lead enters a pipeline stage, not when arbitrary conditions change. Any VaultRE automation that relies on contact_type changes, property listing events, or date-based reminders must be exported as a definition document and rebuilt in Nutshell's automation tools after cutover. During the discovery audit, FlitStack AI captures each automation rule's trigger conditions, actions, and target records. This capture becomes a specification sheet for your Nutshell administrator to reconstruct the workflow using Nutshell’s workflow builder or Zapier integration.

  • VaultRE integrations with Pricefinder and CoreLogic cannot be migrated

    VaultRE integrates with Pricefinder for property valuation and CoreLogic for property data enrichment. These integrations are VaultRE-side connections that have no equivalent in Nutshell. After cutover, teams must establish new data-enrichment integrations (if available) or revert to manual property research. The active integration list is captured during the audit phase so nothing is missed at cutover. If you rely on Pricefinder or CoreLogic for real-time property valuations or market reports, you should evaluate Nutshell-compatible alternatives or third‑party services such as Corefact, Real Estate Business (REB), or API‑based valuation tools after migration.

Migration approach

Six steps for a successful VaultRE to Nutshell data migration

  1. Audit VaultRE data model and field groups

    FlitStack AI exports VaultRE data via the Backup/Export tool and reviews the full field group structure in Settings > Database Fields. We catalog every contact field group, property field group, custom field type, drop-down option count, and office configuration. This audit produces the field mapping plan that drives all subsequent steps. We also capture any custom validation rules, required fields, and multi‑value dropdowns that affect how data can be imported into Nutshell. The result is a detailed data dictionary that both you and FlitStack AI can reference throughout the project.

  2. Build Nutshell custom fields and pipeline structure

    While the audit runs, we create Nutshell custom fields to receive VaultRE data. Custom fields for contact_type, vaultre_id, original_create_date, office, and all property attributes are built on Person and Company. We also create Nutshell pipelines and stages to match VaultRE pipeline names so stage mapping is ready before the migration run. If your account already contains existing custom fields, we compare them with the VaultRE schema to avoid duplicates and reuse where possible, streamlining the field creation process.

  3. Run sample migration with field-level diff

    A representative slice of 200–500 records (contacts, companies, deals, and property records) migrates into Nutshell first. We generate a field-level diff between the VaultRE source values and the Nutshell destination values so you can verify that contact_types, property fields, stage mappings, and owner resolution are correct before the full run commits. The diff highlights any mismatches in field types, missing required values, or unexpected nulls, allowing you to adjust the mapping before the production migration.

  4. Execute full migration with delta-pickup window

    The full migration runs against Nutshell via the API. A delta-pickup window (24–48 hours) captures any VaultRE records created or modified during cutover so Nutshell reflects the final state at go-live. Owner resolution by email is applied across all records; unmatched owners are flagged for manual assignment. Throughout the run, FlitStack AI logs each API call, record ID, and any errors, giving you a full audit trail to trace any issues after the migration completes.

  5. Deliver audit log and reconciliation report

    FlitStack AI delivers a full audit log of every record operation (create, update, link) plus a before-and-after record count by object type. You can reconcile Nutshell record counts against VaultRE source extracts to confirm completeness. One-click rollback is available if reconciliation reveals data integrity issues. The report also highlights any records that could not be migrated due to schema mismatches, so you can address them manually or adjust the mapping for a future sync.

Platform deep dives

Context on both ends of the pair

VaultRE logo

VaultRE

Source

Strengths

  • Purpose-built for Australia/New Zealand real estate, with a unified contact model that treats one person as buyer, seller, tenant, and landlord without duplicating records.
  • Single property record can carry both sales and rental statuses simultaneously, matching how AU/NZ agencies operate across the lifecycle of a listing.
  • Open API-first architecture (now under MRI Software as MRI Vault) for integration with portals, accounting, and marketing tools.
  • Trusted by more than one in three real estate offices across Australia and New Zealand, providing strong vendor stability and ANZ-specific portal support.
  • Native Xero trust accounting integration covers commission disbursements, property management trust balances, and end-of-month reconciliation without external middleware.

Weaknesses

  • Property loading and contact-database sync are reported as slow during high-traffic moments like open-home check-ins, slowing the agent workflow.
  • Contact entry takes more steps than competing CRMs and the platform creates duplicates if details are not entered carefully, requiring routine deduplication.
  • No native deal-stage tracker for moving a transaction through pipeline stages, which is standard in horizontal CRMs.
  • Branded MRI Vault rather than VaultRE post-acquisition, with rebrand transitions affecting documentation, integrations, and partner ecosystem references.
  • Mobile app reviewers report intermittent sync delays on iOS/Android during peak listing activity, affecting on-the-go updates.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across VaultRE and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    VaultRE: Not publicly documented in the public API docs.

  • Data volume sensitivity

    B

    VaultRE doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your VaultRE to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about VaultRE to Nutshell data migrations

Answers to the questions buyers ask most during VaultRE to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your VaultRE to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most VaultRE-to-Nutshell migrations complete within 24–48 hours of clock time for setups under 10,000 total records. Larger datasets with property records, custom field groups, and multi-office configurations extend to 3–5 days. Mapping VaultRE field groups to Nutshell custom fields and planning property-data placement are the longest planning steps. The initial planning phase includes a data audit, custom field creation in Nutshell, and a sample migration to verify mapping. The actual cutover run is typically short, but the surrounding setup and reconciliation add to the timeline. FlitStack AI provides a clear schedule before work begins.

Adjacent paths

Related migrations to explore

Ready when you are

Move from VaultRE.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day