How long does a FotoNotes to Zoho CRM migration take?

Most FotoNotes to Zoho CRM migrations complete in 2–4 weeks for accounts with under 10,000 total records (containers, work orders, contacts) and minimal custom templates. Mid-size migrations of 10,000–50,000 records with custom work order types, active template inheritance, and photo attachments extend to 6–8 weeks. Large property portfolios like FotoNotes customers managing 18,000+ units may require 8–12 weeks, particularly if batch photo re-upload is constrained by the Zoho Standard or Professional API rate limits. The FotoNotes schema inventory (Step 1) is the longest planning step.

Will my FotoNotes workflows and assignment rules migrate to Zoho CRM?

No. FlitStack AI migrates data and schema only — FotoNotes workflows, assignment rules, notification triggers, and template inheritance logic do not transfer. Zoho CRM has its own workflow engine (Workflow Rules and Blueprint), which operates differently from FotoNotes' event-driven rule model. We export a Workflow Rebuild Reference document that lists every FotoNotes automation, its trigger conditions, and its actions so your Zoho admin can reproduce them in Zoho Blueprint or Workflow Rules after migration.

What happens to FotoNotes container types and work order templates in Zoho CRM?

FotoNotes container types (e.g., Single Family Rental, Property Inspection, Construction) become a custom pick-list field (FN_Property_Type__c) on the Account record in Zoho CRM. Work order templates and their field inheritance rules are exported as a Template Inventory Report listing every template name, its conditional fields, and which container fields cascade into child work orders. Your Zoho admin uses this report to configure Zoho Blueprint field-population rules that reproduce the inheritance logic — there is no native template inheritance in Zoho CRM, so this is a manual step post-migration.

Can FotoNotes vendor contacts and field users migrate to Zoho CRM contacts?

Yes. All FotoNotes contacts — including Vendor Admins, Vendor Field Users, and Field Workers — migrate to Zoho Contacts. The FotoNotes role type (Customer, Field User, Vendor Admin, etc.) is stored as a custom pick-list field (FN_Role_Type__c) on each Zoho Contact record. Vendor-specific permissions do not migrate; your Zoho admin assigns Zoho Profiles and Role Hierarchy access after migration using the Role Mapping Report we deliver with the migration.

What happens to inspection photos attached to FotoNotes work orders?

FotoNotes stores photos as URL references linked to work orders and containers. These URLs do not render inline in Zoho CRM. FlitStack AI downloads the original photo files from FotoNotes' storage and re-uploads them as Zoho Files attached to the corresponding Deal (work order) or Account (container) records. For large photo sets, we use Zoho's Bulk API with rate-limit pacing for your edition. The original FotoNotes photo URL is preserved as a custom text field (FN_Original_Photo_URL__c) on the Deal for reference.

Does the migration affect my FotoNotes account during cutover?

No. FlitStack AI uses scoped read access on FotoNotes — your team can continue creating work orders, updating statuses, and uploading photos in FotoNotes during the migration. A delta-pickup window of 24–48 hours after the full migration run captures any records created or modified in FotoNotes during the cutover. All FotoNotes read operations are non-destructive; we do not modify or lock your FotoNotes data during the migration process.

How are FotoNotes Customer portal users handled in Zoho CRM?

FotoNotes Customers are read-only users who can log in to a portal to view assigned projects and reports. Zoho CRM does not include a built-in read-only customer portal by default — Zoho Portal is a separate licensing add-on. We flag every FotoNotes contact with role type 'Customer' in Zoho using the FN_Role_Type__c custom field and export a Customer Access Report listing all affected contacts and their assigned containers. Your Zoho admin activates Zoho Portal and re-invites customers as portal users post-migration using this report.

FotoNotes to Zoho CRM Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

FotoNotes is a field-service platform for property inspections, work orders, and vendor management — not a CRM. Its data model centers on property Containers (parent records), Work Orders (containee inspection and maintenance tasks), Contacts with role types (Customer, Field User, Vendor Admin), Templates with blueprint inheritance, and a photo attachment system with URLs stored in the database. Zoho CRM is a conventional sales CRM with Accounts, Contacts, Leads, Deals, Tasks, and Events. There is no native field-service or property-inspection module in standard Zoho CRM editions — those concepts must be modeled using custom fields, custom modules, or Zoho Creator integrations. FlitStack AI migrates FotoNotes Containers to Zoho Accounts (or a custom Properties module), Work Orders to Zoho Deals, and role-typed Contacts to Zoho Contacts with custom pick-list fields preserving the original role. Template metadata becomes custom fields or lookup relationships. Photo attachments are re-uploaded to Zoho Files via batched API calls that respect Zoho's per-edition rate limits (500–10,000 requests per minute). Original create dates, assigned managers, and vendor assignments are preserved as custom datetime and user-lookup fields. Workflows, blueprints, assignment rules, and notification triggers in FotoNotes have no Zoho CRM equivalent and must be rebuilt in Zoho's Workflow Rules or Blueprint tools — we export the FotoNotes automation definitions as a rebuild reference. Roles and permission sets require a Zoho admin to reassign Profiles and Role hierarchies post-migration.

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

FotoNotes

What's pushing teams away

Status updates on work orders sometimes fail to sync across the web portal and mobile app, causing field supervisors to lose visibility on which properties have been completed.
The platform rebranded from FotoNotes to SiteCapture in 2022, and the two product names cause confusion during vendor evaluation and support escalation — existing customers on the legacy FotoNotes branding struggle to locate updated documentation and pricing pages.
Batch report generation is an admin-only feature, so front-line field managers who need on-demand PDF summaries must request exports from a portal admin rather than generating them independently.
Custom fields created via templates are per-account and not easily documented — when migrating off platform, the complete field schema requires manual enumeration from within the portal admin settings.

Choosing

Zoho CRM

What's pulling them in

Free tier is genuinely usable for up to 3 users with leads, pipeline management, and email tracking — no credit card required, making it easy to evaluate before committing.
Pricing undercuts Salesforce by 80–90% at equivalent feature tiers, with Enterprise plans offering capabilities that cost 3–4× more on competing platforms.
Deep ecosystem of 45+ integrated apps (Books, Desk, Creator, Campaigns) means companies already in the Zoho suite get native integrations without third-party connectors.
Highly customizable: custom modules, custom fields, Canvas drag-and-drop layouts, and Blueprint workflow automation without requiring developer resources.
Small-business reviewers highlight real-time team visibility, daily time savings of 60–90 minutes, and the ability to mold the CRM to any industry vertical.

Object mapping

How FotoNotes objects map to Zoho CRM

Each row shows how a FotoNotes object lands in Zoho CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

FotoNotes

Container / Property / Project

maps to

Zoho CRM

Account (or custom Properties module)

1:1

Fully supported

FotoNotes Containers (also called Properties or Projects) are the parent records that hold work orders, contacts, and photos. Zoho CRM has no native container concept, so we map Containers to Accounts and use a custom Container_ID__c field to preserve the FotoNotes identifier. For organizations that rely heavily on container/containee template inheritance, we create a custom Properties module with a self-lookup for parent-child relationships.

FotoNotes

Work Order

maps to

Zoho CRM

Deal

1:1

Fully supported

FotoNotes Work Orders map directly to Zoho Deals — both represent a task or job tied to a property with a status, priority, assigned user, and dates. Work Order Type maps to a custom pick-list field on the Deal. The container-property association becomes the Account lookup on the Deal. Stage values (Open, In Progress, Completed, Flagged) map to Zoho Deal Stage pick-list values, which your admin defines in Zoho CRM setup.

FotoNotes

Contact (all role types)

maps to

Zoho CRM

Contact

1:1

Fully supported

FotoNotes contacts migrate to Zoho Contacts. Because Zoho has no native role-on-contact equivalent to FotoNotes' nine role types (Customer, Field User, Vendor Admin, etc.), we map the role type to a custom pick-list field (FN_Role_Type__c) on the Contact record. Portal Admins and Managers get a corresponding FN_Is_Portal_Admin__c checkbox for permission parity.

FotoNotes

Template / Containee Work Template

maps to

Zoho CRM

Custom Field or Blueprint

1:1

Fully supported

FotoNotes templates define work order structures and inherit container fields into contained work orders. Since Zoho CRM has no native template inheritance, we migrate template metadata as custom fields on the Deal object and document the template definitions so your Zoho admin can reproduce them as Zoho Blueprint process templates or default field values.

FotoNotes

Photo / Attachment

maps to

Zoho CRM

Zoho Files (Attachments on Deals/Accounts)

1:1

Fully supported

FotoNotes stores photo URLs (pointing to FotoNotes' cloud storage) linked to work orders and containers. Zoho CRM does not render external URL attachments inline. We download the original photo files from FotoNotes' storage, then re-upload them as Zoho Files attached to the corresponding Deal or Account records using Zoho's Batch API, respecting rate limits per your Zoho edition.

FotoNotes

Batch Report / PDF Export

maps to

Zoho CRM

Zoho Documents (attached to Account)

1:1

Fully supported

FotoNotes batch reports and bulk PDF exports are generated reports tied to a container. Zoho CRM has no native batch report equivalent — these must be regenerated post-migration using Zoho Reports or exported from FotoNotes before cutover and stored as Zoho Documents attached to the Account record.

FotoNotes

Activity Log / Comment

maps to

Zoho CRM

Zoho Task or Note

1:1

Fully supported

FotoNotes activity logs and work order comments (including the Comment Modal feature) map to Zoho Notes attached to the Deal. Timestamps and the commenting user are preserved as Note metadata. The Flag Photos feature is captured as a custom checkbox field on the Deal record.

FotoNotes

Vendor / Vendor Admin / Vendor Field User

maps to

Zoho CRM

Contact (with FN_Role_Type__c = Vendor)

1:1

Fully supported

FotoNotes vendors and vendor-role users are migrated as contacts in Zoho with FN_Role_Type__c set to the matching FotoNotes role (e.g., Vendor Admin, Vendor Field User). The migration preserves vendor contact details—name, email, phone, address. Because Zoho Profiles and Role Hierarchy manage permission scopes differently, vendor admin permissions do not migrate automatically; your Zoho admin uses the Role Mapping Report we deliver to assign appropriate Profiles and permissions after migration.

FotoNotes

Customer (read-only portal user)

maps to

Zoho CRM

Contact (with limited access)

1:1

Fully supported

FotoNotes Customers are read-only users who can view assigned projects. Zoho has no built-in customer portal role at the CRM level — for organizations relying on customer self-service, we recommend enabling Zoho Portal (separate license) and linking the Contact record as a portal user. We export the customer list and access relationships as a reference for portal setup.

FotoNotes

User / Manager / Portal Admin

maps to

Zoho CRM

Zoho User

1:1

Fully supported

FotoNotes users (Portal Admins, Managers, and standard Users) are resolved by email match to Zoho Users. Unmatched users are flagged before migration. FotoNotes user IDs are preserved as FN_User_ID__c on the User record for audit traceability. Manager assignments on work orders map to the Deal Owner's Manager hierarchy in Zoho.

FotoNotes	Zoho CRM	Compatibility
Container / Property / Project	Account (or custom Properties module)1:1	Fully supported
Work Order	Deal1:1	Fully supported
Contact (all role types)	Contact1:1	Fully supported
Template / Containee Work Template	Custom Field or Blueprint1:1	Fully supported
Photo / Attachment	Zoho Files (Attachments on Deals/Accounts)1:1	Fully supported
Batch Report / PDF Export	Zoho Documents (attached to Account)1:1	Fully supported
Activity Log / Comment	Zoho Task or Note1:1	Fully supported
Vendor / Vendor Admin / Vendor Field User	Contact (with FN_Role_Type__c = Vendor)1:1	Fully supported
Customer (read-only portal user)	Contact (with limited access)1:1	Fully supported
User / Manager / Portal Admin	Zoho User1:1	Fully supported

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.

FotoNotes gotchas

High

Container-to-contained field inheritance is implicit

Medium

Batch PDF reports are the only bulk export mechanism

Medium

Vendor sub-accounts require hierarchical mapping

Low

FotoNotes is now SiteCapture — documentation split

Zoho CRM gotchas

High

API access requires Professional tier or above

High

Subform fields do not export cleanly via CSV

Medium

API credit consumption is non-linear

Medium

Export download links expire in 7 days

Medium

Owner (User) assignments require pre-mapped user IDs

FotoNotes gotchas		Zoho CRM gotchas
Severity	Issue	Severity	Issue
High	Container-to-contained field inheritance is implicit	High	API access requires Professional tier or above
Medium	Batch PDF reports are the only bulk export mechanism	High	Subform fields do not export cleanly via CSV
Medium	Vendor sub-accounts require hierarchical mapping	Medium	API credit consumption is non-linear
Low	FotoNotes is now SiteCapture — documentation split	Medium	Export download links expire in 7 days
		Medium	Owner (User) assignments require pre-mapped user IDs

Pair-specific challenges

FotoNotes photo URLs require re-upload to Zoho Files — they do not migrate as inline attachments

FotoNotes stores photos as URL references in its database, pointing to FotoNotes' cloud storage, linked to work orders and containers. Zoho CRM does not render external URL fields as inline image previews — photos must be downloaded from FotoNotes' storage and re-uploaded as Zoho Files attached to the corresponding Account or Deal. For accounts with thousands of inspection photos (FotoNotes reports 100+ million photos taken platform-wide), this is a multi-step batch operation. Zoho's per-edition API rate limits (500 req/min on Standard, 2,500 on Professional, 10,000 on Enterprise) govern upload throughput. We batch the re-upload using Zoho's Bulk API and surface the photo count in the pre-migration audit report so you can plan the cutover window accordingly.
FotoNotes container-to-work-order template inheritance has no Zoho CRM equivalent

FotoNotes' container/containee model lets you define work order templates at the container (property) level, and child work orders automatically inherit container field values when created. Zoho CRM Deals have no native template inheritance — field defaults must be configured individually per Deal type or replicated using Zoho Blueprint's field-population rules. We surface the full set of FotoNotes templates, their inherited fields, and their conditional rules in a Template Inventory Report before migration. Your Zoho admin uses this as a blueprint to configure Zoho Blueprint processes that reproduce the inheritance logic. This is a manual step that your admin must complete post-migration.
Zoho CRM has no read-only customer portal for external property contacts by default

FotoNotes includes a Customer role — external property owners or tenants who can log in to a portal to view assigned projects and reports in read-only mode. Zoho CRM's standard editions do not include a built-in read-only customer portal; Zoho Portal is a separate licensing add-on. Contacts migrated with FotoNotes role type 'Customer' are flagged in Zoho with FN_Role_Type__c, and we export a Customer Access Report listing every contact who had portal access. If your organization relies on external property contacts reviewing inspection reports through FotoNotes, plan for Zoho Portal activation and contact re-invitation post-migration.
Zoho API rate limits constrain photo batch upload during migration

Zoho CRM API credit consumption is tied to your edition: Starter/Standard tier allows 500 requests per minute, Professional allows 2,500, Enterprise allows 10,000. Migrating large FotoNotes portfolios with thousands of photos (common for property management companies managing 10,000+ units) requires staged batch uploads. We pace photo re-uploads using Zoho's Bulk API, track API credit consumption per the X-API-CREDITS-REMAINING header, and pause when credit usage exceeds 50% of the daily limit to avoid throttling. The migration timeline estimate includes time for batched photo upload based on your Zoho edition's rate limit.
FotoNotes vendor-role contacts require manual Zoho Profile assignment after migration

FotoNotes' nine named roles (Portal Admin, Manager, User, Field User, Customer, Vendor Admin with Edit, Vendor Admin with Admin Permissions, Vendor Field User) each carry different permission scopes for viewing hidden fields, documents, comments, and reports. Zoho CRM uses Profiles and Role Hierarchy to control access. There is no direct 1:1 mapping between FotoNotes' nine roles and Zoho Profiles — most organizations collapse these to 3–5 Zoho Profiles (e.g., Full Access, Standard User, Field Worker, Read-Only Customer). We export a Role Mapping Report from FotoNotes listing every user, their role, and their permission scope. Your Zoho admin reviews this and assigns Zoho Profiles before the team goes live.

Migration approach

Six steps for a successful FotoNotes to Zoho CRM data migration

Discovery audit and FotoNotes schema inventory

We connect to FotoNotes via read-only API access and inventory every Container, Work Order type, Contact role, Template, and Attachment relationship. We count total records, identify custom field names and pick-list values, and export the FotoNotes workflow definitions and role-permission matrix as a reference for Zoho admin setup. The audit report includes a record count by object, a custom property inventory, a photo attachment count per work order, and a list of users who need Zoho accounts created before migration.
Zoho CRM schema setup and custom field creation

Before data moves, your Zoho admin (or our team) creates the custom fields and modules required for the migration: FN_Role_Type__c and FN_Is_Portal_Admin__c on Contacts, FN_Property_Type__c and Account Status on Accounts, FN_Work_Order_Type__c, FN_Priority__c, FN_Vendor__c, FN_Template_Name__c, FN_Is_Flagged__c, and original-create-date fields on Deals. We deliver a Zoho Setup Checklist based on the FotoNotes schema inventory so the CRM side is configured before validation runs. If you use Zoho Blueprint to model work order processes, we document the FotoNotes template inheritance rules for Blueprint conversion.
Test migration with field-level validation

A representative slice migrates first — typically 100–500 records spanning Containers/Accounts, Work Orders/Deals, Contacts, and a sample of photo attachments. We generate a field-level diff comparing source and destination values so you can verify role-type mapping, container-to-account linkage, work order stage values, and photo upload completeness before the full run commits. Any pick-list value mismatches or missing custom fields surface here so corrections happen in staging, not in production.
Full migration with batch photo re-upload

The full migration runs in dependency order: Accounts first (for foreign-key resolution), then Contacts, then Deals with owner resolution by email match. Photo attachments are re-uploaded as Zoho Files using batched API calls paced to your Zoho edition's rate limit. A delta-pickup window of 24–48 hours captures any FotoNotes records modified during the cutover. All FotoNotes workflow and automation definitions are exported as a Workflow Rebuild Reference document for your Zoho admin.
Audit log, reconciliation report, and rollback readiness

FlitStack AI generates a post-migration audit log listing record counts by object, attachment volumes, and any records that failed validation. We compare total FotoNotes record counts to total Zoho record counts, verify owner resolution rates, and confirm photo file volumes. One-click rollback is available if reconciliation fails. We also deliver the Role Mapping Report and Workflow Rebuild Reference document at this stage so your Zoho admin can proceed with Profile assignments and Blueprint setup.

Platform deep dives

Context on both ends of the pair

FotoNotes

Source

Strengths

Photo-first inspection workflow with mobile app capture and cloud sync across devices
Container/containee data model reduces duplicate property data across large portfolios
Supports seven distinct user roles including vendor admin and customer read-only access
Batch PDF report exports allow portfolio-level review across multiple properties at once
Field user mobile app works offline and syncs when connectivity is restored

Weaknesses

The FotoNotes-to-SiteCapture rebranding splits web presence and creates documentation gaps for legacy customers
Granular role-based permissions require careful mapping during migration — vendor admin and customer roles do not map directly to standard CRM roles
Custom work type templates vary by account, making schema extraction non-trivial without direct portal admin access
Status synchronization issues between web and mobile are an ongoing pain point reported in user reviews
No publicly documented public API means programmatic data export relies on the admin batch report feature rather than a REST endpoint

Zoho CRM

Destination

Strengths

Generous free tier (3 users) with real CRM functionality — no artificial feature restrictions that prevent valid use cases.
Per-seat pricing is transparent and predictable; no contact-based billing surprises that inflate monthly invoices.
Blueprint visual workflow builder lets sales ops teams automate stage progressions without developer involvement.
Canvas drag-and-drop layout editor lets non-technical users customize module views and forms per role.
Active development cadence: API v8 is well-documented, supports bulk endpoints, and COQL queries handle complex filtering.

Weaknesses

Poor support quality and inconsistent SLA — Enterprise tier requires 50+ user minimum for Priority Phone support.
Daily export limits in the UI vary by plan tier, making large dataset extraction slow and planning-dependent.
Zia AI features are gated behind $40+/user Enterprise tier, not available to most SMB customers who chose Zoho for cost savings.
User-reported occasional UI inconsistencies and performance slowdowns on large datasets with many custom fields.
No EU-hosted option limits appeal for GDPR-sensitive companies; some competitors offer data residency guarantees Zoho does not.

	FotoNotes Source	Zoho CRM Destination
Strengths	Photo-first inspection workflow with mobile app capture and cloud sync across devices Container/containee data model reduces duplicate property data across large portfolios Supports seven distinct user roles including vendor admin and customer read-only access Batch PDF report exports allow portfolio-level review across multiple properties at once Field user mobile app works offline and syncs when connectivity is restored	Generous free tier (3 users) with real CRM functionality — no artificial feature restrictions that prevent valid use cases. Per-seat pricing is transparent and predictable; no contact-based billing surprises that inflate monthly invoices. Blueprint visual workflow builder lets sales ops teams automate stage progressions without developer involvement. Canvas drag-and-drop layout editor lets non-technical users customize module views and forms per role. Active development cadence: API v8 is well-documented, supports bulk endpoints, and COQL queries handle complex filtering.
Weaknesses	The FotoNotes-to-SiteCapture rebranding splits web presence and creates documentation gaps for legacy customers Granular role-based permissions require careful mapping during migration — vendor admin and customer roles do not map directly to standard CRM roles Custom work type templates vary by account, making schema extraction non-trivial without direct portal admin access Status synchronization issues between web and mobile are an ongoing pain point reported in user reviews No publicly documented public API means programmatic data export relies on the admin batch report feature rather than a REST endpoint	Poor support quality and inconsistent SLA — Enterprise tier requires 50+ user minimum for Priority Phone support. Daily export limits in the UI vary by plan tier, making large dataset extraction slow and planning-dependent. Zia AI features are gated behind $40+/user Enterprise tier, not available to most SMB customers who chose Zoho for cost savings. User-reported occasional UI inconsistencies and performance slowdowns on large datasets with many custom fields. No EU-hosted option limits appeal for GDPR-sensitive companies; some competitors offer data residency guarantees Zoho does not.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from FotoNotes to Zoho CRM

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

FotoNotes

Zoho CRM

How FotoNotes objects map to Zoho CRM

What specifically takes care here

Six steps for a successful FotoNotes to Zoho CRM data migration

Context on both ends of the pair

How hard is this migration?

Estimate your FotoNotes to Zoho CRM migration cost

What are you migrating?

Frequently asked questions about FotoNotes to Zoho CRM data migrations

Can't find your answer?

Related migrations to explore

Move from FotoNotes.
Land in Zoho CRM, intact.

Migrate from FotoNotes to Zoho CRM

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

FotoNotes

Zoho CRM

How FotoNotes objects map to Zoho CRM

What specifically takes care here

Six steps for a successful FotoNotes to Zoho CRM data migration

Context on both ends of the pair

How hard is this migration?

Estimate your FotoNotes to Zoho CRM migration cost

Frequently asked questions about FotoNotes to Zoho CRM data migrations

Can't find your answer?

How long does a FotoNotes to Zoho CRM migration take?

Will my FotoNotes workflows and assignment rules migrate to Zoho CRM?

What happens to FotoNotes container types and work order templates in Zoho CRM?

Can FotoNotes vendor contacts and field users migrate to Zoho CRM contacts?

What happens to inspection photos attached to FotoNotes work orders?

Does the migration affect my FotoNotes account during cutover?

How are FotoNotes Customer portal users handled in Zoho CRM?

Related migrations to explore

Move from FotoNotes. Land in Zoho CRM, intact.

Move from FotoNotes.
Land in Zoho CRM, intact.