Migrate from APRO CRM to Nutshell

APRO contacts map directly to Nutshell People records. Nutshell uses 'People' in the UI while the API uses 'Contact' — we map to the API entity type. APRO contact properties including job title, phone, email, and address fields migrate as Nutshell standard or custom Person fields.

APRO company records (including property-owner profiles) map to Nutshell Company records. The API entity name is 'Account' while the UI shows 'Companies' — we map to the API entity. Owner profiles from APRO that represent individual property owners become Nutshell Companies or optionally People records based on whether the owner has deals associated.

APRO properties and listings have no direct Nutshell equivalent. We migrate property records as Nutshell Companies with a property-type custom field and address data in Company address fields. Listing-specific data (price, property type, status) becomes custom fields on the Company record. Automatch rules are documented for manual rebuild in Nutshell.

APRO deals map to Nutshell Deals. Nutshell Deals link to one or more People (contacts) and optionally to a Company (account). Deal amount, stage, and expected-close date map directly. APRO deal-stage names map to Nutshell pipeline stage values via value-mapping.

APRO pipelines map to Nutshell pipelines on a one-to-one basis. Each APRO pipeline becomes a separate Nutshell pipeline with identical stage structures. Stage names and probabilities transfer via value-by-value mapping to preserve deal-scoring logic. Nutshell's pipeline configuration is established in the target environment before data migration begins, ensuring pipeline structures are ready to receive records.

APRO call logs, emails, and notes map to Nutshell Activities. Nutshell stores activities on the Person record with type, subject, body, and timestamps. APRO IP telephony call records that live in APRO's telephony layer are migrated as Call activities if the data is accessible via export. Website chat transcripts migrate as Note activities.

APRO agent profile fields (agent ID, team assignment, automatch preferences) have no Nutshell standard equivalent. We create custom fields on Nutshell Person records: Agent_ID__c, Team_Assignment__c, and Automatch_Preferences__c as text fields. These fields preserve the source data for reference and provide context for rebuilding automatch logic in Nutshell's workflow builder or saved filters.

APRO property presentation template references migrate as a custom field on the Company record. Template URL or identifier stored in Presentation_Template__c for reference and reconnection. The actual template files require separate export from APRO and re-hosting in Nutshell's file management system, with the file reference URL captured in the custom field.

APRO attachments and files (property images, documents, contracts) are exported and re-uploaded to Nutshell's file storage. File size limits apply (Nutshell default 50MB per file). Inline images in notes are downloaded and re-hosted. Files are associated to the parent record (Person or Company) after upload.

APRO owner IDs resolve to Nutshell Users by email address match. Unmatched owners are flagged before migration — your team either creates Nutshell user accounts first or assigns records to a fallback owner. Nutshell user records are not migrated; only the OwnerId lookup on migrated records is updated.

APRO website visitor statistics, live chat transcripts from APRO's embedded chat, and call-from-website data live in APRO's integration layer and do not migrate. We document the integration setup for rebuilding in Nutshell using Nutshell's native web forms, live chat integration, or third-party visitor intelligence tools.

APRO custom automation algorithms (automatched listing rules, business-process sequencing) do not have a Nutshell equivalent and cannot be migrated. We export the algorithm definitions as documentation so your team can rebuild equivalent logic in Nutshell's workflow builder or sequences (Pro plan).