CRM migration
Field-level mapping, validation, and rollback between VaultRE and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
VaultRE
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between VaultRE and Nutshell.
Complexity
BStandard
Timeline
24–48 hours
Overview
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.
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 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)
Nutshell
Person
1:1VaultRE 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
Nutshell
Company
1:1VaultRE 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
Nutshell
Custom fields on Person / Company
1:1VaultRE 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
Nutshell
Deal
1:1VaultRE 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)
Nutshell
Activity
1:1VaultRE 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)
Nutshell
Custom field on Person
1:1VaultRE 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)
Nutshell
Custom field on Person / Company
1:1VaultRE 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
Nutshell
File
1:1VaultRE 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
Nutshell
User (via email match)
1:1VaultRE 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)
Nutshell
No equivalent
1:1VaultRE 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
Nutshell
No equivalent
1:1VaultRE 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
Nutshell
No equivalent
1:1VaultRE 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.
| VaultRE | Nutshell | Compatibility | |
|---|---|---|---|
| Contact (Person) | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Property | Custom fields on Person / Company1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Activity (Call / Email / Meeting / Note) | Activity1:1 | Fully supported | |
| Custom database field (Contact Field Group) | Custom field on Person1:1 | Fully supported | |
| Custom database field (Property Field Group) | Custom field on Person / Company1:1 | Fully supported | |
| Attachment / File | File1:1 | Fully supported | |
| Owner / Staff | User (via email match)1:1 | Fully supported | |
| Integration (Pricefinder, CoreLogic) | No equivalent1:1 | Fully supported | |
| Automation / Workflow trigger | No equivalent1:1 | Fully supported | |
| Trust Account / Ledger | 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.
VaultRE gotchas
VaultRE is listed as Out of Business
CSV export is the only documented migration path
Trust accounting varies by Australian state
Custom field type constraints may limit destination mapping
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 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.
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.
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.
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.
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
VaultRE
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 VaultRE 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
VaultRE: Not publicly documented in the public API docs.
Data volume sensitivity
VaultRE doesn't expose a bulk API — REST + parallelization used for high-volume runs.
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 VaultRE to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your VaultRE 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 VaultRE
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.