Back4app is the backend behind CRM apps. For PHP you call the REST API with Guzzle or cURL and use the session token for auth—no server to write or host.

PHP Template

CRM App Backend Template
PHP — Schema, API & AI Guide

Q: Why use Back4app for a PHP CRM app?

Back4app gives PHP or Laravel CRM apps a managed backend: call REST endpoints for Contact, Deal, Activity with Guzzle or cURL; no database migrations.

Q: How do I list deals by stage from PHP?

GET /classes/Deal?where={"stage":"qualified"}&order=-expectedCloseDate with X-Parse-Session-Token header. Parse the JSON response.

Q: How do I pass the session token from PHP?

After login, send the X-Parse-Session-Token header on every request to /classes/Deal, /classes/Contact, etc.

A production-ready PHP CRM backend schema and Starter Kit on Back4app: Contact, Company, Deal, Activity, pipeline stages, ER diagram, data dictionary, JSON schema, API playground, and a one-click AI Agent prompt to deploy in minutes.

Build with AI Agent

Key Takeaways

On this page you get a production-ready CRM schema, a one-click AI prompt, and step-by-step PHP code — so you can ship a CRM app without building the backend.

Deploy in minutes — Paste the AI Agent prompt and get a running app with contacts, companies, deals, and pipeline.
Secure by default — ACLs and role-based access so users see only their assigned deals and data.
PHP-native SDK — Typed objects, async/await, offline pinning, and Live Queries for pipeline updates.
REST + GraphQL — Both APIs auto-generated; filter deals by stage, list activities by relatedTo.
Five classes — _User (built-in), Company, Contact, Deal (pipeline), Activity (tasks/events).

What Is the PHP CRM Backend Template?

Integrate PHP or Laravel with a managed CRM backend on Back4app. Call REST endpoints for Contact, Company, Deal, and Activity using Guzzle or cURL; no database migrations or schema management in PHP. PSR-style requests and type hints keep integration clean. Deploy your app on any host while Back4app handles auth, storage, and real-time.

Best for:

Sales teamsCRM buildersRapid prototypingField repsMVP launchesTeams choosing a BaaS for CRM

Overview

PHP and Laravel apps can use Back4app as the CRM backend without running migrations or managing the database. Call REST endpoints (GET /classes/Deal?where=..., POST /classes/Contact) with Guzzle or cURL; send X-Parse-Session-Token after login.

The five classes are shared across all clients. Your PHP code parses JSON responses and maps to your domain; Back4app handles storage, auth, and real-time. Add fields from the dashboard or API without touching PHP schema code.

Core CRM Features

PHP CRM backend with REST client: contact management, deal pipeline, and activity tracking. Use Guzzle or Laravel HTTP with session tokens and ACLs.

Contact management

Store and manage contacts with name, email, phone, company, and notes. Ideal for PHP apps.

Company management

Track companies with name, website, industry, and address. Links to contacts and deals.

Deal pipeline

Sales pipeline with stages, amount, expected close date, and assignment. Built for PHP backends.

Activity tracking

Log calls, emails, meetings, and notes linked to contacts and deals. Works with PHP SDK.

User & permissions

Built-in user model and pointers for ownership and assignment. ACLs out of the box for PHP.

Why Build Your PHP CRM Backend with Back4app?

Back4app gives PHP apps a ready CRM backend so you can focus on Laravel or your existing stack.

•REST integration: Use Guzzle or cURL to call Back4app REST endpoints for Contact, Company, Deal, Activity; PSR-style code and type hints.
•No database migrations: Schema lives on Back4app; add fields from the dashboard or API without touching your PHP schema layer.
•Deployment flexibility: Run your PHP app on any host; Back4app handles auth, storage, and real-time for CRM.

Ideal for Laravel or standalone PHP projects that need a managed CRM backend.

Core Benefits

A production-ready CRM backend so you can ship faster and focus on your app.

Ship Faster, No Backend Code

REST & GraphQL APIs and a ready-to-use schema — connect your app and go.

Secure by Default

ACLs and class-level permissions; restrict by assignedTo and createdBy.

Real-Time Pipeline

Live Queries over WebSockets for instant deal and activity updates.

Built-In Auth

User sign-up, login, and session handling out of the box.

Works Offline

Local pinning keeps contacts and deals available offline and syncs when you reconnect.

Deploy in Minutes

Use the AI Agent to create and deploy your CRM app from this template.

Ready to try it?

Let the Back4app AI Agent create your CRM app backend, connect the PHP frontend, and deploy — all from a single prompt.

Build with AI Agent Try the API Playground

Free to start — 50 AI Agent prompts/month, no credit card required

Technical Stack

Everything powering this CRM app template at a glance.

Frontend

PHP

Backend

Back4app

Database

MongoDB

Auth

Auth & Access Control

APIs

REST & GraphQL

Deployment

AI Agent / Dashboard

ER Diagram

Entity-Relationship diagram for the PHP CRM app data model.

ER Diagram

View diagram source

Mermaid

erDiagram
    _User {
        String objectId PK
        String username
        String email
        String password
        Date createdAt
        Date updatedAt
    }

    Company {
        String objectId PK
        String name
        String website
        String industry
        String address
        String notes
        Pointer createdBy FK
        Date createdAt
        Date updatedAt
    }

    Contact {
        String objectId PK
        String name
        String email
        String phone
        Pointer company FK
        String notes
        Pointer createdBy FK
        Date createdAt
        Date updatedAt
    }

    Deal {
        String objectId PK
        String title
        Number amount
        String stage
        Pointer contact FK
        Pointer company FK
        Date expectedCloseDate
        String notes
        Pointer assignedTo FK
        Date createdAt
        Date updatedAt
    }

    Activity {
        String objectId PK
        String type
        String subject
        String description
        Date dueDate
        Date completedAt
        Pointer relatedTo FK
        Pointer createdBy FK
        Date createdAt
        Date updatedAt
    }

    Company ||--o{ Contact : "has"
    Company ||--o{ Deal : "has"
    Contact ||--o{ Deal : "has"
    _User ||--o{ Deal : "assignedTo"
    _User ||--o{ Activity : "createdBy"
    Contact ||--o{ Activity : "relatedTo"
    Deal ||--o{ Activity : "relatedTo"
    _User ||--o{ Company : "createdBy"
    _User ||--o{ Contact : "createdBy"

Integration Flow

Auth-to-CRUD sequence: how your PHP app talks to Back4app — login, then query contacts and deals, update pipeline.

ER Diagram

View diagram source

Mermaid

sequenceDiagram
  participant User
  participant App as PHP App
  participant Back4app as Back4app REST API

  User->>App: Login
  App->>Back4app: POST /login (username, password)
  Back4app-->>App: sessionToken
  App-->>User: Logged in

  User->>App: Load contacts and deals
  App->>Back4app: GET /classes/Deal or GET /classes/Contact (X-Parse-Session-Token)
  Back4app-->>App: results[]
  App-->>User: Show pipeline

  User->>App: Create deal or contact
  App->>Back4app: POST /classes/Deal or POST /classes/Contact
  Back4app-->>App: objectId, createdAt
  App-->>User: Updated list

Data Dictionary

Complete field reference for every class in the schema.

Field	Type	Description	Required
objectId	String	Auto-generated unique identifier	auto
name	String	Full name of the contact
email	String	Email address	—
phone	String	Phone number	—
company	Pointer<Company>	Company this contact belongs to	—
notes	String	Free-form notes	—
createdBy	Pointer<_User>	User who created this contact	—
createdAt	Date	Auto-generated creation timestamp	auto
updatedAt	Date	Auto-generated last-update timestamp	auto

9 fields in Contact

Security & Permissions

How ownership, ACLs, and class-level permissions protect data in this CRM schema.

Row-Level ACLs

Use ACLs and pointers (assignedTo, createdBy) so users only see and edit their assigned deals and related data.

Class-Level Permissions

CLPs restrict which roles or users can create, read, update, or delete objects at the class level.

Pointer-Based Ownership

Deal.assignedTo and Activity.createdBy link to _User; Cloud Code can enforce visibility and edits by role.

Schema (JSON)

Raw JSON schema definition — copy and use in your Back4app app or import via the API.

JSON

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

{
  "classes": [
    {
      "className": "Contact",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "name": {
          "type": "String",
          "required": true
        },
        "email": {
          "type": "String",
          "required": false
        },
        "phone": {
          "type": "String",
          "required": false
        },
        "company": {
          "type": "Pointer",
          "targetClass": "Company",
          "required": false
        },
        "notes": {
          "type": "String",
          "required": false
        },
        "createdBy": {
          "type": "Pointer",
          "targetClass": "_User",
          "required": false
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    },
    {
      "className": "Company",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "name": {
          "type": "String",
          "required": true
        },
        "website": {
          "type": "String",
          "required": false
        },
        "industry": {
          "type": "String",
          "required": false
        },
        "address": {
          "type": "String",
          "required": false
        },
        "notes": {
          "type": "String",
          "required": false
        },
        "createdBy": {
          "type": "Pointer",
          "targetClass": "_User",
          "required": false
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    },
    {
      "className": "Deal",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "title": {
          "type": "String",
          "required": true
        },
        "amount": {
          "type": "Number",
          "required": false
        },
        "stage": {
          "type": "String",
          "required": false
        },
        "contact": {
          "type": "Pointer",
          "targetClass": "Contact",
          "required": false
        },
        "company": {
          "type": "Pointer",
          "targetClass": "Company",
          "required": false
        },
        "expectedCloseDate": {
          "type": "Date",
          "required": false
        },
        "notes": {
          "type": "String",
          "required": false
        },
        "assignedTo": {
          "type": "Pointer",
          "targetClass": "_User",
          "required": false
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    },
    {
      "className": "Activity",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "type": {
          "type": "String",
          "required": false
        },
        "subject": {
          "type": "String",
          "required": false
        },
        "description": {
          "type": "String",
          "required": false
        },
        "dueDate": {
          "type": "Date",
          "required": false
        },
        "completedAt": {
          "type": "Date",
          "required": false
        },
        "relatedTo": {
          "type": "Pointer",
          "required": false
        },
        "createdBy": {
          "type": "Pointer",
          "targetClass": "_User",
          "required": false
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    },
    {
      "className": "_User",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "username": {
          "type": "String",
          "required": true
        },
        "email": {
          "type": "String",
          "required": true
        },
        "password": {
          "type": "String",
          "required": true
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    }
  ]
}

Build with AI Agent

Use the Back4app AI Agent to build a real CRM app from this template: it will create the frontend, the backend (this schema, auth, and APIs), and deploy it — no manual setup. The prompt below describes this CRM stack so the Agent can generate a production-ready app in one go.

Back4app AI Agent

Ready to build

Create a CRM app on Back4app with this exact schema and behavior.

Schema:
1. _User (use Back4app built-in): username (String, required), email (String, required), password (String, required); objectId, createdAt, updatedAt (system).
2. Company: name (String, required), website (String), industry (String), address (String), notes (String), createdBy (Pointer to _User); objectId, createdAt, updatedAt (system).
3. Contact: name (String, required), email (String), phone (String), company (Pointer to Company), notes (String), createdBy (Pointer to _User); objectId, createdAt, updatedAt (system).
4. Deal: title (String, required), amount (Number), stage (String; e.g. lead, qualified, proposal, negotiation, won, lost), contact (Pointer to Contact), company (Pointer to Company), expectedCloseDate (Date), notes (String), assignedTo (Pointer to _User); objectId, createdAt, updatedAt (system).
5. Activity: type (String; e.g. call, email, meeting, note), subject (String), description (String), dueDate (Date), completedAt (Date), relatedTo (Pointer to Contact or Deal), createdBy (Pointer to _User); objectId, createdAt, updatedAt (system).

Security:
- Set ACLs so only authenticated users can access data; use role-based or owner-based rules where appropriate (e.g. assignedTo, createdBy).
- Use Class-Level Permissions so only authenticated users can create/read/update/delete these classes.

Auth:
- Sign-up (username, email, password) and login; support logout/session.

Behavior:
- Full CRUD for Company, Contact, Deal, and Activity.
- List deals with filter by stage and order by expectedCloseDate or updatedAt (pipeline view).
- List activities by relatedTo (Contact or Deal).
- Optional: real-time Live Queries for Deal and Activity for dashboard/pipeline updates.
- Optional: offline pinning for mobile (Contacts, Deals, Activities).

Deliver:
- Create the Back4app app with the schema above, ACLs, and any Cloud Code needed.
- Generate the frontend and connect it to this backend; deploy so the app is runnable end-to-end.

Press the button below to open the Agent with this template's prompt pre-filled.

Deploy in minutes50 free prompts / monthNo credit card required

API Playground

Try the REST and GraphQL endpoints for the CRM schema. Responses from the example data above — no Back4app account needed.

Loading playground…

Uses the same CRM schema (Contact, Company, Deal, Activity) as this template.

Step-by-Step PHP Integration

Connect to your Back4app backend from a PHP app using the Back4app PHP SDK.

Step 1: Install Back4app PHP SDK
Add the Back4app SDK for your stack (e.g. npm, pubspec, or package manager).
PHP
1
```
composer require guzzlehttp/guzzle
```

Step 2: Initialize Back4app in your app

Initialize the Back4app SDK at app startup with your App ID and server URL.

PHP

// Initialize (e.g. bootstrap or config)
$baseUrl = 'https://parseapi.back4app.com';
$appId = getenv('PARSE_APP_ID');
$restKey = getenv('PARSE_REST_KEY');
$sessionToken = null; // set after login

Step 3: Query contacts and deals

Use the SDK to fetch Contact and Deal objects; filter deals by stage for the pipeline.

PHP

// GET /classes/Deal or /classes/Contact
function getDeals(string $baseUrl, string $appId, string $restKey, ?string $sessionToken, string $stage = 'qualified'): array {
    $client = new \GuzzleHttp\Client();
    $headers = [
        'X-Parse-Application-Id' => $appId,
        'X-Parse-REST-API-Key'   => $restKey,
        'Content-Type' => 'application/json',
    ];
    if ($sessionToken) $headers['X-Parse-Session-Token'] = $sessionToken;
    $res = $client->get($baseUrl . '/classes/Deal?where=' . urlencode(json_encode(['stage' => $stage])) . '&order=expectedCloseDate', ['headers' => $headers]);
    $body = json_decode($res->getBody()->getContents(), true);
    return $body['results'] ?? [];
}
function getContacts(string $baseUrl, string $appId, string $restKey, ?string $sessionToken): array {
    $client = new \GuzzleHttp\Client();
    $headers = [
        'X-Parse-Application-Id' => $appId,
        'X-Parse-REST-API-Key'   => $restKey,
        'Content-Type' => 'application/json',
    ];
    if ($sessionToken) $headers['X-Parse-Session-Token'] = $sessionToken;
    $res = $client->get($baseUrl . '/classes/Contact', ['headers' => $headers]);
    $body = json_decode($res->getBody()->getContents(), true);
    return $body['results'] ?? [];
}

Step 4: Create a contact or deal

Create a new Contact or Deal with the required fields and pointers (company, contact, assignedTo), then save.

PHP

// POST /classes/Deal or /classes/Contact
function createDeal(string $baseUrl, string $appId, string $restKey, string $sessionToken, string $title, string $stage = 'lead', ?float $amount = null): array {
    $client = new \GuzzleHttp\Client();
    $body = ['title' => $title, 'stage' => $stage];
    if ($amount !== null) $body['amount'] = $amount;
    $res = $client->post($baseUrl . '/classes/Deal', [
        'headers' => [
            'X-Parse-Application-Id' => $appId,
            'X-Parse-REST-API-Key'   => $restKey,
            'X-Parse-Session-Token'  => $sessionToken,
            'Content-Type' => 'application/json',
        ],
        'json' => $body,
    ]);
    return json_decode($res->getBody()->getContents(), true);
}
function createContact(string $baseUrl, string $appId, string $restKey, string $sessionToken, string $name, ?string $email = null, ?string $phone = null): array {
    $client = new \GuzzleHttp\Client();
    $headers = [
        'X-Parse-Application-Id' => $appId,
        'X-Parse-REST-API-Key'   => $restKey,
        'X-Parse-Session-Token'  => $sessionToken,
        'Content-Type' => 'application/json',
    ];
    $body = ['name' => $name];
    if ($email !== null) $body['email'] = $email;
    if ($phone !== null) $body['phone'] = $phone;
    $res = $client->post($baseUrl . '/classes/Contact', ['headers' => $headers, 'json' => $body]);
    return json_decode($res->getBody()->getContents(), true);
}

Step 5: Update deal stage and activities

Update Deal.stage when moving in the pipeline; create and list Activity by relatedTo.

PHP

// PUT /classes/Deal/{objectId} — update stage
// DELETE /classes/Deal/{objectId}
function updateDealStage(string $baseUrl, string $appId, string $restKey, string $sessionToken, string $objectId, string $stage): void {
    $client = new \GuzzleHttp\Client();
    $client->put($baseUrl . '/classes/Deal/' . $objectId, [
        'headers' => [
            'X-Parse-Application-Id' => $appId,
            'X-Parse-REST-API-Key'   => $restKey,
            'X-Parse-Session-Token'  => $sessionToken,
            'Content-Type' => 'application/json',
        ],
        'json' => ['stage' => $stage],
    ]);
}
function deleteDeal(string $baseUrl, string $appId, string $restKey, string $sessionToken, string $objectId): void {
    $client = new \GuzzleHttp\Client();
    $headers = [
        'X-Parse-Application-Id' => $appId,
        'X-Parse-REST-API-Key'   => $restKey,
        'X-Parse-Session-Token'  => $sessionToken,
    ];
    $client->delete($baseUrl . '/classes/Deal/' . $objectId, ['headers' => $headers]);
}

Frequently Asked Questions

Common questions about the CRM app backend template.

What is Back4app?

Why use Back4app for a PHP CRM app?

How do I list deals by stage from PHP?

How do I pass the session token from PHP?

Trusted by developers worldwide

Join the community building the future of apps

Ready to Build Your CRM App?

Start your PHP project in minutes. No credit card required.

Build with AI Agent

CRM App Backend TemplatePHP — Schema, API & AI Guide

Key Takeaways

What Is the PHP CRM Backend Template?

Overview

Core CRM Features

Contact management

Company management

Deal pipeline

Activity tracking

User & permissions

Why Build Your PHP CRM Backend with Back4app?

Core Benefits

Ship Faster, No Backend Code

Secure by Default

Real-Time Pipeline

Built-In Auth

Works Offline

Deploy in Minutes

Ready to try it?

Technical Stack

ER Diagram

Integration Flow

Data Dictionary

Security & Permissions

Row-Level ACLs

Class-Level Permissions

Pointer-Based Ownership

Schema (JSON)

Build with AI Agent

API Playground

Step-by-Step PHP Integration

Step 1: Install Back4app PHP SDK

Step 2: Initialize Back4app in your app

Step 3: Query contacts and deals

Step 4: Create a contact or deal

Step 5: Update deal stage and activities

Frequently Asked Questions

Trusted by developers worldwide

Ready to Build Your CRM App?

CRM App Backend Template
PHP — Schema, API & AI Guide