diff --git a/lib/perpetuity/mapper.rb b/lib/perpetuity/mapper.rb
index <HASH>..<HASH> 100644
--- a/lib/perpetuity/mapper.rb
+++ b/lib/perpetuity/mapper.rb
@@ -60,7 +60,6 @@ module Perpetuity
     end
 
     def insert
-      raise "#{object} is invalid and cannot be persisted." if object.respond_to?(:valid?) and !object.valid?
       raise "#{object} is invalid and cannot be persisted." unless validations.valid?(object)
       serializable_attributes = {}
       serializable_attributes[:id] = object.instance_eval(&self.class.id) unless self.class.id.nil?
diff --git a/spec/mapper_spec.rb b/spec/mapper_spec.rb
index <HASH>..<HASH> 100644
--- a/spec/mapper_spec.rb
+++ b/spec/mapper_spec.rb
@@ -56,12 +56,6 @@ describe Perpetuity::Mapper do
       BookMapper.insert book
       BookMapper.first.id.should == 'my-title'
     end
-
-    it "checks for object validity before persisting" do
-      invalid_article = Article.new(title=nil)
-      invalid_article.stub(valid?: nil)
-      expect { ArticleMapper.insert(invalid_article) }.to raise_error
-    end
   end
 
   describe "deletion" do
Remove check for an object's `valid?` method

Having an object tell the ORM whether or not it is valid places
persistence concerns within the business objects, which is not what we
want to do.