CRM migration
Field-level mapping, validation, and rollback between Advance Practice Management Suite and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Advance Practice Management Suite
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Advance Practice Management Suite and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Advance Practice Management Suite is a healthcare-dedicated platform centered on patient records, appointment scheduling, medical billing, and practice-level reporting. When practices move to Nutshell, the shift is from a clinical-vertical tool to a horizontal CRM focused on sales pipeline management, contact organization, and team activity tracking. FlitStack AI handles this transition by mapping Advance Practice Management Suite patient contacts to Nutshell People, practice companies to Nutshell Companies, open billing cases or service agreements to Nutshell Deals, and activity history to Nutshell Activities. Custom fields configured in Advance Practice Management Suite — such as specialty codes, payer IDs, or appointment type tags — migrate as Nutshell custom fields on the relevant object. The migration runs against Nutshell's JSON-RPC API using scoped read access on the source, with a 24–48-hour delta pickup window to capture any records modified during the cutover. Workflows, billing rules, scheduling templates, and payer-specific automations in Advance Practice Management Suite have no equivalent in Nutshell and must be rebuilt manually after migration.
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 Advance Practice Management Suite 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.
Advance Practice Management Suite
Patient
Nutshell
Person
1:1Advance Practice Management Suite patient records map directly to Nutshell People. The patient's first name, last name, email, phone, and address fields transfer as-is. Custom fields on the patient record (specialty codes, referring provider, insurance tier) migrate as Nutshell custom fields on the Person object. Original create dates are preserved in a custom datetime field since Nutshell's system-created date reflects migration time.
Advance Practice Management Suite
Practice / Employer Group
Nutshell
Company
1:1Advance Practice Management Suite stores the practice or employer group name, address, phone, and taxonomy code. These map to Nutshell Company fields: name, address, phone, and website. Taxonomy and specialty codes migrate as Nutshell custom fields on the Company record. Parent-child practice relationships (if the group has satellite locations) map to Nutshell's parent company field.
Advance Practice Management Suite
Lead / Referral Source
Nutshell
Lead
1:1Referral sources tracked as lead records in Advance Practice Management Suite — referring physician, hospital, insurance group — map to Nutshell Leads. Fields include name, organization, contact info, and source attribution. Status and rating values are mapped via value_mapping to match Nutshell's lead status pick-list options.
Advance Practice Management Suite
Billing Case / Service Agreement
Nutshell
Deal
1:1Advance Practice Management Suite billing cases and service agreements contain an amount, payer, status, and open/closed date. These translate to Nutshell Deals: name from case description, amount from billed total, stage from status (open=b Qualitative In Progress, closed_paid=Closed Won, denied=Closed Lost), close date from last activity date. Pipeline mapping is determined by case type — evaluation cases route to one pipeline, service agreements to another.
Advance Practice Management Suite
Appointment / Encounter
Nutshell
Activity (Task or Event)
1:1Appointments and clinical encounters carry a date, duration, type, provider, and patient link. Each maps to a Nutshell Activity: appointments with a duration become Events with start/end times; encounter types without a time block become Tasks with the description in the subject. Provider and patient links are preserved via association to the relevant Nutshell Person record.
Advance Practice Management Suite
Insurance / Payer Record
Nutshell
Custom Field on Company or Person
1:1Advance Practice Management Suite insurance records contain payer name, policy number, group number, and coverage tier. Since Nutshell has no native payer object, these fields migrate as custom text fields on the related Nutshell Company (employer group) or Person (patient) record. Multi-plan patients may require a custom field group to store all active payer associations.
Advance Practice Management Suite
Custom Field — Specialty Code
Nutshell
Custom Field on Person
1:1Advance Practice Management Suite patient records frequently contain specialty codes, condition flags, or referral tags unique to the practice. These map to Nutshell custom fields on the Person object. We create the custom field definition in Nutshell before migration and populate values during the load phase. Required-field enforcement is disabled until migration completes to avoid rejection of records with missing legacy values.
Advance Practice Management Suite
Clinical Note / SOAP Note
Nutshell
Note on Person
1:1Clinical notes attached to a patient record migrate as Nutshell Notes linked to the corresponding Person. Rich-text formatting is preserved where the source export format supports it. Note metadata (author, created date) is stored in the Note record. Note that Nutshell Notes support plain text and basic HTML; highly formatted SOAP notes may require manual review post-migration.
Advance Practice Management Suite
Attachment / Document
Nutshell
File attachment on Person or Deal
1:1Documents attached to patient records — consent forms, imaging referrals, claim documents — are downloaded from Advance Practice Management Suite and re-uploaded to the corresponding Nutshell Person or Deal record as file attachments. File size limits and format compatibility are checked during the sample migration phase. Files exceeding Nutshell's attachment size limit are flagged for manual download reference.
Advance Practice Management Suite
User / Provider
Nutshell
User in Nutshell
1:1Providers and staff users in Advance Practice Management Suite are matched to Nutshell users by email address. Unmatched users are flagged before migration — your team either creates the Nutshell account first or assigns records to a fallback owner. Provider name and credentials are preserved in a custom field on the user record for reference.
Advance Practice Management Suite
Workflow / Automation
Nutshell
None
1:1Appointment reminders, recall sequences, billing triggers, and payer-rule automations in Advance Practice Management Suite have no equivalent in Nutshell. These must be rebuilt manually in Nutshell's sequence and task-automation tools post-migration. We export the Advance Practice Management Suite workflow definitions as a structured reference document to assist your team during the rebuild phase.
Advance Practice Management Suite
Report / Dashboard
Nutshell
None
1:1Healthcare practice reports — claim denial rates, payer mix, provider productivity — do not map to Nutshell's sales reporting framework. The underlying data migrates; reports and dashboards must be rebuilt manually using Nutshell's built-in reporting tools or a connected BI tool. Claims and billing data preserved in Nutshell custom fields can be used to construct basic payer-level reports post-migration.
| Advance Practice Management Suite | Nutshell | Compatibility | |
|---|---|---|---|
| Patient | Person1:1 | Fully supported | |
| Practice / Employer Group | Company1:1 | Fully supported | |
| Lead / Referral Source | Lead1:1 | Fully supported | |
| Billing Case / Service Agreement | Deal1:1 | Fully supported | |
| Appointment / Encounter | Activity (Task or Event)1:1 | Fully supported | |
| Insurance / Payer Record | Custom Field on Company or Person1:1 | Fully supported | |
| Custom Field — Specialty Code | Custom Field on Person1:1 | Fully supported | |
| Clinical Note / SOAP Note | Note on Person1:1 | Fully supported | |
| Attachment / Document | File attachment on Person or Deal1:1 | Fully supported | |
| User / Provider | User in Nutshell1:1 | Fully supported | |
| Workflow / Automation | None1:1 | Fully supported | |
| Report / Dashboard | None1: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.
Advance Practice Management Suite gotchas
Extended implementation timeline creates migration scheduling risk
Billing claim state coordination is required during cutover
Attachment export requires explicit data dump beyond standard reports
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 Advance Practice Management Suite data and define Nutshell custom fields
We extract a full data inventory from your Advance Practice Management Suite environment — patient records, company/practice records, billing cases, appointments, attachments, and all custom field definitions. We then deliver a custom field creation plan for Nutshell, specifying the field name, type (text, pick-list, date, number), and object assignment for every custom field discovered in the source. Your Nutshell admin creates these fields before the migration load phase begins.
Match providers and staff to Nutshell users by email
Nutshell requires explicit owner assignments on all records, so Advance Practice Management Suite provider and staff accounts must be matched to Nutshell users before migration begins. We resolve each source user to a Nutshell user by email address. Any provider without a matching Nutshell account appears in a pre-migration exception report — your team then either provisions the corresponding Nutshell user account first or designates a fallback owner for all their records. This step eliminates orphaned records after cutover and ensures activity history and task assignments route to the correct user in Nutshell.
Migrate People and Companies first, then Deals and Activities
Nutshell's object model requires People to be created before they can be linked to Deals (via person-company associations), and Companies before Contacts can reference them. We sequence the migration as: Companies first, then People, then Leads, then Deals with pipeline routing, then Activities linked to the correct Person or Deal records. This ordering respects Nutshell's foreign-key constraints and prevents reference errors during the load phase.
Run a sample migration and generate a field-level diff report
Before committing to the full dataset, we run a representative sample — typically 100–500 records spanning patients, companies, billing cases, and appointments — through the complete migration pipeline. We then generate a field-level diff report that compares each source field value against the corresponding populated Nutshell field. You review this diff to confirm custom field mapping accuracy, case-to-pipeline routing, insurance field population, and original timestamp preservation. Any mapping inconsistencies or data transformation issues discovered in the sample phase are corrected before the full run begins, reducing risk across the production migration.
Execute full migration with delta-pickup window and rollback plan
The full dataset migrates in sequenced batches. A 24–48-hour delta pickup window runs concurrently, capturing any records created or modified in Advance Practice Management Suite during the migration window. An audit log records every operation performed. If reconciliation reveals missing records or mapping errors, one-click rollback reverts the Nutshell instance to its pre-migration state. Your team continues working in Advance Practice Management Suite throughout cutover — the migration uses scoped read access only.
Platform deep dives
Advance Practice Management Suite
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Advance Practice Management Suite and Nutshell.
Object compatibility
2 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
Advance Practice Management Suite: Not publicly documented.
Data volume sensitivity
Advance Practice Management Suite 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 Advance Practice Management Suite to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Advance Practice Management Suite 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 Advance Practice Management Suite
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.