Yes. Existing automations keep running, but Salesforce stopped supporting them on 31 December 2025. That means no bug fixes and no help when they break, and new features are built only for Flow. Each release adds risk to a legacy org. Asamara’s free Automation Health Assessment lists every Workflow Rule and Process Builder in your org, flags conflicts and points of failure, and gives you a prioritised plan for moving to Flow.

Salesforce’s Migrate to Flow tool only handles simple cases. The real risk is in automations that overlap, run in the wrong order, or depend on logic nobody wrote down. Asamara audits what each automation actually does, combines duplicates into well-designed record-triggered Flows, tests them in a sandbox, and documents everything. Your team can then maintain it without needing us.

Not automatically. NPSP still works, but all new nonprofit features now go to Nonprofit Cloud, which runs on the core platform with Person Accounts and a newer gift data model. Moving is more like a re-implementation than an upgrade. Asamara works with NPSP and Nonprofit Cloud and will tell you honestly whether moving now is worth it for your organisation, even if the answer is “not yet.”

NPSP is a managed package built on Accounts and Contacts with the Household model. Nonprofit Cloud is built into the core platform. It uses Person Accounts and relationship groups, has native modules for programs and fundraising, and gets new platform features first. The change affects your data model, reports and integrations. Asamara maps your current processes against both products before you decide, so the move fits how you work.

Quip subscriptions can’t be renewed after 1 March 2027. After a subscription ends, there are about 90 days of read-only access, then logins are blocked, and then data is deleted. Salesforce’s main recommended destination is Slack canvases. For organisations already on Microsoft, Asamara can connect Salesforce to SharePoint for document management with SSO, and plan the migration of your Quip content as a proper data migration.

It depends on where your team already works. Slack canvases suit Slack-first teams. SharePoint suits organisations on Microsoft 365, because documents stay in your existing governance and link directly to Salesforce records. Asamara builds Salesforce–Microsoft integrations with SSO and SharePoint document management, so account plans and files sit alongside the records they belong to.

Usually the platform was set up around a consultant’s template instead of your real processes. Other common causes are undocumented customisations and no support after go-live. Asamara starts by listening and maps how your organisation actually works. Then it redesigns Salesforce around that process and stays involved after launch to train your team and keep the system adapting.

Write down each process as it actually happens today: who does what, which data is involved, and where things get stuck. Then decide what should change before anything is built. Asamara runs this discovery as the first step of every project. It turns your workflows into a documented scope and a roadmap, so there are no surprises on deliverables or cost.

Salesforce now recommends Flow Approval Processes over classic approval processes. They handle multi-step, conditional and parallel approvals, which classic approvals struggle with. Asamara designs approval flows around your governance rules, such as spending limits, grant sign-offs and contract reviews, so decisions follow clear rules without slowing your team down.

Deduplicate, standardise formats, archive records nobody uses, and agree on one field mapping before anything is loaded. Teams often underestimate how much work this is, and it’s often where projects fail. Asamara plans and runs data migrations and clean-ups so your data arrives clean, structured and ready to use, whether you’re moving to Salesforce for the first time or out of NPSP.

Use standard objects whenever they fit, because they come with built-in features and reporting. Create custom objects only when your business has concepts Salesforce doesn’t model, such as projects, properties or memberships. Asamara designs data models that match how your organisation works and avoids adding complexity you’ll pay for later.

For many organisations, the real work starts after go-live: adoption, training, small fixes and changes as the organisation grows. Many partners disappear at handoff. Asamara stays involved after launch with training and ongoing changes, and documents everything so you’re never dependent on us to understand your own system.